|
161. Do You Write Actual Result Even For Successful Test Cases?
Date Posted: 06/27/2012
No, because a test case is successful only if actual result is the same as the expected result. Hence it is implied that if the test case is successful then the actual result is same as the expected result.
|
|
|
162. How Do You Understand Functionality Without Screens?
Date Posted: 06/27/2012
Ans: We get wireframe in the use case which helps a lot to understand the functionality.
|
|
|
163. How Do You Know That Your Test Cases Are Complete?
Date Posted: 06/27/2012
We follow two steps approach to ensure that test cases are completed
Reviews- It ensures that quality of the test cases is good
Requirement traceability matrix- It ensures that all the requirements have been covered through test cases.
|
|
|
164. What Is Difference Between Suspension And Stop Criteria?
Date Posted: 06/27/2012
Suspension is halting the testing temporarily with dissatisfaction because of situations like failure of smoke tests. Stop criteria is halting the testing with satisfaction that the product can be released.
|
|
|
165. What Is Wireframe?
Date Posted: 06/27/2012
Ans: A diagram which simulates the feel of actual screen.
|
|
|
166. Discuss Few Risks Software Projects Have?
Date Posted: 06/27/2012
Some of the example of risks in the project is
Team turnover
Domain of the project was new
Unexpected long leave of the employees
Knowledge of technology
Knowledge of products and requirements developing during the course of the project
Complexity of the project
Visibility of project.
|
|
|
167. Who Will Be Involved In RCA?
Date Posted: 06/27/2012
All the stake holders related to the work will be participated in RCA. For example if many defects are Re-opened in a particular module, developers of corresponding module, architect, test engineer, development and testing leads and managers will participate in RCA.
|
|
|
168. What Are The Techniques Used For Root Cause Analysis?
Date Posted: 06/27/2012
The techniques used for root cause analysis are
Cause factor tree analysis
Fishbone analysis
|
|
|
169. How Does Your Requirement Document Look Like?
Date Posted: 06/27/2012
Ans: It contains lots of Use cases where each use case explains one or more functionalities.
|
|
|
170. What Is Root Cause Analysis?
Date Posted: 06/27/2012
Root cause analysis is a systematic approach to get to the true root causes of any problem identified in the project. The primary aim of RCA is to identify the root cause of a problem in order to create an effective corrective action that prevents the problem from ever recovering.
|
|