Brief on the timeline of Sprint can be found here: Scrum in Jira & Confluence | Sprints
These testing activities are integrated into the sprint's workflow, ensuring that testing is ongoing and aligned with development efforts. Agile testing practices aim to provide rapid feedback, identify issues early, and maintain a high level of software quality throughout the development process.
Test Planning
Before the sprint begins, the testing team, in collaboration with the product owner and development team, plans the testing activities for the upcoming sprint. This includes defining what features or user stories will be tested and outlining the test strategy.
Test Estimation
Test estimation is the process of predicting the time, effort required to complete testing activities of that user story or feature being discussed.
More info here: Task Estimation , Am I providing the right "Estimates"? - Testing Center of Excellence - Confluence (atlassian.net)
3 Amigos
3 Amigos - Youtap Tech Indonesia - Confluence (atlassian.net)
Test Case Design
Testers create detailed test cases based on the acceptance criteria defined for each user story or feature.
Test Data Preparation
Testers prepare the necessary test data, which may include setting up test environments, databases, or any other data sources required for testing.
Test Execution
During the sprint, as developers complete their work on user stories or features, testers start executing the test cases. They systematically go through each test case, following the specified steps, and record the results.
Regression Testing
As new code is added during the sprint, it's crucial to perform regression testing to ensure that existing functionality has not been affected.
Defect Reporting
If testers encounter any defects (bugs) during the testing process, they document them in JIRA. These issues are then prioritized and shared with the development team for resolution.
Test Automation
Automation is encouraged to increase testing efficiency. Testers will develop and maintain automated test scripts for those features/ user stories of the previous sprint, targeting the critical test cases.
Continuous Integration (CI)
As code changes are integrated into the shared repository, CI tools trigger automated builds and tests. This helps catch integration issues early and ensures that the codebase remains in a stable state.
Daily Stand-ups
Testers participate in daily stand-up meetings to discuss progress, highlight any testing-related challenges or roadblocks, and ensure alignment with the development team.
Acceptance Testing
Towards the end of the sprint, user acceptance testing (UAT) may be performed. This involves end-users or client representatives validating that the software meets their requirements and expectations.
Sprint Review
At the sprint review meeting, the testing team may present their findings and demonstrate the tested functionality to stakeholders. Any defects or issues are discussed for resolution.
Testers will also take this opportunity to mark-out the critical test-cases, as a foundation for increasing our automation capability.
Test Reporting
Testers generate test reports summarizing the test results, including pass/fail status, defect statistics, and any relevant metrics. These reports provide visibility into the quality of the sprint's deliverables.
Sprint Retrospective
In the sprint retrospective, the testing team reflects on their own processes and identifies areas for improvement. This includes discussing testing-related practices and tools.