Navigational Steps When test engineer joins into project he will be received URL(s) and supported documents related to application from the lead or existing team member. Lead will leave him 2 to 3 days request him to perform few operations to understand the flow of screens to have basic idea on the functionality. At this stage, many test engineers get bored or go to sleep when lead wouldn’t keep eye on him. A short time test engineers perform adhoc operations on the application to understand the functionality though the documents shared. If navigation document has prepared and shared to the test engineer, this document would help to perform step by step operations specified for understanding complete feature list. With this approach, lead will saves existing team members time, cut down the KT time and reduce lot of dependency on the existing team members.
Navigational steps document, It's all about the navigation of the application and it is not intended to stand-alone; rather, it is primarily provided as reference material for test engineer in the training and also facilitate to engineers to avoid writing field level steps in test case document.
Navigational document: we update sequence of steps or operations for each action (add/modify/delete buttons etc) that lead to a specific destination/ functionality in the interface. This document helps to user who may not have clear idea on the functionality.