Creating a common test approach DEWT5 Peer Conference

Creating a common test approach DEWT-5 Peer Conference Massimo D’Antonio Simon P. Schrijver

A problem to solve • One project – one tester • Personal approach • Missing guidelines for common approach Need for a common strategy to test

How? Let’s check on the Internet! Found an interesting article by Katrina Clokie: “Creating a common test approach across multiple teams”

What did we do?

rt Test repo

rt Test report

Create Unit test s rt Test report

rt Test repo w Peer revie Test report st Sharing te artifacts Create Unit test s st Sharing te artifacts

Test report Sharing test artifacts Peer review Create Unit tests

Everyone Bug reporting: it should be always done: formal (jira ticket) when necessary, always via talk with devs or POs Gathering and sharing requirements: It should always be done, trying to suggest methods for effective sharing of knowledge across the team (involve POs and Devs as much as possible) Regression testing: it should be done every time allocating the necessary time if not allowed by time constraints or PO's judgment, highlight the risk to the PO Sharing: Test cases/test results/session reports/mindmaps/Soap. UI projects. . . all the artifacts, defined above, created before/after/during tests execution should be saved and shared with necessary documentation for their use/interpretation […] SOMETIMES Demos: on request of the stakeholders, usually a rerun of the tests done Communicate support/customer: new features should be described/demoed to Customer Support [. . . ]

That's it? No! New testers in the testing team Need for consensus Proposed a discussion

References • URL : http: //katrinatester. blogspot. co. nz/2014/08/cre ating-common-test-approach-across. html