Manual Testing Interview Questions for Freshers and Experience

1. What is software testing?
Software Testing is the process of executing a program or system with the intent of finding errors.
Software testing is the process used to help identify the Correctness, Completeness, Security and Quality of the developed Computer Software
(OR)
The process of evaluating the software application or program to find the difference between the actual results to the expected result.
2. Software testing has three main purposes:

  1. Verification
  2. Validation and
  3. Defect finding.

The verification process confirms that the software meets its technical specifications and user requirements. It’s a Process based application.
The Defect is a variance between the expected and actual result. The defect’s ultimate source may be traced to a fault introduced in the specification, design, or development (coding) phases.

3. Testing Methodology?
Means what kind of approach is following while testing (e.g.) functional testing, Regression testing, Retesting, Confirmation testing.

4. Describe the difference between validation and verification
Verification is done by frequent evaluation and meetings to appraise the documents, policy, code, requirements, and specifications. This is done with the checklists, walkthroughs, and inspection meetings.
Validation is done during actual testing and it takes place after all the verification’s are being done.

5. What is Software Bug life cycle:
It has the following life cycle such as:

  • New: When the bug is posted for the first time is called new.
  • Open: After the tester sends the bug, the lead checks if it genuine then it is called as open.
  • Assign: After the lead checks, he assigns to the developer and that state is called assign.
  • Test: Before the developer releases the software with bug fixed, he changes the state of bug to “TEST”.
  • Fixed: When the developer resolved the bug the status is fixed.
  • Reopen: If the bug still exists even after the bug is fixed by the developer, the tester changes the status to reopen.
  • Closed: If the bug is no more the status is closed.

6. What is Software testing Life Cycle:

  • Requirements gathering: Collecting the project related information.
  • Analyzing: Discussing the collected information whether the requirements can meet.
  • Test plan preparation: It specifies the entire testing activity
  • Test case preparation: It is a document which contains input and corresponding results.
  • Test case execution: Execution of test case results to find bugs
  • Bug Tracking: Monitoring of the bug till closed.
  • Regression testing: Testing the application to find whether the change in code affect anywhere in the application.

7. Describe the Software Development Life Cycle
It includes aspects such as initial concept, requirements analysis, functional design, internal design, documentation planning, test planning, coding, document preparation, integration, testing, maintenance, updates, retesting, phase-out, and other aspects.

8. What are SDLC and STLC and the different phases of both?

STLC is software test life cycle it starts with:

  • Preparing the test strategy.
  • Preparing the test plan.
  • Creating the test environment.
  • Writing the test cases.
  • Creating test scripts.
  • Executing the test scripts.
  • Analyzing the results and reporting the bugs.
  • Doing regression testing.
  • Test exiting.

SDLC is software or system development life cycle, phases are:

  • Project initiation
  • Requirement gathering and documenting
  • Designing
  • Coding and unit testing
  • Integration testing
  • System testing
  • Installation and acceptance testing
  • Support or maintenance

10. Software testing has three main purposes:

  1. Verification
  2. Validation and
  3. Defect finding.

The verification process confirms that the software meets its technical specifications and user requirements. It’s a Process based application.
The Defect is a variance between the expected and actual result. The defect’s ultimate source may be traced to a fault introduced in the specification, design, or development (coding) phases.

Leave a Reply

Your email address will not be published. Required fields are marked *