vault backup: 2023-08-14 23:50:43
This commit is contained in:
@@ -4,8 +4,7 @@ week: 2023-W33
|
||||
year: 2023
|
||||
---
|
||||
#### To do 💪
|
||||
- [ ] courses
|
||||
- [ ]
|
||||
- [x] courses ✅ 2023-08-14
|
||||
|
||||
#### Habits ☕
|
||||
- [ ] Sport
|
||||
@@ -19,13 +18,14 @@ year: 2023
|
||||
- [x] Batch deliveries ✅ 2023-08-14
|
||||
- [x] Start testing the application ✅ 2023-08-14
|
||||
- [x] Vitest for unit testing on the frontend ✅ 2023-08-14
|
||||
- [ ] Storybook for component testing on the frontend
|
||||
- [x] Storybook for component testing on the frontend ✅ 2023-08-14
|
||||
- [ ] Playwright for end to end testing, should play along with behave for behavioural tests on the backend
|
||||
- [x] Try jenkins for automated testing ASAP ✅ 2023-08-14
|
||||
|
||||
#### Notes ✏
|
||||
- [[Jenkins]] looks cool 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.
|
||||
- [[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 too which hindered the DX.
|
||||
|
||||
#### Outcomes 🦄
|
||||
1.
|
||||
Reference in New Issue
Block a user