Agile testing focuses on a mindset of collaborative testing where the QA engineer helps customers write acceptance tests, coaches developers in testing techniques, and works as part of the development team. The QA engineer thinks about testability and tests that can run in continuous integration rather than working in isolation. Agile testing values automated unit and component tests over manual testing and focuses testing on the business logic and functionality rather than user interface or technology. It promotes practices like pair programming, code reviews, refactoring, and continuous integration to catch bugs earlier in development.

1. Agile
Testing
By Walmyr Filho
Senior Software Engineer in Test @GitLab
A quality culture in
the company’s core
business

3. What’s Agile Testing?

4. It’s a mindset for software engineering
it’s a different way of thinking about testing
it’s about re-thinking software testing

5. The QA engineer in the eXtreme programming discipline helps the customer to
choose and write acceptance tests, to automate them. He also serves as a
coach developer in software testing techniques. He is not responsible for finding
trivial bugs, this being responsibility from the developers themselves. He doesn’t
work isolated. Instead, he’s part of the team. He thinks in the tests that will go
to CI, and helps developers in pair to solve issues.
D.Wildt, D.Moura, G. Lacerda & R.Helm, XP - daily practices for software development

6. "And why not, he develops new features, he refactors the code, he fixes the
bugs he finds, and he always thinks about testability."
Walmyr Lima e Silva Filho

7. TRADITIONAL
AGILE

19. We value
automated tests
over
manual tests

20. Testing
quadrants
Focus in the business
Focus in the technology
Supportsthedevelopment
Critiquestheproduct
Q2 Q3
Q1 Q4
- Unit tests (FE/BE)
- Component tests
- Functional tests
- Wireframes
- Simulations
- Acceptance tests
- Usability tests
- Exploratory tests
- Performance tests
- Load tests
- Security tests
¢
¢
$
$

21. Testing pyramid
gui
UNIT
SERVICE
$$$
¢

22. Testing pyramid variation 1
$$$
¢
BE
SERVICE
gui
FE

23. Testing pyramid variation 2
$$$
¢
UNIT
Integration
api
gui

24. Testing pyramid variation 3
$$$
¢
visual
gui
UNIT
SERVICE
"Visual regression tests are test scripts that navigate through the application under test taking screenshot along
the way and looking for visual differences based on previously approved screenshots."

25. bug
FILTER
Any bug can get here
only bugs not reducible by unit
testing get here
only bugs irreducible by unit OR
integration tests get here
only the most subtle bugs reach
here
Only functionally undetectable bugs make it
to production!
Manual
GUI
Integration
Unit
Infinite set of
possible known
bugs

26. Manual
GUI
INTEGRATION
UNIT
ANTI
PATTERN 1

27. Test automators
developers
MANUAL TESTERS
Manual
ANTI
PATTERN 2
gui
integration/unit

28. TEST
MANAGER
TEST
COACH
Says “I”
Uses people
Does micromanaging
Is not willing to change
Takes credits
Is tied to a strict test schedule
Works with a traditional approach to testing
Considers test execution outside his scope
Restricts the team to execute predefined test
cases
Acts like an old school manager
Says “We”
Coaches people
Does not micromanaging
Is open to new ideas
Shares the team accomplishments
Motivates the team to work together
Develops an amplified testing mindset
Executes test with the team whenever possible
Gives testers freedom to perform exploratory testing
Acts like someone responsible for organizing the test
effort, to not overload the team.

29. Here are
some practices
I have experimented

30. Rotate
between
projects/teams

31. Create a test base
to be maintained
by the team

32. Pair programming &
Pair testing

33. Code review

35. Refactoring

36. RED
GREENREFACTOR
( 1 )
( 2 )( 3 )

37. Continuous integration/delivery/deployment pipelines

39. “Leave the campground cleaner than you found it.”

40. Coding dojos

41. Do not fight, instead, collaborate

44. Conclusion

45. Agile testing is about people working as a
team to develop software with quality in mind,
independent of roles, whether testers or
developers.

46. Walmyr Lima e Silva Filho
@walmyrlimaesilv
Thank you!