EuroSTAR Software Testing Conference 2010 presentation on A Lean And Mean Approach To Model-Based Testing by Bert Zuurke. See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/

1. W20 -A Lean And Mean Approach To Model-Based Testing
Bert Zuurke
LogicaNetherlands

2. Presenting
•I will present a method :
–where the test scripts are generated from state transition diagrams
–and populated with test data from an Excel spreadsheet.

3. Including
•Demonstrating the use of open source tools
–For making state transition diagrams
–For generating test scripts
–For recording test results
–For automating tests

4. Not included
•This is not a tutorial on model based testing
•This is not a tutorial on how to test with state transition diagrams
•This is not a demonstration of all features of all the tools

5. Lean and mean
•Only open source
–Low costs to start with MBT
•Understandable and usable by any average tester

6. We all use models
Hmmm…
if I want to make a note
than I need to start
Notepad, enter my text,
save it and close Notepad
start
Save
Type text
Cancel
No

7. A state transition diagram
START State
Action
END State
Start
Startnotepad
Notepadrunning
Notepadrunning
Type text
Textentered
Textentered
Close window
Savethe changes?
Savethe changes?
No
Notepadnotrunning
Savethe changes
Cancel
Textentered
start
Save
Type text
Cancel
No
Start Notepad

8. And also depictured asSave
Type text
Cancel
No

9. How to test using state transition diagrams
Test scenario’s
All states
All Edges
Statistics:
-Edge coverage
-State coverage
-Test cases coverage

10. Where is the test data?

11. Endless edges? For every test case we need an extra edge

12. Why using Excel for test data? Action wordWhat to do
Arguments
= test data
Field labels

13. Use of excel
Edgename
Label
Type Text
1
Anote for Eurostar2010
2
Anotherline
3
Lastline to type

14. Putting it all togetherUse Model State Diagram for navigationUse Excel for the test data

15. Add a user interface
Model engineTestdata
Model state diagram
SOAP Request
SOAP Repley
Testdata
Test engine
•Offline mode
•Online mode
•Test automation
OperationModes
Navigation

16. Details

17. Demo YeDmake a transition diagram for Notepad
The following sheets are placeholders for the real demonstration.

18. Generate Excel worksheet

19. Generate an Excel worksheet (2)

20. Supply the test data

21. Run and have fun!

22. Automation
Test Automation can be added in the same way as with keyword driven tests
keywordtestdata3
testdata2
testdata1Step 1: action (enter testdata1 in field 1) Step2: action …
Notepad running
Text addedAdd Text
Edge name
testdata1
FuncAdd_text
send(“A note for Eurostar2010{ENTER}”)
Endfunc

23. Automation (2) Per step automatione.g. Start the applicationrun("Notepad.exe") Enter textsend(“A note for Eurostar2010{ENTER}”) Close the windowWinClose("Untitled -Notepad","") Cancel “Save the changes”; click No buttonControlClick("Notepad","","[CLASS:Button; INSTANCE:2]") Do not “Save the changes”; click No buttonControlClick("Notepad","","[CLASS:Button; INSTANCE:2]") How it is done:
1.Generate an autoitscript template
2.Add programming statements for each step inside the functions
3.Compile with engine
4.Test the test

24. Demo: generate the programming frameand add the statements to automate the test
Switch$name
case“e_Type_A”
$nextaction=e_Type-A($sproc,$itestcase,$aArguments)
case“e_Close”
$nextaction=e_Type-A($sproc,$itestcase,$aArguments)
…
End switch
Funca_Type_A($Proc,$testnr,$aData)
; do the action on the SUT
WinWait("Untitled -Notepad","")
If Not WinActive("Untitled -Notepad","") Then WinActivate("Untitled -Notepad","")
WinWaitActive("Untitled -Notepad","")
send()
Endfunc;e_Type_A

25. Run again and have more fun
This page is a placeholder for the real life demo

26. Extensions to the model
Use of guards and expressions
Edge can only be used if the condition is true:
Test_entered=true
Expressions can change the stateVariables:
Test-entered=true
Syntax:
Name[guard1;guard2;]/expression1;expression2

27. Run again and have more fun
This page is a placeholder for the real life demo

28. Summary
•I have demonstrated the use of open source tools
√ For making state transition diagrams
√ For generating test scripts
√ For recording test results
√ For automating test
√ Can be used for a start with Model based testing.
•Commercial tools add more features
•Better GUI
•More input models
•Data generation from class diagrams
•Integration with QTP and other tools

29. Thank you