Manual testing interview questions
Manual testing interview questions
1) Difference between Regression and retesting?
 
Retesting:
 
When QA identified a defect, then it should be assign it to Developer. Once developer gives fix, then there should be retesting done to confirm defect has been removed or not. This we call RETESTING”. Retesting will done before regression.
 
Regression:
If any new code added to the application (New CR and Defected fixed code), ensure this new code doesn’t impact on other components of the system. Regression will done after retesting.
 
2) What are different phases in agile process?
 
Agile is very powerful SDLC methodology to implement software in a better manner.
 
  • Sprint planning.
  • Sprint meeting.
  • Sprint product demonstration.
  • Sprint Retrospective.
 3) Who Will prepare RTM(Requirement Traceability Matrix)
 
Requirement Traceability Matrix will ensure 100% test coverage. Which means every test case should be mapped to their corresponding Requirement. In an organization, QA Manager will prepare Requirement Traceability Matrix
  
4) Define Defect Life Cycle with defect status?
 
Defect life cycle starts with when defect found and when it successfully closed(also Known as Bug Life Cycle). In this defect undergoes different status, Which described below.
 
  • New: When QA member finds the defect.
  •  Open: Once QA lead/Manager review defect and change it status to open and assign it to Developer.
  •  Fixed/ Retest: Once defect got fixed from Developer and assign it to QA member.
  •  Re-OPenedIssue after retesting the defect. In this member assign defect to Developer again.
  •  Rejected: There will be two reasons to reject defect from Developer.
  •  Duplicate Defect: Same defect has been raised by another QA member
  •  Not a Defect: Raised defect is not related to Requirement.
  •  Deferred: Fix will be given in further phases.
  •  Closed: Once the retested defect meets user requirement, QA member will close the defect.
 5) Where Test cases will be written in QC?
 
Test cases design will be done in Test Plan.
 
6) Where Test cases will be executed?
 
When tested application is migrated to QA Environment, then Test cases corresponding application will be pulled to Test lab and will be executed.
 
7. Name different requirement documents?
 
  • SRS(System requirement specification)
  • BRD (Business requirement document)
  • TRD (Technical Review document)
  • User Manuals.
  • Use cases
  • User stories(only in agile)
 8. What is meant by test scenario and test case?
 
Test scenario is “what to be tested and test case “How to be tested”. Test scenario is simply one liner statement Which explains about What to test. Whereas Test case gives detailed information about Pre-condition. What to test ,test description, design steps and expected results.
 
9. At What condition automation is preferred?
 
After completion of manual testing (application is in Stable), if any regression/repeated test cases going to execute, in that case Automation is preferred.
 
10) System and E2E testing levels will fall into what method?
 
System and E2E will come into Black Box Testing
 
11) What is meant by alpha and beta testing?
 
In Alpha, Application/Software is under Developer environment. Here we will shows case the application as per the user requirements.
 
Where in Beta, Application/Software is under user environment and Developer will send only few feedbacks to support UAT.
 
12) Name the roles and responsibilities of product owner in Agile?
 
Roles for product owner are:
 
He/She prioritize the Sprint duration.
 
He/She prioritize the User stories for the particular Sprint.
 
13) What things do we discuss in Retrospective meeting in Agile?
 
      Below things are discussed in Retrospective meetings.
 
  • Things went well.
  • Things not went well
  • Things need to be updated.
14) Name few SDLC types
 
SDLC types:
 
  • Water fall.
  • V-Model.
  •  Iterative.
  •  Spiral.
  •  Big bang.
  •  Agile etc.
15) Name types of integration testing?
 
  • Top- Bottom Approach.
  •  Bottom- Up Approach.
  •  Sandwich Approach.
  •  Big Bang Approach.
SOFTWARE TESTING TECHNIQUES
 
 

 SOFTWARE TESTING TECHNIQUES

SOFTWARE TESTING TECHNIQUES:

 
Some of the software testing techniques given below:
 
1) Process: It is a single activity or testing process.
 
2) All Life Cycle Activities:
 
It is an activity or it is a process.It covers Software development life cycle (SDLC). In earlier days the life cycle can end the defects. Designing the tests from the being introducing code. Sometimes it may stated as test basis verify by the test design. Requirements and design specifications which used to test basis.
 
3) Planning:
 
 Planning includes that what they want to do. And it is control the test activities. Test progress reported, and knowing about the software test.
 
4) Static Testing: 
 
This testing is eliminating the code the test conducted. And find the defects. The test was going when verification process done. Static analysis and document reviews are including the test. This is cost effective test and it is very useful. Ex: inspection, reviewing and walk through.
 
5) Dynamic Testing:
 
In this testing the running tests results are administrate. By eliminating the software code. Validation code it done. Ex. system testing, integration testing, and unit testing etc.
 
6) Preparation:
 
In this we have to the type of testing. Depending on designing cases and test conditions.
 
7) Evaluation:
 
This test evaluated as the middle of the test. We have to refer the result of the test. It evaluates the software and knows about completion criteria. The test finished or not and the software passed the test known by the help of this test.
 
8) Software products and related work products:
 
This related to Testing of designing the testing of code. Along with the rule and the designing specification. It related to the training material and operation documents are having equal importance.
 
 

SOFTWARE TESTING:

 
It is a process of eliminating the software bugs. And software testing is the process of assassinate a programming applications.
 
· It can also be refer as the process of verifying and validating . The software programs or products or applications.
 
· Expected works.
 
· Software implemented with the equal characteristics.
 
· It meets the technical and business requirements by the development and design.