Determine standard test automation tasks and meetings - NextensArelB/SwaggerGenerationTool GitHub Wiki

Objective By having standard test automation tasks on the board and meetings in the agenda, test automation will become standard way of working and activities will not be missed.

Who The whole team will be involved

What Determine which standard Test automation tasks should be created in (development) PBI tasks, examples are:

  • Handover Unit test
    • To create by DEV or QA
    • Add in the task the unit tests prepared for the PBI with logical, functional naming
    • Discuss scope and content of the unit test between DEV and QA
    • Add missing unit test
  • API test automation
    • To create by the one responsible for API test automation
    • When a PBI is containing API (new or update), API tasks should be on the board to create new tests or to maintain existing tests
    • Scope and coverage is amongst others based on what is already covered in unit tests
  • UI test automation
    • To create by the one responsible for UI test automation
    • When a PBI is containing UI (new or update), UI tasks should be on the board to create new tests or to maintain existing tests
    • Scope and coverage is amongst others based on what is already covered in unit tests and API tests
  • E2E test
    • To create by the one responsible for E2E
    • When a feature is complete, E2E tasks should be on the board to create new tests or to maintain existing tests
    • Scope and coverage is amongst others based on what is already covered in unit tests, API and UI
    • E2E test should be as simple as possible

Determine which standard Test automation meetings could be scheduled on a regular basis, examples are:

  • Sprint test automation demo
    • To be organized at the end of the sprint
    • Demo by DEV and QA involved in testautomation to the whole team to demo what is covered where
    • Add missing tests if required

When When a new team is set up or for existing teams once every year to determine if the agreed approach is still valid and up to date

How

  • Organize a team meeting
  • Discuss, agree and register the outcome in the team wiki

Tools

  • Wiki: use the team wiki to store what has been agreed
  • DoR: update the DoR template with criteria related to test automation
  • DoD: update the DoD template with criteria related to test automation
⚠️ **GitHub.com Fallback** ⚠️