diff --git a/Tracking/Daily/2023-08-14.md b/Tracking/Daily/2023-08-14.md index 6fbb1be..aaf23b9 100644 --- a/Tracking/Daily/2023-08-14.md +++ b/Tracking/Daily/2023-08-14.md @@ -23,10 +23,10 @@ year: 2023 - [x] Try jenkins for automated testing ASAP ✅ 2023-08-14 #### Notes ✏ -- [[Jenkins]] looks cool and a really complete [[CI]]/[[CD]] solution but I couldn't have it talk to [[Perforce]], or more specifically the [[Docker]] container couldn't receive packets from the [[Perforce]]. I should just let that slide for the moment and use it somewhat manually and automate [[Perforce]] later. -- [[Vitest]] is so cool and efficient, it's great for [[Unit testing]]. -- [[Storybook]] seems really powerful but a bit difficult to setup and a fair amount of boilerplate, it's quite verbose. Hot reload didn't work properly either which hindered the DX. Anyway when the UI becomes more complex with more components it's going to become more and more useful, I've only written a couple of stories. I think the true power comes from the integration with automated tools especially. -- [[Playwright]] is next of [[End to end testing]]. +- [[Jenkins]] looks cool and a really complete [[CI]]/[[CD]] solution but I couldn't have it talk to [[Perforce]], or more specifically the [[Docker]] container couldn't receive packets from the [[Perforce]]. I should just let that slide for the moment and use it somewhat manually and automate [[Perforce]] later. #devops/cicd +- [[Vitest]] is so cool and efficient, it's great for [[Unit testing]]. #devops/testing +- [[Storybook]] seems really powerful but a bit difficult to setup and a fair amount of boilerplate, it's quite verbose. Hot reload didn't work properly either which hindered the DX. Anyway when the UI becomes more complex with more components it's going to become more and more useful, I've only written a couple of stories. I think the true power comes from the integration with automated tools especially. #devops +- [[Playwright]] is next of [[End to end testing]]. #devops/testing #### Outcomes 🦄 1. Started stretching again 2. Started testing the app for work. Already done a fair amount of unit testing and component isolation.