Agile QA and Testing process
-
Upload
gloria-stoilova -
Category
Technology
-
view
61 -
download
1
Transcript of Agile QA and Testing process
![Page 1: Agile QA and Testing process](https://reader035.fdocuments.us/reader035/viewer/2022081506/55d2a91ebb61eb9a6e8b47c0/html5/thumbnails/1.jpg)
Process Overview
Gloria Stoilova – SCRUM Product OwnerGfK – BA Team Bulgaria
![Page 2: Agile QA and Testing process](https://reader035.fdocuments.us/reader035/viewer/2022081506/55d2a91ebb61eb9a6e8b47c0/html5/thumbnails/2.jpg)
Agile – iterative development methodology, where requirements evolve through collaboration between the customer and self-organizing teams. Agile business approach aligns development with customer needs.
![Page 3: Agile QA and Testing process](https://reader035.fdocuments.us/reader035/viewer/2022081506/55d2a91ebb61eb9a6e8b47c0/html5/thumbnails/3.jpg)
A tester is not the one who can not program and causes breaks only.
Inadequate use of the person’s potential and experience.
A tester does not participate in planning.
A tester’s work starts after the functional development.
![Page 4: Agile QA and Testing process](https://reader035.fdocuments.us/reader035/viewer/2022081506/55d2a91ebb61eb9a6e8b47c0/html5/thumbnails/4.jpg)
Simplicity of principles and apparent easiness of their employment.
More transparent communication with the customer and accurate planning.
Agile is in fashion. Examples of other teams.
![Page 5: Agile QA and Testing process](https://reader035.fdocuments.us/reader035/viewer/2022081506/55d2a91ebb61eb9a6e8b47c0/html5/thumbnails/5.jpg)
Difficulty of leaving the traditional understanding of roles.
Resistance to changes. In the adaptation phase the basic
Agile principles may be destroyed. Agile is not a panacea to solve all
the problems. Agile principles just reveal the problems, and it is people who are to solve them.
![Page 6: Agile QA and Testing process](https://reader035.fdocuments.us/reader035/viewer/2022081506/55d2a91ebb61eb9a6e8b47c0/html5/thumbnails/6.jpg)
A tester is a team member! The tester’s experience in
development should be fully used.
The tester’s functions are largely determined by the tester himself.
Participation in planning and requirements analysis.
![Page 7: Agile QA and Testing process](https://reader035.fdocuments.us/reader035/viewer/2022081506/55d2a91ebb61eb9a6e8b47c0/html5/thumbnails/7.jpg)
Start of a sprint – start of testing. Testing activities are the same as in other
methodologies. Testing tasks – usual sprint tasks. All the team is responsible for the result,
including quality. Testing tasks – common tasks of all the
team. Maximum communication. Provide continuous feedback.
To the customer. To the programmers.
![Page 8: Agile QA and Testing process](https://reader035.fdocuments.us/reader035/viewer/2022081506/55d2a91ebb61eb9a6e8b47c0/html5/thumbnails/8.jpg)
Test planning. Build acceptance testing. Functional testing. Regression testing. Demo testing. Test automation.
![Page 9: Agile QA and Testing process](https://reader035.fdocuments.us/reader035/viewer/2022081506/55d2a91ebb61eb9a6e8b47c0/html5/thumbnails/9.jpg)
Analysis of requirements and risks; test planning.
Test automation. Setting up test environments. Preparing the necessary
documentation. Work with external resources. Providing help to developers.
![Page 10: Agile QA and Testing process](https://reader035.fdocuments.us/reader035/viewer/2022081506/55d2a91ebb61eb9a6e8b47c0/html5/thumbnails/10.jpg)
Lack of testing resources. Inefficient test planning. A lot of manual testing. Inefficient testing process. Increasing functional for
regression testing.
![Page 11: Agile QA and Testing process](https://reader035.fdocuments.us/reader035/viewer/2022081506/55d2a91ebb61eb9a6e8b47c0/html5/thumbnails/11.jpg)
Detailed test planning. Automation, possibly with the
developers’ help. Increased unit test code coverage. Implementation of stabilization
sprints. Increase in the amount of testing
resources.
![Page 12: Agile QA and Testing process](https://reader035.fdocuments.us/reader035/viewer/2022081506/55d2a91ebb61eb9a6e8b47c0/html5/thumbnails/12.jpg)
Less risk of compressed test period.
Test all the time, not just at the end.
Work together as one team towards a common goal.
![Page 13: Agile QA and Testing process](https://reader035.fdocuments.us/reader035/viewer/2022081506/55d2a91ebb61eb9a6e8b47c0/html5/thumbnails/13.jpg)
THANK YOU FOR YOUR TIME! THANK YOU FOR YOUR TIME!