Paths

ByBelhassen Ouerghi

Taking back the control of GUI-Testing

OrganizationMotivation

PATHS and how it work

Conclusion

Discussion

Motivation

After 3 months and 16 presentations

What did we learned???

MotivationGUI testing is hardGUI testing is complex Old test metric don‘t fit for GUI testingGenerating efficient test cases is hardSo let‘s review the test oracleSo let‘s generate flexible test cases with

parametersSo let‘s repair test cases

we created more problems and lost the control of GUI testing

Why is this happen

To day

With PATHSPATHS stand for Planning Assisted Tester for

grapHical user interface Systems.

phase1:Tester give PATHS where to start and the goal to achieve.

phase2:In return PATHS give him back plans to achieve the defined goal.

There is no phase3

How it work

Deriving the operatorsSystem-interaction operator

Abstract operator

Unrestricted focus events

System interaction events

Unrestricted focus events

Restricted focus events

Deriving the operators

System interaction operatorsEdit_Cut , Edit_Copy and Edit_Paste

Abstract operator File_Open

Deriving the operators

Reducing the number of operators

Reduce the complexity of testing

Defining Precondition and effects

Defining Precondition and effects

Defining initial and goal state

Generating Plans

Low level Plan (Test case)

ConclusionGUI-testing with PATHS is a

cooperation work between Testers and PATHS.

Unlike others approaches and tools which only with a goal in mind (GUI-testing) start testing, we have now a concrete plan of how we could test.

ConclusionWe can now concentrate on what we want

to test insted of how we test.

Discussion

Where did you see disadvantages of PATHS?

How can we expand the functionality of PATHS?