Q1. What is the difference between Functional and Non-Functional Requirements?
Answer:
- Functional Requirements specify what the system should do (e.g., login, search).
- Non-Functional Requirements specify how the system should be (e.g., performance, reliability).
Examples: - Functional: Authentication, Business Rules, Legal Requirements
- Non-Functional: Usability, Data Integrity, Security
Q2. How are Severity and Priority related in defect management?
Answer:
- Severity: Technical seriousness of the bug (Application perspective)
- Priority: Urgency to fix the bug (User perspective)
High Severity ≠ High Priority always. Example: - High Severity, Low Priority: Crash on a rarely used feature
- Low Severity, High Priority: Spelling error on homepage
Q3. What are different types of Severity levels in testing?
Answer:
- Low – UI Defects
- Medium – Boundary/Validation Defects
- High – Calculation, Compatibility, Hardware Failures, Control Flow
Q4. What is the difference between Priority and Severity?
Answer:
- Severity is about the impact of a defect (How bad is it?)
- Priority is about the order in which a defect should be fixed (How soon?)
Examples:
- High Severity, Low Priority: Crash in a rarely used feature
- Low Severity, High Priority: Wrong company name on the homepage
- High Severity, High Priority: App crash during login
- Low Severity, Low Priority: Minor cosmetic issue
Q5. What is Defect Severity?
Answer:
Defect Severity is the level of impact a defect has on the functionality or system operation. It is determined based on how badly the deviation affects the product.
Q6. What is Bucket Testing?
Answer:
Bucket Testing (A/B Testing) is used to compare two versions of a webpage or feature to measure which one performs better based on metrics like click rate or traffic.
Q7. What are Entry and Exit Criteria in Testing?
Answer:
- Entry Criteria: Conditions before testing starts (e.g., SRS, Test Plan ready)
- Exit Criteria: Conditions to stop testing (e.g., No critical bugs, test summary report ready)
Q8. What is Concurrency Testing?
Answer:
Concurrency Testing checks the performance of an app when multiple users access it simultaneously. It helps detect issues like locking, deadlock, and response delays. Tools like LoadRunner are used.
Q9. What is Statement/Line/Code Coverage?
Answer:
It’s a White Box Testing metric to check which lines of code were executed.
Formula:
Statement Coverage = (Executed Statements / Total Statements) * 100
Q10. What is Branch/Decision Coverage?
Answer:
Branch Coverage checks that each possible path (like if/else) is executed at least once.
Formula:
Branch Coverage = (Tested Branches / Total Branches) * 100
Q11. What is the difference between High-level and Low-level Test Cases?
Answer:
- High-Level Test Cases: Cover major app functionalities (e.g., login, DB updates)
- Low-Level Test Cases: Focus on UI elements (e.g., button color, label alignment)
Q12. What is Localization Testing?
Answer:
Localization Testing checks if the app is correctly adapted for a specific culture or language (e.g., date formats, currency, language translation).
Example: Testing Islamic banking rules and Hijiri calendar support.
Q13. What is Risk Analysis in Software Testing?
Answer:
Risk Analysis identifies possible risks in a project and plans to reduce or avoid them.
Examples of risks:
- Time constraints
- Requirement changes
- Build delays
Mitigation: Allocate more testers to high-risk areas, create risk profiles.
Q14. What is the difference between Two-tier and Three-tier Architecture?
Answer:
- Two-tier (Client/Server): Direct communication between client and database server.
- Three-tier (Client/Server/DB): Middle layer (application server) processes client requests and fetches data from DB.
Q15. What is Static Testing?
Answer:
Static Testing is done without executing code.
Includes: Code reviews, walkthroughs, inspections.
Q16. What is Dynamic Testing?
Answer:
Dynamic Testing is done by executing the application and verifying the output.
Examples: Unit, Integration, System, Acceptance Testing
Q17. Difference between Static and Dynamic Testing?
Answer:
| Static Testing | Dynamic Testing |
| No code execution | Executes the code |
| Early stage | Later stage |
| Cost-effective | More expensive |
| Examples: Code reviews | Examples: System testing |
Q18. What is the purpose of Risk Assessment Review Meetings?
Answer:
Risk Assessment Review meetings help identify and discuss potential testing risks with development teams and allocate resources efficiently based on risk level.
Q19. What is meant by Code Coverage in testing?
Answer:
Code Coverage is a measure used in white-box testing to determine how much code has been tested. It ensures no critical lines or paths are left untested.
Q20. What is A/B Testing?
Answer:
A/B Testing (Bucket Testing) compares two versions of a webpage or app to see which one performs better in terms of user engagement or conversions.
👉The Next 20 Questions-I: MANUAL TESTING
