Q21. What is Test Harness?
Ans:
A Test Harness is a set of tools, scripts, and test data configured to test an application in various conditions. It involves checking the output against the expected output for correctness. Test harness benefits include:
- Increased productivity due to automation.
- Improved quality in the application.
Q22. What is the difference between Bug Log and Defect Tracking?
Ans:
- Bug Log: It is a document that tracks the status of defects, such as whether they are open, closed, reopened, or deferred for a particular module.
- Defect Tracking: It is the process of tracking defects, including their symptoms, reproducibility, priority, severity, and status.
Q23. What are Integration Testing and Regression Testing?
Ans:
- Integration Testing: Involves combining modules and testing how they work together, focusing on communication and data flow. Techniques like White-box and Black-box testing are used.
- Regression Testing: Involves re-running tests after a bug fix to ensure the new build is free from previously fixed issues. It is performed after bugs are resolved, typically by testers.
Q24. Explain Peer Review in Software Testing?
Ans:
Peer review is when colleagues examine your work products to identify defects and suggest improvements. Some common approaches are:
- Inspection: A formal and systematic review.
- Team Review: A structured but informal approach.
- Walkthrough: An informal review where the author presents the work to colleagues.
- Pair Programming: Two developers work together on the same task to review each other’s work.
- Peer Desk Check: A simple check where one colleague reviews the work.
- Passaround: A multiple peer review process to gather feedback from several colleagues.
Q25. Explain Compatibility Testing with an Example?
Ans:
Compatibility testing checks whether an application works in different environments like operating systems, browsers, hardware, and peripherals.
Example:
For a game application, compatibility testing involves ensuring that it runs on different computers, verifying if it meets the system specifications like processor speed, RAM, and GPU compatibility.
Q26. What is Traceability Matrix?
Ans:
A Traceability Matrix is a document used to map and track test cases to specific requirements. It ensures that each requirement has a corresponding test case, and any defects related to those tests can be tracked. It typically includes:
- Requirement ID
- Test case ID
- Defect ID (if any)
Q27. Explain Boundary Value Testing and Equivalence Testing with Examples?
Ans:
- Boundary Value Testing (BVT): Focuses on testing the boundaries of input values.
Example:
If a field accepts user IDs from 4 to 10 characters, tests would include checking the boundaries: 4, 10 (valid), and 3, 11 (invalid). - Equivalence Testing: Checks if a value within a certain range or condition is valid.
Example:
A text box accepts only alphabet characters (a-z). Equivalence tests would involve entering valid alphabetic characters (a-z) and invalid characters (numbers, special symbols).
Q28. What is Security Testing?
Ans:
Security testing checks how well the system protects sensitive data and prevents unauthorized access or malicious activities. It includes techniques like functional testing, penetration testing, and vulnerability assessments.
Q29. What is Installation Testing?
Ans:
Installation testing ensures that hardware and software are installed and configured properly. It verifies whether the system components function correctly during installation and checks for potential errors or security issues.
Q30. What is AUT?
Ans:
AUT stands for “Application Under Test.” It is the software being tested after the design and coding phases during the software development lifecycle.
Q31. What is Defect Leakage?
Ans:
Defect leakage occurs when defects are discovered by end-users after the software has been delivered to them. It refers to bugs that were not found during testing but are identified when the application is used in real-world conditions.
Q32. What are the contents of an effective Bug Report?
Ans:
An effective bug report should contain:
- Project Name
- Subject
- Description
- Summary
- Detected By (Tester)
- Assigned To (Developer)
- Test Lead
- Test Version (Detected & Closed)
- Dates (Detected & Closed)
- Priority & Severity
- Status
- Bug ID
- Attachments (Screenshots, Logs)
- Failed Test Case
Q33. What is Error Guessing and Error Seeding?
Ans:
- Error Guessing: A technique where the tester guesses where defects might be and creates tests based on those assumptions.
- Error Seeding: A technique where known faults are deliberately added to the software to track how well the testing process detects them.
Q34. What is Ad-hoc Testing?
Ans:
Ad-hoc testing involves testing an application without any formal planning or predefined test cases. It is typically done by testers who have a strong understanding of the application and explore it intuitively.
Q35. What are the basic solutions for software development problems?
Ans:
- Clear and achievable requirements.
- Realistic schedules with adequate time for testing.
- Early and thorough testing, including re-testing after fixes.
- Clear communication and documentation among team members.
- Continuous feedback and close coordination with end-users.
Q36. What are common problems in software development?
Ans:
Common issues include:
- Inadequate or unclear requirements.
- Unrealistic project timelines.
- Insufficient or incomplete testing.
- Miscommunication among team members or with clients.
Q37. What is the difference between Software Testing and Quality Assurance (QA)?
Ans:
- Software Testing: Focuses on detecting defects through the testing process.
- Quality Assurance (QA): Involves improving and monitoring the entire development process to ensure quality, focusing on defect prevention rather than detection.
Q38. How to test a water bottle?
Ans:
Testing a water bottle can involve various tests:
- Usability Testing: Check if the cap fits well and if it leaks when tilted.
- Stress Testing: Test if the bottle can handle extreme temperatures or impacts.
- Compatibility Testing: Test if it holds different liquids without leaking or degrading.
- Ergonomics Testing: Ensure it is comfortable to hold and use.
Q39. What is Portlet Testing?
Ans:
Portlet testing refers to testing the individual modules (portlets) of a web-based application, typically within a portal. This involves verifying that each portlet functions as expected in isolation and integrates well within the portal.
40. What is Equivalence Partitioning?
Ans:
Equivalence partitioning is a testing technique used to reduce the number of test cases by dividing input data into different partitions or classes. In this method, the input conditions are grouped into equivalence classes, where each class is expected to produce the same result or behavior. The core idea is that testing one value from a particular equivalence class is enough to validate the behavior of the system for all values in that class.
Key Concepts:
- Equivalence Classes: These are sets of input conditions that are treated the same way by the system. If the system processes one case in the class incorrectly, it is likely to process all cases in that class incorrectly.
- Test Case Optimization: This technique helps in reducing the total number of test cases, focusing only on representative values from each equivalence class.
- Positive and Negative Classes: Equivalence classes can be positive (valid inputs) or negative (invalid inputs).
Example:
For an age validation system that accepts values between 18 and 60:
- Valid Input: Any number between 18 and 60, inclusive, forms a valid equivalence class.
- Invalid Input (too low): Any number less than 18 forms an invalid equivalence class.
- Invalid Input (too high): Any number greater than 60 forms another invalid equivalence class.
