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.
Introduction Of Manual Testing
 

Selenium Manual Testing Training in Hyderabad

What is Manual testing?

Manual Testing is a process to find the defects. The testers play an important role as an end user and verify all features of the application. The ensure that the behavior of the application. The Manual Testing is the very basic type of testing. This helps to find the bugs in the application under test. It is preliminary testing, must carry out before start automating.

Selenium Manual Testing Training in Hyderabad

The test cases and also needs to check the feasibility of automation testing. The Test plan creates & follows by the tester to the comprehensiveness of testing. The automation testing tool using without executing test cases In Selenium Training in Hyderabad.
It is not necessary to the knowledge of any testing tool for manual software testing. The Software testing fundamental always 100% Automation is not possible. So the Manual Testing is very important For Selenium Training.

Goal of Manual Testing

The Goal of Manual Testing to make an application under test is defect free. The software application is working as per the specification document Using Selenium Training.
This type includes the testing of the Software manual. Without using any automated tool or any script. In this type, tester takes over the role of the end user. Test the Software to identify any unexpected behavior or bug. There are different stages of Manual Testing. Like Unit testing, Integration tests, System tests and User Acceptance testing.
A test plan document created by test lead. This describes the detailed and systematic approach to testing a software application. The test plan includes a complete understanding of ultimate workflow. To ensure the completeness of testing test cases or test scenarios created. Manual Testing includes exploratory testing as testers explore the software to identify errors.
After the testing started the designed test cases or test scenarios execute. Any differences between actual & expected results reported as defects. Once the reported defects are fixed. The testers will retest the defect to make sure that the defects fixed. The goals of testing are defect free & deliver quality Product to the customer.

Selenium Manual Testing  Training in Hyderabad

Selenium Manual Testing Training In Hyderabad: We offers Classroom And Online Selenium Manual Testing Training in Hyderabad By real time Experts.