Page History

...

How do you then implement testing in this scenario?

Mainly with manual testing

Suppose that you are working in version "XPTO" and you want to implement testing in it, in order to make sure that the features you deliver are correct.

...

If this is the case, then you have Sprints and you can them as basis to define some scope.

Mainly with manual testing

Suppose that you are working in sprint "X" and you want to implement testing in it, in order to make sure that the features you deliver are correct.

...

1. create "requirements" (e.g. Story, Epic or other similar issue types) and associate them with sprint X

2. create one or more Tests for validating each requirement;  In this case your automated tests will be specified before the actual implementation of the requirement is done, if you're following TDD, or after the requirement is implemented, in the worst case scenario.

    

   Cucumber automated tests can be

   created in the same manner

   specified in JIRA (and implemented in code), while other automated tests will be written in code and either linked to the requirement directly in the code or manually after importing their respective results
   organize your Tests either in lists (i.e. Test Set issues) or in folders, so you can easily pick them afterwards whenever you need to

3. create executions or plans. Test Sets can also be used as a way to indirectly validate requirements, since you can link them to requirements using the "tests" issue link 
   create at least one Test Plan with the Tests you want to validate in sprint X; don't forget to assign the Test Plan with sprint X. Having a specific Test Plan for tracking the regression testing may probe to be useful.
   
   

   Info
   title Learn more
   Pleas Please see our Tips for planning tests, which explore the different possibilities you have concerning planning, including in Waterfall and Agile methodologies.

4. from the Test Plan, create one or more planned Test Executions with the Tests that you want to execute. Each Test Execution is an abstraction of a "task for running some Tests" and can be assigned to specific users. Inside the Test Execution invidividual Test Runs may be reasssigned to some other users;

5. 
   

6. in the CI tool (e.g. Bamboo, Jenkins), run the automated tests and report them to Xray, associating them to the respective Test Plan. In Xray, a Test Execution associated with the Test Plan will be created; it will contain the results for each automated Test. Test entities will be created automatically from the results, if they have not yet been created before
7. analyze the results execute the Tests (i.e. Test Runs), in the scope of each Test Execution. For each failed Test Run, report the status of each step or the overall result if you prefer; you may need to manually create defects for failed Test Runs, which you can do immediately from a given step or globally at Test Run levelfrom the Test Plan, create new Test Executions to validate all Tests or just with the ones that are, for example, failingin the execution details screen of the respective Test Run
8. use the prompt feedback of Test Plan and Test Execution issues along with reports to track the progress of your testing; built-in reports, such as the Traceability Report, Overall Requirment Coverage and others, along with custom dashboards can be used to track the relevant information such as open defects

...