At Testim.io - we see the automation projects of thousands of companies and run millions of e2e tests weekly. We saw that it's very hard to debug end to end tests and it's a common reason companies abandon e2e tests.
We wrote "Root Cause" for the community in order to use our expertise from Testim to engage and promote puppeteer and playwright and in order to get better community feedback regarding what we see in tests.
Basically - currently most of the industry does manual QA and we wanted to encourage (in our small way) automation.
Thanks for the suggestion, there is a GitHub link going there that looks like the GitHub logo. I take it that isn't clear enough so I will ask the website team (btw: cool they built a landing page for an OS project for us!) to add a more prominent button.
Wow. I actually happen to work in a company where I have to maintain tons of scrapers and end up creating similar tool like this (scraper tend to fail for whatever reason and sometimes, the error tends to be very cryptic on what exactly the root cause of it).
There was one specific case I can't find right now, where Amazon literally took an open source project host it on top of AWS and then shipped it without even acknowledging the original Creator in any real capacity.
10 comments
[ 4.0 ms ] story [ 34.9 ms ] threadWe'd love (developer) feedback on this. This is the first (big'ish) open source tool that Testim makes.
Root Cause is a new open-source Node.js library, to help you visualize and troubleshoot your E2E Puppeteer & Playwright tests.
Check out our interactive demo: https://github.com/testimio/root-cause-interactive-demo/
At Testim.io - we see the automation projects of thousands of companies and run millions of e2e tests weekly. We saw that it's very hard to debug end to end tests and it's a common reason companies abandon e2e tests.
We wrote "Root Cause" for the community in order to use our expertise from Testim to engage and promote puppeteer and playwright and in order to get better community feedback regarding what we see in tests.
Basically - currently most of the industry does manual QA and we wanted to encourage (in our small way) automation.
Good luck with the project and have fun :)
Definitely looks like a cool tool
There was one specific case I can't find right now, where Amazon literally took an open source project host it on top of AWS and then shipped it without even acknowledging the original Creator in any real capacity.