vault backup: 2023-08-15 18:39:20
This commit is contained in:
@@ -15,12 +15,15 @@ year: 2023
|
|||||||
|2000 kcal|90 kg|
|
|2000 kcal|90 kg|
|
||||||
|
|
||||||
#### Work 💻
|
#### Work 💻
|
||||||
- [ ] Try playwright
|
- [x] Try playwright ✅ 2023-08-15
|
||||||
- [ ] behave and unit testing on the backend
|
- [ ] behave and unit testing on the backend
|
||||||
- [ ] jenkins the shit out of this
|
- [ ] jenkins the shit out of this
|
||||||
|
|
||||||
#### Notes ✏
|
#### Notes ✏
|
||||||
-
|
- [[Playwright]] [[E2E testing]] seems really powerful but I can't seem to get the tests working at all from within the [[Docker]] container. I don't know if this is a network issue or a docker issue or whatever.
|
||||||
|
- On the backend I don't know if there's going to be a need of [[Behave]] for [[Behaviour tests]]. [[Unit testing]] at least should be fine.
|
||||||
|
- [[Playwright]] seems to be working well with [[Cucumber]] for [[Behaviour tests]] and [[BDD]]. It would be nice to try it out sometime to remove code duplication and to allow for better collaboration since QA can write their own tests in using gherkin.
|
||||||
|
- [[Playwright]] and [[Storybook]] should play well together but still haven't had the time to try it out.
|
||||||
|
- Whenever [[Playwright]] works, I should set up just a few tests on the backend, the bare minimum, so I can finish setting up [[Jenkins]] in its own container, even if it doesn't trigger automatically on P4 triggers.
|
||||||
#### Outcomes 🦄
|
#### Outcomes 🦄
|
||||||
1.
|
1. Learned about [[Playwright]], implemented some basic tests that don't yet work.
|
||||||
Reference in New Issue
Block a user