hi @quantuminfo thank you for sharing this piece. i like the excerpt.
I am a tester my self and would like to mansion a process flow which i find more engaging and more fruitful .
As a QA i get involved at the very beginning of the process (Requirement gathering). Tests gets developed right after the requirements are frozen and it is sent to the developers to serve as a blueprint of the feature. Unit tests are written and perform by the Developers. You have mension that E2E Tests should get handled by the Developers but i think End to End flow tests are good if it's in Testers hand as developers work only on the specific or portion of the requirement but QA is involved in entire software life cycle.
Would love to here your Views. Thanks.
Thanks mate, for your advice, happy to hear more about your process.
I have been on steemit for a few days now. Finally a post about software testing. You made my day today buddy... :) Thanks again.
So when you write your tests before the developers start, how do you write them? Selenium?
First wire frames and UX gets developed and then Manual test gets written based on them. This manual tests are sent to the developers and in parallel Automation test cases are written in BDD using cucumber (Based on manual tests).
As you can see Manual tests are of paramount importance and each and every feature gets tracked to BDD tests these tests are in sync with manual tests which in return are linked to the requirement.
Hope this helps. Sorry for the delay. :-)
Have you seen anyone use stuff like https://screenster.io/image-and-screenshot-comparison-tools-for-ui-testing/ and https://www.testing-whiz.com/blog/how-image-comparison-works-in-website-testing
I haven't used anything for UI comparison. UI/UX team is generally involved in UI testing. They tests Html Ui with the actual design which are prepared in Photoshop(or any other tool). pixel to pixel comparison is too much of a hassle. It's good if design team test it.