In my scrum team, as a tester, I'm responsible for the test work to be done. Most of that test work is done manually. We need to automate those test cases. But, when? And how? The developers and and the tester can do a lot together. Some times we test together. Some times we program together. Some times I'm on my own, testing or creating/writing automation scripts. In my talk I will share my experiences what I'm doing with my developer colleagues. From the moment we start development on the feature (Epic or user story) up until we ship it. We explore, build and test the feature. Based on that we create scripts for automation on various levels. From unit test level up until end to end testing. Take aways from this session are: - How to work together with your developer(s) - Motivate your stakeholders to work this way - Give tester a way to participate in coding and learn from the experience - Provide Agile coaches a way how to set up automation in a scrum team

1. Pair testing?
Pair programming?
Working together with the developers
Simon ‘Peter' Schrijver
TesT-PRO
@simonsaysnomore
p.schrijver@test-pro.nl

2. SPONSORS & PARTNERS

3. Who Am I
✦ Simon ‘Peter' Schrijver
✦ Age : 52
✦ Coming from The Netherlands
✦ Married with children
✦ Independent Tester
✦ Since 2005
✦ Founding Member of DEWT
✦ Current : Software Design
Engineer in Testing

4. I'm a tester, and …
✦ I’m challenged to extend my skills beyond testing.
✦ I’m challenged to support my scrum team.
✦ That is, I have to learn to program.
✦ The industry is sort of demanding this ……
"A tester must code"

5. Be aware
If you require a tester to start to program
You will get an average programmer
But you will loose an excellent tester

6. That is not all
Which programming language do I need to learn?

7. Working together
Knowing (or learning) the programming language
your developers are working with, you can help as a
tester to write some code with your developer.
During the software development life cycle a lot of
development and test work is done. Some of this
work have a common interest.

8. Some context
A developer helps a tester and vice versa
Are we doing Pair Programming or Pair Testing?

9. Pair Testing
✦ When a tester asks a developer to look into a problem
the tester has encountered in the code, you look
together if this is just a test error or a real problem.
✦ In this situation you can speak of pair testing.
✦ The outcome of the pair session is information (is it a
bug or not).
✦ The tester is the person in control.

10. Pair Programming
✦ When a developer is asking the tester to look into a
feature and to see how it works, you can end up in a
session where some code is rewritten or even new
code is created.
✦ In this situation you can speak of Pair Programming.
✦ The outcome of the pair session is new/changed code.
✦ The developer is the person in control.

11. Unit test
Unit integration test
UI test
UI integration test
End to end test, virtualised
End to end test, real
Regression test
Exploratory test
Tester
Developer
Tests to be done (functional)

12. Unit test
✦ Smallest testable part of an application.
✦ Written and run by developers.
✦ Easy to execute.
✦ Gives specific data to a developer.
✦ Early feedback

13. Unit test
The objective in unit testing is to isolate a unit and
validate its correctness
✦ But these units have to work together
✦ One unit depends on another unit
✦ Combine units to create a new test.

14. Unit Integration test
✦ Two or more units ‘connected’ with each other.
✦ Integrated Unit.
✦ Relations between units need to be tested.
✦ When test cases fail, it makes less clear which
component is causing the failure.
✦ Troubleshooting done with the information how single
units are working.

15. UI test
✦ All functionality on an User Interface (UI).
✦ No interaction to next screen or peripheral system.
✦ All units or integrated units within the UI are covered
and working.
✦ Combined they will provide an output to:
❖ Another User Interface (UI).
❖ Peripheral system.

16. UI Integration test
✦ Two or more user interface (UI) screens ‘connected’
with each other.
✦ Relations between user interface screens need to be
tested
✦ Stay within the App
✦ Stop at an external interface
✦ Not an End to End scenario.

17. End to End test, virtual
✦ Complete End to End (E2E) flows of core processes
✦ Interaction with virtual peripherals
✦ Always in control
✦ Maintenance needed
✦ Virtualisation created by …

18. End to End test, real
✦ Complete End to End (E2E) flows of core processes.
✦ Interaction with real systems.
✦ Automation in place, i.e. regression tests
✦ Request for availability of real systems.
✦ Use virtual environment as your reference.

19. Regression test, not automated
✦ Automation not in place for End to End with real
systems:
❖ New interface, automation needs to be developed (must be
soon available)
❖ Complex interface, difficult to automate
❖ Peripheral system operates on different platform (e.g.
Responsive Web).
❖ Other Mobile Apps

