What test phases you execute as part of Agile?

Open 2 Answers 70 Views
1 2
Hi guys,

So in waterfall, We do Unit testing then System, System Intergration, UAT etc . From every stage to next stage we have entry and exist criteria. In Agile, we have a Sprint where you plan your dev work and you test. I want to know if its a 2 week sprint, Do you do ur Dev and then do all phases of testing ? or You do ur Dev and then just exploratory testing stratight on for that piece of requirements that u are delivering in that Sprint.

Now if you go by 2nd approach of doing exploratory testing, How do u manage test cases and test artifacts ? i.e. Every sprint you do exploratory testing Do you write test cases with detailed test steps upload them in your test tool, this case HP ALM or you write high level test cases only. ? Also from QA team prospetive once you are done with sprint, what test artificats you need to produce/provide ?



2 Answers

I have had experience of completely working Agile. In Agile, we have requirements frozen. From requirements, we create backlog items/stories. That backlog item will further be divided into tasks. So, while doing task out of backlog items, we will have tasks for testing as well. Like, analyzing the story, writing test cases, executing test cases. Also, we will make sure that we have separate QA environment set up.

So, initial stage, the QA team will pick up as many backlog items as possible and write test cases based on the story. Once the product is ready for testing, we will start executing test cases. Most of the time, in the two-week sprint, during IInd or IIIrd sprint, the QA team will get the first release of an app. The QA team will raise the bugs and work with the business team to figure out priorities.

During 6th or 7th sprint, we will see application becoming stable, so we start automating test cases for the stable part.

Usually, the application will move from Dev to QA to Stg or PROD.
answered by
commented by (22 points)
My impression was that changes are welcome in Agile but you are saying requirements are frozen ?
commented by (527 points)
When I say requirements are frozen. We will have basic requirements to kickstart the project. Throughout demos and sprints, we constantly keep the business team updated of our progress. They can change backlog item when and then required.
commented by (22 points)
So requirements are frozen for current Sprint. Make sense Thanks !
Btw where would solution design fit in this? Once you have requirements in Backlog, Do u design in same Sprint where Dev work happens ?
commented by (527 points)
edited by
If you talk about solution design and architecture of the solution, that will be done even before you start the sprint. Practically. When the sprint starts, we will know high-level architecture.

There may be small independent components, for which the architecture and design will be done during the sprint. But at a high level, we will know what should be the input and what should be the output.

Most of the time, we design sprints after creating POC and getting it approved from the client.

E.g. You have a project which does ETL. So, before the sprint starts we will know high-level architecture. We will have below questions answered to start the sprint.
1. How should we store data?
2. What are data sources?
3. What are data points?
4. How will data flow?
5. How are we going to implement business logic?
6. What kind of reporting tool are we going use?
7. How many reports should we be generating?

The answer to all those will give me Epics from where I can design features and Backlog items.
Small independent components we usually create a backlog item.

Agile process starts in the beginning of the project with continuous integration between application development and software testing outsourcing. Along with the incrementing development, the QA process is initiated by functional testing services.

Agile Testing Strategies:
1. Iteration: Under the first stage some initial setup tasks are performed like selecting people for testing, identifying testing tools, scheduling resources etc.
2. Development : Majority of the testing occurs during Construction phase. Under this phase, software testing services works on the prioritized requirement.
3. Release : It is the process of deploying the system successfully into production. Training of end users, support people and operational people comes under this phase.

The agile testing is based on four sections and it helps to understand how agile works:
1. Phase 1: In this phase, software testing services mainly works on the internal code quality i.e., mainly to perform Unit Tests and Component Tests.
2. Phase 2: In this phase software testing services mainly works on the requirements and they perform testing on main scenarios and workflows.
3. Phase 3: This phase shows the status of Phase 1 and Phase 2. In this phase, software testing services performs the Usability Testing, Exploratory Testing ans User acceptance testing
4. Phase 4: This phase is based on the non-functional requirements like application performance, security, stability. Software testing services performs Scalability testing, Data migration testing, Scalability testing, Load testing, etc. in this phase.

answered by (408 points)

Your answer

Your name to display (optional):
Privacy: Your email address will only be used for sending these notifications.
Anti-spam verification:
To avoid this verification in future, please log in or register.

Top Contributors