Trade Me - Senior Software Test Analyst: Difference between revisions
Jump to navigation
Jump to search
m
→Testing
m (→Testing) |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 15: | Line 15: | ||
* Context driven, tool assisted exploratory testing, using session and thread based techniques | * Context driven, tool assisted exploratory testing, using session and thread based techniques | ||
* Testing DB, UI, API, and architectural changes | * Testing DB, UI, API, and architectural changes | ||
* Leading | * Leading daily deployments to production | ||
* [https://www.splunk.com/ Splunk] system monitoring | * [https://www.splunk.com/ Splunk] system monitoring | ||
* Agile Squad Mastering (Facilitating project inception, story grooming, planning & estimation, retrospectives, daily standups, sprintboard) | * Agile Squad Mastering (Facilitating project inception, story grooming, planning & estimation, retrospectives, daily standups, sprintboard) | ||
* Test automation for API ([https://smartbear.com/product/ready-api/ ReadyAPI]/[https://www.soapui.org/ SoapUI]) and UI changes ([https://www.protractortest.org/#/ protractor]) using BDD with Gherkin syntax. | * Test automation for API ([https://smartbear.com/product/ready-api/ ReadyAPI]/[https://www.soapui.org/ SoapUI]) and UI changes ([https://www.protractortest.org/#/ protractor]) using BDD with Gherkin syntax. | ||
* Test planning | * Test planning, peer test plan reviews, executing test sessions, defect workflow. | ||
* Documentation of test practices. | |||
* Metrics driven development - using A/B Testing. | |||
* Metrics driven development - using A/B Testing | * Active contributor to test and agile guilds. | ||
* Active contributor to test and agile guilds | * New staff induction and junior staff support. | ||
* New staff induction and junior staff support | |||
== Tools and Technologies == | == Tools and Technologies == | ||
| Line 53: | Line 52: | ||
* Efficient, focussed on high risks, leaving acceptable risks. | * Efficient, focussed on high risks, leaving acceptable risks. | ||
* Used [https://www.agilealliance.org/glossary/three-amigos/ "Three Amigos"] to share and understand the problem, the solution, and the testing. | * Used [https://www.agilealliance.org/glossary/three-amigos/ "Three Amigos"] to share and understand the problem, the solution, and the testing. | ||
* Peer reviewed test plans (session based exploratory test charters) | * Peer reviewed test plans (session based exploratory test charters) | ||
* Test early for early feedback. ie. before dev work was completed. Aiding alignment, informing what is left to complete story, avoids re-work. | * Test early for early feedback. ie. before dev work was completed. Aiding alignment, informing what is left to complete story, avoids re-work. | ||
* Dev walk through - UI and code - review test plan | * Dev walk through - UI and code - review test plan | ||
* Demo to PO | * Demo to PO | ||
* Testers deployed to production during twice daily release windows | * Testers deployed to production during twice daily release windows | ||