20. Regression test, improvements
✦ Automation in place for End to End with real systems:
❖ Add new regression tests as new functionality is
introduced.
❖ Maintain existing regression tests.
❖ Delete regression tests when no longer needed.

21. Exploratory test
✦ Test done by yourself.
✦ Based on new or changed functionality.
✦ “Where can I find problems”.
✦ Risk based approach.

22. Exploratory test, output
✦ Created new/changed tests.
❖ Main path(s).
❖ Alternative path(s).
❖ Error.
✦ Regression tests.
✦ New/changed tests for automation.

23. Test opportunities
✦ Upper layer(s) will offer
feedback to lower
layer.
✦ Lower layer(s) will
provide information to
upper layer.
Unit test
Unit integration test
UI test
UI integration test
End to end test, virtualised
End to end test, real
Regression test
Exploratory test
Tester
Developer

24. Responsibility
Developer in the lead,
Tester will support
Tester in the lead,
Developer will support
Tester responsibility
Unit test
Unit integration test
UI test
UI integration test
End to end test, virtualised
End to end test, real
Regression test
Exploratory test

25. Automation or not
Automation
Test
Unit test
Unit integration test
UI test
UI integration test
End to end test, virtualised
End to end test, real
Regression test
Exploratory test
Semi-automated

26. Dependencies
Unit test
Unit integration test
UI test
UI integration test
End to end test, virtualised
End to end test, real
Regression test
Exploratory test
No dependancies
with peripheral
systems

27. Time line
But there is a mistake
Unit Test
Unit Integration Test
UI Test
UI Integration Test
End 2 End Test, Virtual
Regression Test
Exploratory Test
End 2 End Test, Real
Unit Test
Unit Integration Test
UI Test
UI Integration Test
End 2 End Test, Virtual
Regression Test
Exploratory Test
End 2 End Test, Real

28. Time line
Unit Test
Unit Integration Test
UI Test
UI Integration Test
End 2 End Test, Virtual
Regression Test
End 2 End Test, Real
Exploratory Test

29. Application life cycle
Unit Test
Unit Integration Test
UI Test
UI Integration Test
End 2 End Test, Virtual
Regression Test
End 2 End Test, Real
Exploratory Test
Design Development Test Deploy Maintenance

30. Continuous Development & Test
Unit Test
Unit Integration Test
UI Test
UI Integration Test
End 2 End Test, Virtual
Regression Test
Exploratory Test
End 2 End Test, Real
✦ We test during the whole application life cycle, we test
continuously
✦ We develop during the whole application life cycle, we
develop continuously

31. But there is a constraint in my role
For me as a mobile app tester, I have an extra
challenge. Being the only tester in my team, I have
to learn two programming languages

32. Unit test - code example

33. UI test - code example

34. End-to-End test - code example

35. Unit test - code example

36. UI test - code example

37. End-to-End test - code example

38. End-to-End test - code example

39. Virtualisation - Mock ‘the Back End’
✦ Simulate responses
✦ Always ‘access'
✦ Early development
✦ Use it as a reference

40. Virtualisation - Mock ‘the Back End’

41. Automation
✦ We test together
✦ We develop together
✦ To have automation in place
✦ Decide which tests needs to be automated (if possible)
✦ As a part of our development process
✦ The automation code is part of the development code

42. Working together
✦ Share the same tools
✦ Share the same repository
✦ Help each other with their work
✦ Easy communication
✦ Understand each others needs
✦ Understand each others problems

43. Working together
✦ Developers skill; how to solve a problem
✦ Testers skill; find out where it can go wrong
✦ Our mission is different, but we share the same vision
✦ To build software which can be deployed at any
moment in time checked by the automation scripts
which help us to make an informed decision.

44. Info
✦ Pair Testing
✦ The Many Advantages of Pair Testing (URL : https://
www.stickyminds.com/article/many-advantages-pair-testing)
✦ Pair Programming
✦ 7 Pair Programming Tips for Beginners (URL : https://
blog.gurock.com/7-pair-programming-tips-for-beginners/)
✦ Paring
✦ 5 Ways to Pair Developers with Testers (URL : https://
www.stickyminds.com/better-software-magazine-article/5-ways-pair-developers-testers)

45. The developers I work with

46. Conclusion
✦ Tester can make a conscious choice of learning a
coding language
✦ Make sure the choice you made adds value to your the
team
✦ If you want maximum support, learn the language your
programmers work with
✦ You can work together in various situations as a pair,
wether it is testing or programming (for automation)

47. Simon Says
Thank You
Do you have any questions?
@simonsaysnomore
p.schrijver@test-pro.nl

48. SPONSORS & PARTNERS