1. What is Manual Testing?
Manual Testing is a type of software testing where test cases are executed manually by a tester without using automation tools.
Example: Every morning, before release deployment, you manually log in to the QA environment and validate critical flows like login, dashboard, and logout using real user test data.
2. What is a Test Case?
A test case is a document with a set of conditions to determine if a feature is working as expected.
Example: You create a test case to verify login: enter valid email/password, click login, expect the dashboard page. You do this every time a build is deployed.
3. What is a Bug?
A bug is a flaw in the software which leads to incorrect or unexpected results.
Example: You click 'Submit' on a leave form, but the page freezes. You raise a bug in JIRA and assign it to the developer.
4. What is Regression Testing?
Testing previously tested functionality to ensure new changes haven't broken existing features.
Example: After a password reset feature is added, you retest login, dashboard access, and logout—just to be sure they're still working.
5. What is Smoke Testing?
A basic test to check if the build is stable enough for further testing.
Example: You launch the app after a new deployment and check if major pages like login and dashboard load correctly before full testing begins.
6. What is Sanity Testing?
It is a focused test to ensure a specific bug fix or new functionality works as expected.
Example: After a bug fix for mobile number validation, you check only the registration form to verify if it's now accepting valid numbers.
7. What is the Defect Life Cycle?
It represents the states a defect goes through during its life: New → Assigned → Open → Fixed → Retest → Closed.
Example: You find a bug in a payment gateway, log it in JIRA, dev fixes it, you retest, and then close the ticket.
8. What is Exploratory Testing?
Unscripted testing based on tester's intuition and experience.
Example: You navigate through a newly developed user profile module randomly and find that "Change Picture" crashes the page.
9. What is Ad-hoc Testing?
Informal testing without any structured approach or documentation.
Example: During lunch, you casually test the application on your phone and discover a button misalignment issue.
10. What is Functional Testing?
Testing to ensure the system performs its functions as expected.
Example: Checking if the 'Add to Cart' button actually adds an item in the cart and updates the cart count.
11. What is Non-Functional Testing?
Testing non-functional aspects like performance, usability, and reliability.
Example: Checking whether a web page loads within 3 seconds under slow internet conditions.
12. What is Boundary Value Analysis?
Testing input values at boundaries to catch edge-case bugs.Example: For an age field allowing 18–60, you test with 17, 18, 60, and 61 to validate limits.
13. What is Equivalence Partitioning?
Dividing input data into valid and invalid classes to reduce test cases.
Example: For a PIN field that accepts 4 digits only, you test with 1234 (valid), 123 (invalid), and abcd (invalid).
14. What is a Test Scenario?
A high-level idea of what to test.
Example: "Verify user can reset password" is a test scenario; its test cases would be steps to execute it.
15. What is a Test Plan?
A document that outlines the strategy, scope, approach, and resources for testing.
Example: You create a test plan before sprint testing begins, listing all features to be tested and who will do what.
16. What is Usability Testing?
Testing how user-friendly and intuitive the application is.
Example: You ask a non-technical team member to use the app and observe if they struggle with navigation.
17. What is Compatibility Testing?
Testing how the application behaves across browsers, OS, and devices.
Example: You test the app on Chrome, Firefox, and Safari and find layout issues in Safari.
18. What is Severity?
It indicates the impact of the bug on the system’s functionality.
Example: App crash on payment page is a high-severity issue.
19. What is Priority?
It indicates how soon the bug should be fixed.
Example: A broken company logo on the footer might be low severity but high priority before a client demo.
20. What is Integration Testing?
Testing how different modules work together.
Example: After completing the profile page and dashboard modules, you verify if updated profile data shows up correctly on the dashboard.
21. What is System Testing?
Testing the complete application as a whole.
Example: You test all modules of an e-commerce app together – login, search, cart, payment, and order history.
22. What is Acceptance Testing?
Final testing done to ensure the system meets business requirements.
Example: You and the client walk through a live application demo and validate whether it satisfies contract terms.
23. What is the role of QA in Agile?
QA collaborates closely with developers and product owners throughout the sprint to ensure quality in every stage.
Example: You attend daily standups, clarify user stories, write acceptance tests, and pair test with developers.
24. What is Test Data?
Data used to execute test cases – valid, invalid, boundary, random, etc.
Example: While testing registration, you create users with names in uppercase, lowercase, and special characters.
25. What is a Traceability Matrix?
It maps requirements to their corresponding test cases to ensure coverage.
Example: Before release, you check the matrix to confirm all critical requirements have at least one passed test case linked.
Comments
Post a Comment