Are there any special techniques to test navigation of AUT? it is only manual or can be automated? When do we say that navigation is consistant? Or it is just tester's judgement/opinion which is accepted as a test outcome?
Printable View
Are there any special techniques to test navigation of AUT? it is only manual or can be automated? When do we say that navigation is consistant? Or it is just tester's judgement/opinion which is accepted as a test outcome?
I am not getting your question.
Do you mean AUT (Application Under Test), or something else?
Yes, the question is how do we prepare test cases for navigation of an application? What should we look for?
See for navigation to test, the best approach is to draw a DFD where every node represent a unique page, and then as many pages we can navigate through it will be outgoing arrows from that node to the respective destination node, and as many page can point that page for navigation will be incoming arrows to that node.
In this way you can test for navigation as well for orphan pages also.You can use traceability matrix also to track the success of test.
The Navigation testing comes under User Interface Testing.:eek:
It can’t be automated, so only manual testing is possible for navigation testing. Navigation of various modules and features of a software system is defined in the front-end design. Test cases can be written basing on these definitions.:D
The possible test cases could be based on, availability and accessibility of options at the right place and at the right time, the acceptable level of navigation depth, availability and accessibility of options according to the user privileges. And more depending on front-end design.:cool: