What

• Testing sub-task for every user story

• Comments, tips, tricks, data, screenshots, risks, test results, test cases

• Additional information about testing of the specific user story

Why

• For purpose of proof our testing and results

  • When someone asks, how did you test it or how should I test it? We need to know the answer

• For purpose of a tutorial:

  • for QA - We need to test user story again in late phases /in regression tests and we need to know how

  • for customer - Customer will test feature ideally in the sprint acceptation and for sure in UAT. He needs to know how (how to set data, in which tables, what to calculate and where to find it)

  • For other QA - Hand over knowledge between QAs

• For purpose of a testing documentation

  • when feature is complex, we need to have some call or chat with CE/IE/SA/client. This additional information about testing, we need to store here (not in our private files).

• For purpose of reporting.

  • subtasks are easy to add into dashboard or report

  • we could have an overview about our testing

• For purpose of clear comments in user story

  • when we have some information about testing is not needed to put in comments in user story - it will be mess in the future. This testing informations should have be in separate space - subtasks

Where

• in every user story is button “create subtask“

...

• after click - new subtask is created

• name of this subtask should be “Testing“

...

How

• It is easy to manage status of the subtasks

  • Open - you have not started yet

  • In progress

  • Closed - testing has been done

• Better to have some additional information in JIRA, than everywhere else.

• Added value for us and for client

Examples

...