I see what you mean. That's an interesting way to help you improve the code quality.
I was working on an open-source tool called TesterBot and the idea was to point out such issues sort of in a post-build test automation. However, I stopped because of LightHouse. Although, I'm contemplating restarting the project when I get some time and sooner if someone else finds it interesting. :o
I was also planning on implementing things listed in the FrontEndChecklist
During development, there isn't enough time to write tests, so our only option is manual testing. We don't need a reminder of how inefficient, time-consuming, error-prone and boring that can get. When we get around to writing test-automations, we spend a lot of time writing tests from scratch. However, most of the test-cases for testing web-applications can be automated and reused.
We created Testerbot to automatically test web-applications during the development process via Puppeteer which talks to Headless Google Chrome.
The basic framework is ready and we have implemented a few test-cases, but we need help in adding more reusable test-cases.
Note: I started this project several months ago and built a SaaS product, but realized that an open-source test automation package will help catch issues quickly during development. I recently stumbled upon frontendchecklist.io/ and created github issues to automate as many of those…
I see what you mean. That's an interesting way to help you improve the code quality.
I was working on an open-source tool called TesterBot and the idea was to point out such issues sort of in a post-build test automation. However, I stopped because of LightHouse. Although, I'm contemplating restarting the project when I get some time and sooner if someone else finds it interesting. :o
I was also planning on implementing things listed in the FrontEndChecklist
theoutlander / testerbot
Automatic Front-End Testing
testerbot
Automatic Front-End Testing
Purpose
During development, there isn't enough time to write tests, so our only option is manual testing. We don't need a reminder of how inefficient, time-consuming, error-prone and boring that can get. When we get around to writing test-automations, we spend a lot of time writing tests from scratch. However, most of the test-cases for testing web-applications can be automated and reused.
We created Testerbot to automatically test web-applications during the development process via Puppeteer which talks to Headless Google Chrome.
The basic framework is ready and we have implemented a few test-cases, but we need help in adding more reusable test-cases.
Note: I started this project several months ago and built a SaaS product, but realized that an open-source test automation package will help catch issues quickly during development. I recently stumbled upon frontendchecklist.io/ and created github issues to automate as many of those…