Model Based Testing

1. Model-Based Testing
Kristian Karl, Spotify

2. 1983 Started programming
1994 Testing and automation
1998 Consultant
2004 Discovered Model-Based Testing
2005 Founded graphwalker.org
2010 Test Manager @Spotify

3. ●Subscribers: Over 30 million
●Active users: Over 80 million
●Revenue paid to rightsholders: $3bn
●Number of songs: Over 30 million
●Number of playlists: Over 1.5 billion
●Available in 58 markets
Andorra, Argentina, Austria, Australia, Belgium, Bolivia, Brazil, Bulgaria, Canada, Chile, Colombia,
Costa Rica, Cyprus, Czech Republic, Denmark, Dominican Republic, Ecuador, El Salvador,
Estonia, Finland, France, Germany, Greece, Guatemala, Honduras, Hong Kong, Hungary, Iceland,
Ireland, Italy, Latvia, Liechtenstein, Lithuania, Luxembourg, Malaysia, Malta, Mexico, Monaco, New
Zealand, Netherlands, Nicaragua, Norway, Panama, Paraguay, Peru, Philippines, Poland, Portugal,
Singapore, Slovakia, Spain, Sweden, Switzerland, Taiwan, Turkey, UK, Uruguay and USA.
Fun Facts

4. What is Model-Based
Testing?

5. [Very] [and unscientific] brief history of MBT
15 May, 1997
Software Quality Week Conference in May, 1997
http://www.geocities.ws/model_based_testing/sqw97.pdf
13:52, 30 December 2004
First edit in Wikipedia
https://en.wikipedia.org/wiki/Model-based_testing
I met Harry Robinson May 2004

6. What is MBT?

7. What is MBT?
● Models are the expected behavior of a
System Under Test.

8. What is MBT?
● Models are the expected behavior of a
System Under Test.
● Models are much simpler than the the reality.

9. What is MBT?
● Models are the expected behavior of a
System Under Test.
● Models are much simpler than the the reality.
● State models are a set of states and the
relationships between them.

10. What is MBT?
● Models are the expected behavior of a
System Under Test.
● Models are much simpler than the the reality.
● State models are a set of states and the
relationships between them.
● From the models, test are automatically
generated.

12. Not
authenticated

13. Login using
valid
credentials
Not
authenticated

14. Login using
valid
credentials
Authenticated
Not
authenticated

15. Login using
valid
credentials
Authenticated
Not
authenticated
VertexVertex

16. Login using
valid
credentials
Authenticated
Not
authenticated
VertexVertex
Edge

30. Use cases
● UI
● Payments systems
● Ads
● Workflow systems
● REST APIs
● Mobile
● Desktop
● Web
● Backend
● Real time systems

31. Why bother?

32. The incentive behind MBT

33. The incentive behind MBT
● MBT is [visual] collaborative.

34. The incentive behind MBT
● MBT is [visual] collaborative.
● Separation of test design from code
implementation.

35. The incentive behind MBT
● MBT is [visual] collaborative.
● Separation of test design from code
implementation.
● Test suites are generated
automatically.

36. The incentive behind MBT
● MBT is [visual] collaborative.
● Separation of test design from code
implementation.
● Test suites are generated
automatically.
● Lower maintenance - higher return of
investment.

37. Test execution

38. MBT execution

39. MBT execution
● Tests are generated automatically.

40. MBT execution
● Tests are generated automatically.
● Different test types can be generated.
- Smoke tests
- Functional
- Non-functional, exhaustive tests

41. Q&A

42. References
● http://graphwalker.org/
● https://github.com/GraphWalker/graphwalker-project
● https://github.com/GraphWalker/graphwalker-example
● https://github.com/spotify/python-graphwalker
● https://www.youtube.com/watch?v=idSgWX6rGdk
● https://www.youtube.com/watch?v=oWWiPGIFDAo