111. What is the difference between UAT (User Acceptance Testing) and System testing?
System Testing: System testing is finding defects when the system under goes testing as a whole, it is also known as end to end testing. In such type of testing, the application undergoes from beginning till the end.
UAT: User Acceptance Testing (UAT) involves running a product through a series of specific tests which determines whether the product will meet the needs of its users.
112. Mention the difference between Data Driven Testing and Retesting?
Retesting: It is a process of checking bugs that are actioned by development team to verify that they are actually fixed.
Data Driven Testing (DDT): In data driven testing process, application is tested with multiple test data. Application is tested with different set of values.
113. What are the valuable steps to resolve issues while testing?
Record : Log and handle any problems which has happened
Report: Report the issues to higher level manager
Control: Define the issue management process
114. What is the difference between test scenarios, test cases and test script?
Difference between test scenarios and test cases is that
Test Scenarios: Test scenario is prepared before the actual testing starts, it includes plans for testing product, number of team members, environmental condition, making test cases, making test plans and all the features that are to be tested for the product.
Test Cases: It is a document that contains the steps that has to be executed, it has been planned earlier.
Test Script: It is written in a programming language and it's a short program used to test part of functionality of the software system. In other words a written set of steps that should be performed manually.
115. What is Latent defect?
Latent defect: This defect is an existing defect in the system which does not cause any failure as the exact set of conditions has never been met
116. What are the two parameters which can be useful to know the quality of test execution?
To know the quality of test execution we can use two parameters
Defect reject ratio
Defect leakage ratio
117. What is the function of software testing tool "phantom"?
Phantom is a freeware, and is used for windows GUI automation scripting language. It allows to take control of windows and functions automatically. It can simulate any combination of key strokes and mouse clicks as well as menus, lists and more.
118. Explain what is Test Deliverables ?
Test Deliverables are set of documents, tools and other components that has to be developed and maintained in support of testing.
There are different test deliverables at every phase of the software development lifecycle
Before Testing
During Testing
After the Testing
119. What is mutation testing?
Mutation testing is a technique to identify if a set of test data or test case is useful by intentionally introducing various code changes (bugs) and retesting with original test data/ cases to determine if the bugs are detected.
120. What all things you should consider before selecting automation tools for the AUT?
Technical Feasibility
Complexity level
Application stability
Test data
Application size
Re-usability of automated scripts
Execution across environment
121. How will you conduct Risk Analysis?
For the risk analysis following steps need to be implemented
a) Finding the score of the risk
b) Making a profile for the risk
c) Changing the risk properties
d) Deploy the resources of that test risk
e) Making a database of risk
122. What are the categories of debugging?
Categories for debugging
a) Brute force debugging
b) Backtracking
c) Cause elimination
d) Program slicing
e) Fault tree analysis
123. What is fault masking explain with example?
When presence of one defect hides the presence of another defect in the system is known as fault masking.
Example : If the "Negative Value" cause a firing of unhandled system exception, the developer will prevent the negative values inpu. This will resolve the issue and hide the defect of unhandled exception firing.
124. Explain what is Test Plan ? What are the information that should be covered in Test Plan ?
A test plan can be defined as a document describing the scope, approach, resources and schedule of testing activities and a test plan should cover the following details.
Test Strategy
Test Objective
Exit/Suspension Criteria
Resource Planning
Test Deliverables
125. How you can eliminate the product risk in your project ?
To eliminate product risk in your project, there is simple yet crucial step that can reduce the product risk in your project.
Investigate the specification documents
Have discussions about the project with all stakeholders including the developer
As a real user walk around the website
126. What are the common risk that leads to the project failure?
The common risk that leads to a project failure are
Not having enough human resource
Testing Environment may not be set up properly
Limited Budget
Time Limitations
127. On what basis you can arrive to an estimation for your project?
To estimate your project , you have to consider following points
Divide the whole project into a smallest tasks
Allocate each task to team members
Estimate the effort required to complete each task
Validate the estimation
128. Explain how you would allocate task to team members ?
Task
Member
Analyze software requirement specification
All the members
Create the test specification
Tester/Test Analyst
Build up the test environment
Test administrator
Execute the test cases
Tester, Test administrator
Report defects
Tester
129. Explain what is testing type and what are the commonly used testing type ?
To get an expected test outcome a standard procedure is followed which is referred as Testing Type.
Commonly used testing types are
Unit Testing: Test the smallest code of an application
API Testing: Testing API created for the application
Integration Testing: Individual software modules are combined and tested
System Testing: Complete testing of system
Install/UnInstall Testing: Testing done from the point of client/customer view
Agile Testing: Testing through Agile technique
130. While monitoring your project what all things you have to consider ?
The things that has to be taken in considerations are
Is you project on schedule
Are you over budget
Are you working towards the same career goal
Have you got enough resources
Are there any warning signs of impending problems
Is there any pressure from management to complete the project sooner
131. What are the common mistakes which creates issues ?
Matching resources to wrong projects
Test manager lack of skills
Not listening to others
Poor Scheduling
Underestimating
Ignoring the small problems
Not following the process
132. What does a typical test report contains? What are the benefits of test reports?
A test report contains following things:
Project Information
Test Objective
Test Summary
Defect
The benefits of test reports are:
Current status of project and quality of product are informed
If required, stake holder and customer can take corrective action
A final document helps to decide whether the product is ready for release
133. What is test management review and why it is important?
Management review is also referred as Software Quality Assurance or SQA. SQA focusses more on the software process rather than the software work products. It is a set of activities designed to make sure that the project manager follows the standard process. SQA helps test manager to benchmark the project against the set standards.
134. What are the best practices for software quality assurance?
The best practices for an effective SQA implementation is
Continuous Improvement
Documentation
Tool Usage
Metrics
Responsibility by team members
Experienced SQA auditors
135. When is RTM (Requirement Traceability Matrix) prepared ?
RTM is prepared before test case designing. Requirements should be traceable from review activities.
136. What is difference between Test matrix and Traceability matrix?
Test Matrix: Test matrix is used to capture actual quality, effort, the plan, resources and time required to capture all phases of software testing
Traceability Matrix:Mapping between test cases and customer requirements is known as Traceability Matrix
137. In manual testing what are stubs and drivers?
Both stubs and drivers are part of incremental testing. In incremental testing there are two approaches namely bottom up and top down approach. Drivers are used in bottom up testing and stub is used for top down approach. In order to test the main module, stub is used, whuich is a dummy code or program .
138. What are the step you would follow once you find the defect?
Once defect is found you would follow the step
a) Recreate the defect
b) Attach the screen shot
c) Log the defect
139. Explain what is "Test Plan Driven" or "Key Word Driven" method of testing?
This technique uses the actual test case document developed by testers using a spread sheet containing special "key Words". The key words control the processing.
140. What is DFD (Data Flow Diagram) ?
When a "flow of data" through an information system is graphically represented then it is known as Data Flow Diagram. It is also used for the visualization of data processing.
141. Explain what is LCSAJ?
LCSAJ stands for 'linear code sequence and jump'. It consists of the following three items
a) Start of the linear sequence of executable statements
b) End of the linear sequence
c) The target line to which control flow is transferred at the end of the linear sequence
142. Explain what is N+1 testing?
The variation of regression testing is represented as N+1. In this technique the testing is performed in multiple cycles in which errors found in test cycle 'N' are resolved and re-tested in test cycle N+1. The cycle is repeated unless there are no errors found.
143. What is Fuzz testing and when it is used?
Fuzz testing is used to detect security loopholes and coding errors in software. In this technique random data is added to the system in attempt to crash the system. If vulnerability persists, a tool called fuzz tester is used to determine potential causes. This technique is more useful for bigger projects but only detects major fault.
144. Mention what are the main advantages of statement coverage metric of software testing?
The benefit of statement coverage metric is that
a) It does not require processing source code and can be applied directly to object code
b) Bugs are distributed evenly through code, due to which percentage of executable statements covered reflects the percentage of faults discovered
145. How to generate test cases for replace string method?
a) If characters in new string > characters in previous string. None of the characters should get truncated
b) If characters in new string< characters in previous string. Junk characters should not be added
c) Spaces after and before the string should not be deleted
d) String should be replaced only for the first occurrence of the string
146. How will you handle a conflict amogst your team members ?
I will talk individually to each person and note their concerns
I will find solution to the common problems raised by team members
I will hold a team meeting , reveal the solution and ask people to co-operate
147. Mention what are the categories of defects?
Mainly there are three defect categories
Wrong: When requirement is implemented incorrectly
Missing: It is a variance from the specification, an indication that a specification was not implemented or a requirement of the customer is not met
Extra: A requirement incorporated into the product that was not given by the end customer. It is considered as a defect because it is a variance from the existing requirements
148. Explain how does a test coverage tool works?
The code coverage testing tool runs parallel while performing testing on the actual product. The code coverage tool monitors the executed statements of the source code. When the final testing is done we get a complete report of the pending statements and also get the coverage percentage.
149. Mention what is the difference between a "defect" and a "failure" in software testing?
In simple terms when a defect reaches the end customer it is called a failure while the defect is identified internally and resolved then it is referred as defect.
150. Explain how to test documents in a project that span across the software development lifecycle?
The project span across the software development lifecycle in following manner
Central/Project test plan: It is the main test plan that outlines the complete test strategy of the project. This plan is used till the end of the software development lifecycle
Acceptance test plan: This document begins during the requirement phase and is completed at final delivery
System test plan: This plan starts during the design plan and proceeds until the end of the project
Integration and Unit test plan: Both these test plans start during the execution phase and last until the final delivery
151. Explain which test cases are written first black boxes or white boxes?
Black box test cases are written first as to write black box test cases; it requires project plan and requirement document all these documents are easily available at the beginning of the project. While writing white box test cases requires more architectural understanding and is not available at the start of the project.
152. Explain what is the difference between latent and masked defects?
Latent defect: A latent defect is an existing defect that has not caused a failure because the sets of conditions were never met
Masked defect: It is an existing defect that has not caused a failure because another defect has prevented that part of the code from being executed
153. Mention what is bottom up testing?
Bottom up testing is an approach to integration testing, where the lowest level components are tested first, then used to facilitate the testing of higher level components. The process is repeated until the component at the top of the hierarchy is tested.
154. Mention what are the different types of test coverage techniques?
Different types of test coverage techniques include
Statement Coverage: It verifies that each line of source code has been executed and tested
Decision Coverage: It ensures that every decision in the source code is executed and tested
Path Coverage: It ensures that every possible route through a given part of code is executed and tested
155. Mention what is the meaning of breadth testing?
Breadth testing is a test suite that exercises the full functionality of a product but does not test features in detail
156. Mention what is the difference between Pilot and Beta testing?
The difference between pilot and beta testing is that pilot testing is actually done using the product by the group of user before the final deployment and in beta testing we do not input real data, but it is installed at the end customer to validate if the product can be used in production.
157. Explain what is the meaning of Code Walk Through?
Code Walk Through is the informal analysis of the program source code to find defects and verify coding techniques
158. Mention what are the basic components of defect report format?
The basic components of defect report format includes
Project Name
Module Name
Defect detected on
Defect detected by
Defect ID and Name
Snapshot of the defect
Priority and Severity status
Defect resolved by
Defect resolved on
159. Mention what is the purpose behind doing end-to-end testing?
End-to end testing is done after functional testing. The purpose behind doing end-to-end testing is that
To validate the software requirements and integration with external interfaces
Testing application in real world environment scenario
Testing of interaction between application and database
160. Explain what it means by test harness?
A test harness is configuring a set of tools and test data to test an application in various conditions, it involves monitoring the output with expected output for correctness.
161. Explain in a testing project what testing activities would you automate?
In a testing project testing activities you would automate are
Tests that need to be run for every build of the application
Tests that use multiple data for the same set of actions
Identical tests that needs to be executed using different browsers
Mission critical pages
Transaction with pages that do not change in short time
System Testing: System testing is finding defects when the system under goes testing as a whole, it is also known as end to end testing. In such type of testing, the application undergoes from beginning till the end.
UAT: User Acceptance Testing (UAT) involves running a product through a series of specific tests which determines whether the product will meet the needs of its users.
112. Mention the difference between Data Driven Testing and Retesting?
Retesting: It is a process of checking bugs that are actioned by development team to verify that they are actually fixed.
Data Driven Testing (DDT): In data driven testing process, application is tested with multiple test data. Application is tested with different set of values.
113. What are the valuable steps to resolve issues while testing?
Record : Log and handle any problems which has happened
Report: Report the issues to higher level manager
Control: Define the issue management process
114. What is the difference between test scenarios, test cases and test script?
Difference between test scenarios and test cases is that
Test Scenarios: Test scenario is prepared before the actual testing starts, it includes plans for testing product, number of team members, environmental condition, making test cases, making test plans and all the features that are to be tested for the product.
Test Cases: It is a document that contains the steps that has to be executed, it has been planned earlier.
Test Script: It is written in a programming language and it's a short program used to test part of functionality of the software system. In other words a written set of steps that should be performed manually.
115. What is Latent defect?
Latent defect: This defect is an existing defect in the system which does not cause any failure as the exact set of conditions has never been met
116. What are the two parameters which can be useful to know the quality of test execution?
To know the quality of test execution we can use two parameters
Defect reject ratio
Defect leakage ratio
117. What is the function of software testing tool "phantom"?
Phantom is a freeware, and is used for windows GUI automation scripting language. It allows to take control of windows and functions automatically. It can simulate any combination of key strokes and mouse clicks as well as menus, lists and more.
118. Explain what is Test Deliverables ?
Test Deliverables are set of documents, tools and other components that has to be developed and maintained in support of testing.
There are different test deliverables at every phase of the software development lifecycle
Before Testing
During Testing
After the Testing
119. What is mutation testing?
Mutation testing is a technique to identify if a set of test data or test case is useful by intentionally introducing various code changes (bugs) and retesting with original test data/ cases to determine if the bugs are detected.
120. What all things you should consider before selecting automation tools for the AUT?
Technical Feasibility
Complexity level
Application stability
Test data
Application size
Re-usability of automated scripts
Execution across environment
121. How will you conduct Risk Analysis?
For the risk analysis following steps need to be implemented
a) Finding the score of the risk
b) Making a profile for the risk
c) Changing the risk properties
d) Deploy the resources of that test risk
e) Making a database of risk
122. What are the categories of debugging?
Categories for debugging
a) Brute force debugging
b) Backtracking
c) Cause elimination
d) Program slicing
e) Fault tree analysis
123. What is fault masking explain with example?
When presence of one defect hides the presence of another defect in the system is known as fault masking.
Example : If the "Negative Value" cause a firing of unhandled system exception, the developer will prevent the negative values inpu. This will resolve the issue and hide the defect of unhandled exception firing.
124. Explain what is Test Plan ? What are the information that should be covered in Test Plan ?
A test plan can be defined as a document describing the scope, approach, resources and schedule of testing activities and a test plan should cover the following details.
Test Strategy
Test Objective
Exit/Suspension Criteria
Resource Planning
Test Deliverables
125. How you can eliminate the product risk in your project ?
To eliminate product risk in your project, there is simple yet crucial step that can reduce the product risk in your project.
Investigate the specification documents
Have discussions about the project with all stakeholders including the developer
As a real user walk around the website
126. What are the common risk that leads to the project failure?
The common risk that leads to a project failure are
Not having enough human resource
Testing Environment may not be set up properly
Limited Budget
Time Limitations
127. On what basis you can arrive to an estimation for your project?
To estimate your project , you have to consider following points
Divide the whole project into a smallest tasks
Allocate each task to team members
Estimate the effort required to complete each task
Validate the estimation
128. Explain how you would allocate task to team members ?
Task
Member
Analyze software requirement specification
All the members
Create the test specification
Tester/Test Analyst
Build up the test environment
Test administrator
Execute the test cases
Tester, Test administrator
Report defects
Tester
129. Explain what is testing type and what are the commonly used testing type ?
To get an expected test outcome a standard procedure is followed which is referred as Testing Type.
Commonly used testing types are
Unit Testing: Test the smallest code of an application
API Testing: Testing API created for the application
Integration Testing: Individual software modules are combined and tested
System Testing: Complete testing of system
Install/UnInstall Testing: Testing done from the point of client/customer view
Agile Testing: Testing through Agile technique
130. While monitoring your project what all things you have to consider ?
The things that has to be taken in considerations are
Is you project on schedule
Are you over budget
Are you working towards the same career goal
Have you got enough resources
Are there any warning signs of impending problems
Is there any pressure from management to complete the project sooner
131. What are the common mistakes which creates issues ?
Matching resources to wrong projects
Test manager lack of skills
Not listening to others
Poor Scheduling
Underestimating
Ignoring the small problems
Not following the process
132. What does a typical test report contains? What are the benefits of test reports?
A test report contains following things:
Project Information
Test Objective
Test Summary
Defect
The benefits of test reports are:
Current status of project and quality of product are informed
If required, stake holder and customer can take corrective action
A final document helps to decide whether the product is ready for release
133. What is test management review and why it is important?
Management review is also referred as Software Quality Assurance or SQA. SQA focusses more on the software process rather than the software work products. It is a set of activities designed to make sure that the project manager follows the standard process. SQA helps test manager to benchmark the project against the set standards.
134. What are the best practices for software quality assurance?
The best practices for an effective SQA implementation is
Continuous Improvement
Documentation
Tool Usage
Metrics
Responsibility by team members
Experienced SQA auditors
135. When is RTM (Requirement Traceability Matrix) prepared ?
RTM is prepared before test case designing. Requirements should be traceable from review activities.
136. What is difference between Test matrix and Traceability matrix?
Test Matrix: Test matrix is used to capture actual quality, effort, the plan, resources and time required to capture all phases of software testing
Traceability Matrix:Mapping between test cases and customer requirements is known as Traceability Matrix
137. In manual testing what are stubs and drivers?
Both stubs and drivers are part of incremental testing. In incremental testing there are two approaches namely bottom up and top down approach. Drivers are used in bottom up testing and stub is used for top down approach. In order to test the main module, stub is used, whuich is a dummy code or program .
138. What are the step you would follow once you find the defect?
Once defect is found you would follow the step
a) Recreate the defect
b) Attach the screen shot
c) Log the defect
139. Explain what is "Test Plan Driven" or "Key Word Driven" method of testing?
This technique uses the actual test case document developed by testers using a spread sheet containing special "key Words". The key words control the processing.
140. What is DFD (Data Flow Diagram) ?
When a "flow of data" through an information system is graphically represented then it is known as Data Flow Diagram. It is also used for the visualization of data processing.
141. Explain what is LCSAJ?
LCSAJ stands for 'linear code sequence and jump'. It consists of the following three items
a) Start of the linear sequence of executable statements
b) End of the linear sequence
c) The target line to which control flow is transferred at the end of the linear sequence
142. Explain what is N+1 testing?
The variation of regression testing is represented as N+1. In this technique the testing is performed in multiple cycles in which errors found in test cycle 'N' are resolved and re-tested in test cycle N+1. The cycle is repeated unless there are no errors found.
143. What is Fuzz testing and when it is used?
Fuzz testing is used to detect security loopholes and coding errors in software. In this technique random data is added to the system in attempt to crash the system. If vulnerability persists, a tool called fuzz tester is used to determine potential causes. This technique is more useful for bigger projects but only detects major fault.
144. Mention what are the main advantages of statement coverage metric of software testing?
The benefit of statement coverage metric is that
a) It does not require processing source code and can be applied directly to object code
b) Bugs are distributed evenly through code, due to which percentage of executable statements covered reflects the percentage of faults discovered
145. How to generate test cases for replace string method?
a) If characters in new string > characters in previous string. None of the characters should get truncated
b) If characters in new string< characters in previous string. Junk characters should not be added
c) Spaces after and before the string should not be deleted
d) String should be replaced only for the first occurrence of the string
146. How will you handle a conflict amogst your team members ?
I will talk individually to each person and note their concerns
I will find solution to the common problems raised by team members
I will hold a team meeting , reveal the solution and ask people to co-operate
147. Mention what are the categories of defects?
Mainly there are three defect categories
Wrong: When requirement is implemented incorrectly
Missing: It is a variance from the specification, an indication that a specification was not implemented or a requirement of the customer is not met
Extra: A requirement incorporated into the product that was not given by the end customer. It is considered as a defect because it is a variance from the existing requirements
148. Explain how does a test coverage tool works?
The code coverage testing tool runs parallel while performing testing on the actual product. The code coverage tool monitors the executed statements of the source code. When the final testing is done we get a complete report of the pending statements and also get the coverage percentage.
149. Mention what is the difference between a "defect" and a "failure" in software testing?
In simple terms when a defect reaches the end customer it is called a failure while the defect is identified internally and resolved then it is referred as defect.
150. Explain how to test documents in a project that span across the software development lifecycle?
The project span across the software development lifecycle in following manner
Central/Project test plan: It is the main test plan that outlines the complete test strategy of the project. This plan is used till the end of the software development lifecycle
Acceptance test plan: This document begins during the requirement phase and is completed at final delivery
System test plan: This plan starts during the design plan and proceeds until the end of the project
Integration and Unit test plan: Both these test plans start during the execution phase and last until the final delivery
151. Explain which test cases are written first black boxes or white boxes?
Black box test cases are written first as to write black box test cases; it requires project plan and requirement document all these documents are easily available at the beginning of the project. While writing white box test cases requires more architectural understanding and is not available at the start of the project.
152. Explain what is the difference between latent and masked defects?
Latent defect: A latent defect is an existing defect that has not caused a failure because the sets of conditions were never met
Masked defect: It is an existing defect that has not caused a failure because another defect has prevented that part of the code from being executed
153. Mention what is bottom up testing?
Bottom up testing is an approach to integration testing, where the lowest level components are tested first, then used to facilitate the testing of higher level components. The process is repeated until the component at the top of the hierarchy is tested.
154. Mention what are the different types of test coverage techniques?
Different types of test coverage techniques include
Statement Coverage: It verifies that each line of source code has been executed and tested
Decision Coverage: It ensures that every decision in the source code is executed and tested
Path Coverage: It ensures that every possible route through a given part of code is executed and tested
155. Mention what is the meaning of breadth testing?
Breadth testing is a test suite that exercises the full functionality of a product but does not test features in detail
156. Mention what is the difference between Pilot and Beta testing?
The difference between pilot and beta testing is that pilot testing is actually done using the product by the group of user before the final deployment and in beta testing we do not input real data, but it is installed at the end customer to validate if the product can be used in production.
157. Explain what is the meaning of Code Walk Through?
Code Walk Through is the informal analysis of the program source code to find defects and verify coding techniques
158. Mention what are the basic components of defect report format?
The basic components of defect report format includes
Project Name
Module Name
Defect detected on
Defect detected by
Defect ID and Name
Snapshot of the defect
Priority and Severity status
Defect resolved by
Defect resolved on
159. Mention what is the purpose behind doing end-to-end testing?
End-to end testing is done after functional testing. The purpose behind doing end-to-end testing is that
To validate the software requirements and integration with external interfaces
Testing application in real world environment scenario
Testing of interaction between application and database
160. Explain what it means by test harness?
A test harness is configuring a set of tools and test data to test an application in various conditions, it involves monitoring the output with expected output for correctness.
161. Explain in a testing project what testing activities would you automate?
In a testing project testing activities you would automate are
Tests that need to be run for every build of the application
Tests that use multiple data for the same set of actions
Identical tests that needs to be executed using different browsers
Mission critical pages
Transaction with pages that do not change in short time