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.
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 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-OPened: Issue 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
- Water fall.
15) Name types of integration testing?
- Top- Bottom Approach.
Bottom- Up Approach.
Big Bang Approach.