Trade Me - Senior Software Test Analyst

From Vincents CV Wiki
Jump to navigation Jump to search

Dec-2014 - Aug-2016

Trade Me

skills Online Auction Platforms, Context Driven Testing, Exploratory Testing,
Visual Modelling, Agile (Scrum, Kanban, Squad Master), Testability,
Accessibility, Observability, Jira, Confluence, Web App, Mobile App,
API Testing, PowerShell, Splunk, ReadyAPI, A/B Testing, XMind,
Staff Mentoring & Induction, SQL & SQL Server Management Studio (SSMS)

Trade Me is the iconic consumer auction website in NZ, one of the most popular websites accessed from NZ. Trade Me are renowned for their agile implementation, and have a well established test guild.

I was a Test Analyst with the Motors group, in a small cross functional agile squad, testing software changes to the iconic NZ Trade Me website focussing on the Motors page and features.

Squads owned the full technology stack to deliver new features and projects, from inception through to deployment in production. They were responsible for the story's design, implementation, testing, and deployment.

References

Responsibilities

  • Context driven, tool assisted exploratory testing, using session and thread based techniques
  • Testing DB, UI, API, and architectural changes
  • Leading daily deployments to production
  • Splunk system monitoring
  • Agile Squad Mastering (Facilitating project inception, story grooming, planning & estimation, retrospectives, daily standups, sprintboard)
  • Test automation for API (ReadyAPI/SoapUI) and UI changes (protractor) using BDD with Gherkin syntax.
  • Test planning, peer test plan reviews, executing test sessions, defect workflow.
  • Documentation of test practices.
  • Metrics driven development - using A/B Testing.
  • Active contributor to test and agile guilds.
  • New staff induction and junior staff support.

Testing

  • Followed Context Driven Testing principles. Considering a wide scope for testing, looking for anything that might surprise someone that matters.
  • Shifted Left. Contributing early to discussions about UX, system architecture, and testability.
  • Efficient, focussed on high risks, leaving acceptable risks, with great Observability to detect problem early.
  • Used "Three Amigos" to share and understand the problem, the solution, and the testing.
  • 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 a story, avoids re-work.
  • Dev walk through - UI and code - review test plan
  • Demo to PO
  • Testers deployed to production during twice daily release windows