Hello friends!!
Hope you are doing well, This post is mainly for QA guys who writes E2E testing code in playwright or puppeteer or any other framework. Before moving any further let's start with problems or motivation that occur while writing these tests.
- Long running Tests.
- Complicated test flows.
- Duplicate Code.
- No track of regression or future tests.
These all problems can be shorted with simple architecture adaptions in the code. I will explain in points.
- Keep Index file or entry file which declares all tests in one place.
- Keep tests in order Insertion, Updation then Deletion.
- Write regressions or future tests in same file as commented code or ToDo.
Thanks and Have a Nice Day.
Top comments (1)
pdf generation with puppeteer is great until you need to scale it. then it becomes a full-time job
snapapi.pics does pdf too btw — same REST API, just set format=pdf. handles headers/footers/margins