Trade Me - Senior Software Test Analyst: Difference between revisions

From Vincents CV Wiki
Jump to navigation Jump to search
 
(3 intermediate revisions 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 the deployment of changes using Trade Me's continuous integration and continuous delivery processes
* 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 and peer test reviews
* Test planning, peer test plan reviews, executing test sessions, defect workflow.  
* Visual test tools (eg mind maps for test planning, and video capture of test sessions etc)
* Documentation of test practices.
* Jira for test plans, managing test sessions, and defect workflow. Confluence wiki for test practice documentation.
* 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 ==
At Trade Me is used the following tools and technologies
* [https://smartbear.com/product/ready-api/ '''ReadyAPI'''] for API testing & Automation using [https://groovy-lang.org/ '''Groovy''']
* [https://www.atlassian.com/software/jira '''Jira'''] for stories, test plans, session charters, bug tracking,
* [https://www.mindmup.com/# '''mindmup'''], [https://xmind.app/ '''Xmind'''], [https://simplemind.eu/ '''SimpleMind'''] for mind maps
* [https://www.atlassian.com/software/confluence '''Confluence'''] Wiki
* [https://www.mercurial-scm.org/ '''Mercurial'''] for source control management
* [https://www.protractortest.org/#/ '''Protractor'''] for UI automation
* [https://learn.microsoft.com/en-us/powershell/ '''PowerShell'''] scripts
* [https://icecreamapps.com/Screen-Recorder/ '''Icecream Screen Recorder'''] for recording test sessions
* [https://en.wikipedia.org/wiki/SQL_Server_Management_Studio '''Microsoft SQL Server Management Studio'''] for querying databases and profiling stored procedure calls
* [https://www.splunk.com/ '''Splunk'''] for monitoring and live error analysis and error graphs
* [https://www.telerik.com/fiddler '''Fiddler'''] and [https://www.wireshark.org/ '''Wireshark'''] for network protocol analysis
* Chrome extensions ([https://chromewebstore.google.com/detail/custom-javascript-for-web/ddbjnfjiigjmcpcpkmhogomapikjbjdk?pli=1 '''CJS Custom JavaScript'''], [https://chromewebstore.google.com/detail/bug-magnet/efhedldbjahpgjcneebmbolkalbhckfi '''Bug Magnet'''], [https://chromewebstore.google.com/detail/clear-session/maejjihldgmkjlfmgpgoebepjchengka '''Clear Session'''], Responsive Web Ruler,  WASP etc).
* Developer tools on tier 1 browsers


== Agile ==
== Agile ==
Line 37: 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) in Jira
* 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
== Tools and Technologies ==
At Trade Me is used the following tools and technologies
* [https://smartbear.com/product/ready-api/ '''ReadyAPI'''] for API testing & Automation using [https://groovy-lang.org/ '''Groovy''']
* [https://www.atlassian.com/software/jira '''Jira'''] for stories, test plans, session charters, bug tracking,
* [https://www.mindmup.com/# '''mindmup'''], [https://xmind.app/ '''Xmind'''], [https://simplemind.eu/ '''SimpleMind'''] for mind maps
* [https://www.atlassian.com/software/confluence '''Confluence'''] Wiki
* [https://www.mercurial-scm.org/ '''Mercurial'''] for source control management
* [https://www.protractortest.org/#/ '''Protractor'''] for UI automation
* [https://learn.microsoft.com/en-us/powershell/ '''PowerShell'''] scripts
* [https://icecreamapps.com/Screen-Recorder/ '''Icecream Screen Recorder'''] for recording test sessions
* [https://en.wikipedia.org/wiki/SQL_Server_Management_Studio '''Microsoft SQL Server Management Studio'''] for querying databases and profiling stored procedure calls
* [https://www.splunk.com/ '''Splunk'''] for monitoring and live error analysis and error graphs
* [https://www.telerik.com/fiddler '''Fiddler'''] and [https://www.wireshark.org/ '''Wireshark'''] for network protocol analysis
* Chrome extensions ([https://chromewebstore.google.com/detail/custom-javascript-for-web/ddbjnfjiigjmcpcpkmhogomapikjbjdk?pli=1 '''CJS Custom JavaScript'''], [https://chromewebstore.google.com/detail/bug-magnet/efhedldbjahpgjcneebmbolkalbhckfi '''Bug Magnet'''], [https://chromewebstore.google.com/detail/clear-session/maejjihldgmkjlfmgpgoebepjchengka '''Clear Session'''], Responsive Web Ruler,  WASP etc).
* Developer tools on tier 1 browsers

Latest revision as of 01:21, 10 May 2024

Dec-2014 - Aug-2016

Trade Me

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.

Tools and Technologies

At Trade Me is used the following tools and technologies

Agile

  • Spotify model of squads, chapters and guilds.
  • Small squads typically 2 Dev's, 1 Tester, ½ BA. The Product Owner (PO) gave direction but was considered outside the squad.
  • Squads are trusted to ask for assistance when needed
  • Squads perform regular retrospectives, are encouraged to use any mix of methodologies, and to continually look for new ways to improve their processes.

Testing

  • Followed Context Driven Testing principles. Considering a wide scope for testing, looking for anything that might surprise someone that mattered.
  • Shifted Left. Contributing early to discussions about UX, system architecture, and testability.
  • Efficient, focussed on high risks, leaving acceptable risks.
  • 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 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
Retrieved from ‘https://dirksonline.net/cvwiki/index.php?title=Trade_Me_-_Senior_Software_Test_Analyst&oldid=933’