0% found this document useful (0 votes)
42 views2 pages

Questions

The document provides a comprehensive overview of various testing concepts, including the defect/bug life cycle, test cases, test plans, and strategies. It outlines the differences between severity and priority of defects, defect reporting steps, and examples of different severity and priority combinations. Additionally, it covers principles of testing, defect density, defect removal efficiency, and other testing methodologies and terminologies.

Uploaded by

vreena3
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
42 views2 pages

Questions

The document provides a comprehensive overview of various testing concepts, including the defect/bug life cycle, test cases, test plans, and strategies. It outlines the differences between severity and priority of defects, defect reporting steps, and examples of different severity and priority combinations. Additionally, it covers principles of testing, defect density, defect removal efficiency, and other testing methodologies and terminologies.

Uploaded by

vreena3
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd

Ques 1: Defect/Bug Life Cycle?

Ans 1: Refer attached document.

Ques 2: What is Test Case?


Ans 2: Steps to verify the functionalties of an application.

Ques 3: Test Plan and Test Strategy?


Ans 3:
Test Strategy:

Ques 4: Severity and Priority?


Ans 4:
Severity: How critical the Defect is?

Priority: In how much time, we need to fix the defect/bug?

Ques 5: Defect Reporting Steps?


Ans 5:
Description:

Test Data:

Steps to Replicate:

Expected Result:
Actual Result:

Screen shots attach if requried.

Ques 6: Example to High Severity and Low Priority?


Ans 6: Registration Form: After continous 100 click, application is getting crash.
(Severity: High)

Priority: Low (Because, it would not be practically done by a user that it clicks a
"Submit" button continously 100 times.)

Ques 7: Example of Low Severity and High Priority?


Ans 7: Logo is not displaying correctly (Sev: Low, as it not effecting or breaking
functionality)

Priority: High (Logo should be fixed as soon as possible, as it represent a site)

Ques 8: Example of High Severity and High Priority?


Ans 8: Application is logging in with any username and Password (Sev: High,
Priority: High)

Ques 9: Example of Low Severity and Low Priority?


Ans 9: Submit button works after 2 clicks (Sev: Low, priority: Low)

Ques 10: Equivalence partioning and Boundry Value analysis?

Ques 11: Principles of Testing and also there explanations?


Ans 11: 7 Principles of Testing are:
- Exhaustive Testing is Impossible (100% coverage is impossible)
- Testing means finding Defects
- Early Testing
- Defect Clustering (Doing testing and finding defect in a particular module of an
application)
- Test is context dependent. (Domain Specific)
- Pesticide Paradox (Test cases needs to be updated time to time)
- Absence of Error Fallacy

Ques 12: Defect Density?


Ans: Total number of Defects Found/Total number of Modules

Ques 13: Defect Removal Efficiency (DRE)?


Ans: Total number of Defects Resolved/Total number of Defects Found *100

Ques 14: Test Cases on Fire Extinguisher/Clock/Pen?


Ans 14: - Should be stick at the visible place
- Should be of Red color
- Gas should be filled all the time
- Fire Drill should be happened after a while so that people should aware
the use of
- Pin should be tied
- Maintenance should be done after relevant interval of time
- should be placed in an easily approachable mode

Ques 15: V-Model : Verification and Validation?


Ans 15:
Verification: Verification Done after every phase of Development and before moving
onto the next phase. That's why it is cost effective.

Validation: Validation done after complete "Software Development" i.e. once the
Software gets Developed completely. That's why it is less cost effective.

Ques 16: Entry Criteria and Exit Criteria?


Ans 16:
Entry Criteria: Once the smoke test gets Pass.

Exit Criteria: Once an application meets with the requirement and reported Defects
gets fixed. Also, the Known issues if remains should be informed to Client.

Ques 17: What is Smoke test and why it is required and when, it should be done?

Ques 18: Difference b/w Regression and Retesting?

Ques 19: What is Testing and why it is required?

Ques 20: Estimation --- I generally explain Work Break Down Structure (WBS)?

Ques 21: What is RTM (Requirement Tracebility Matrix)?

You might also like