Download presentation
Presentation is loading. Please wait.
Published byEthan Lambert Modified over 6 years ago
1
Back Tracking of Issues –Before Escalating to Developer
Microsoft Connect 2016 11/28/2018 4:14 PM Back Tracking of Issues –Before Escalating to Developer Mekala Ramesh -Lead QA & Product Support © 2016 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
2
What is back tracking in general?
11/28/2018 4:14 PM What is back tracking in general? Word itself has the meaning Erroneous in the flow Go back to the travelled way In simple words “Detecting the problem with exact root cause” © 2016 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
3
In a software testing context
It is a main essence for testing Based on experience bug reporting skill differs Novice Intermediate Expert Less Risk
4
Issue back tracking an example
Generally software has three layers, UI Web Service Database
5
UI Layer Binding issue Look for the console error, if any
Browser issue The exception is not handled properly
6
Service Layer Method Identification GET POST
7
Database layer Log files
8
Thank you !!! When you don't identify and reduce risks at the beginning of a project, they can often become issues later on. Make sure you understand your risks early. Learn from previous projects, and benefit from the team's past experiences. This way, you'll have fewer issues to manage as you move forward.
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.