General Manual Testing Interview Answers

General Manual Testing Interview Answers


  1. Difference between Verification & Validation ?

  2. Priority & Severity of a bug with example

  3. Use Case & Test Case

  4. Types of testing and Scope of testing

  5. Given a Real time scenario what is your approach to test and deliver it to Prod

  6. Given a Real time scenario write  (eg Elevator or Oven)

    1. Test Strategy document

    2. Test Plan document

    3. 10 Function Test Cases

    4. 10 Performance Test Cases

    5. 10 Security Test Cases

    6. Also talk about Accessibility Test Cases , UAT , Compatibility test etc

  7. Smoke Testing, Exploratory Testing, Regression Testing ,Sanity Testing, adhoc Testing

  8. Unit Testing, Integration Testing , System Testing and End to End Testing

  9. Test Pyramid concept

  10.  White box testing and Black box testing and Grey box testing

  11. Functional and non functional testing

  12. Defect Life Cycle and tools to track it

  13. Given  a product like vendor machine give Test Strategy , Test Plan and Test Cases (Functional + Non Functional)

  1. Difference between Test Plan Vs Test Strategy

  2. SDLC

  3. Agile 

    1. Different concepts

    2. How does it perform in your company ?

  4. Left Shift 

  1. When will you stop your testing and say the product is production ready.

  2. If you figure out an issue and your developer says it is not a bug , then what will you do?

  3. A challenging project you have tested, what was the challenge and how you overcame it 

  4. 5 Interesting or challenging bugs you reported

  5. Your recent Production issue and how you missed it ? How you ensured it won’t happen in future ?

  6. What is RCA ? 

  7. How do you prefer to manage your test cases , test plan etc ?

  8. Automation Concepts 




6 comments:

  1. What is Chaos Monkey and How Does it Work?
    When Netflix started chaos testing their system during their move to AWS, they created different “chaos monkeys” to help meet the need of continuous and consistent testing. These chaos monkeys were deployed into a system to introduce specific issues—network delays, instances, missing data segments, etc—and simulate different real-world scenarios.

    Each chaos monkey had its own name and job, including:

    Latency Monkey: Induces artificial delays
    Conformity and Security Monkeys: Hunt and kill instances that don’t adhere to best practices
    Janitor Monkey: Cleans up and removes unused resources
    Chaos Gorilla: Simulates an entire Amazon availability zone outage

    ReplyDelete
  2. Verification uses methods like reviews, walkthroughs, inspections and desk-checking whereas Validation uses methods like black box testing, white box testing and non-functional testing.

    ReplyDelete
  3. This comment has been removed by the author.

    ReplyDelete
  4. Priority is the order in which the developer should resolve a defect whereas Severity is the degree of impact that a defect has on the operation of the product.
    Priority is categorized into three types : low, medium and high whereas Severity is categorized into five types : critical. major, moderate, minor and cosmetic.
    Priority is associated with scheduling while Severity is associated with functionality or standards.
    Types of Severity
    In Software Testing, Types of Severity of bug/defect can be categorized into four parts :

    Critical: This defect indicates complete shut-down of the process, nothing can proceed further
    Major: It is a highly severe defect and collapses the system. However, certain parts of the system remain functional
    Medium: It causes some undesirable behavior, but the system is still functional
    Low: It won’t cause any major break-down of the system
    Priority Types
    Types of Priority of bug/defect can be categorized into three parts :

    Low: The Defect is an irritant but repair can be done once the more serious Defect has been fixed
    Medium: During the normal course of the development activities defect should be resolved. It can wait until a new version is created
    High: The defect must be resolved as soon as possible as it affects the system severely and cannot be used until it is fixed

    ReplyDelete
  5. A Use Case is used to define the system that how to use the system for performing a specific task. and A Test Case is defined as a group of test inputs, execution condition, and expected results which further lead to developing a particular test objective.

    A use case is not a part of execution it is only a diagrammatic presentation of a document that specifies how to perform a certain task. If we talk about test case it is used to validate the software which is developed by testers for validating that the software is in working as per requirement or not.

    ReplyDelete
  6. Sanity Testing is a type of software testing that is performed after receiving a software build. The goal is to determine that the proposed functionality works approximately as expected.

    ReplyDelete