Quality Testing

Quality is delighting customers

Your current role and resposibilities?

how you says functionality as defect?

write one test case up to raise a defect?

what is the Exit criteria for U.A.Testing?

what is the Exit criteria for System testing?

what is the RTM (requirement Tracebility Matrix) ?

have you worked with Unit testing?

What is verification and validation?

What is regression testing?

What is defect life cycle?

What is test life cycle?

Why are you looking for a change?

How is your relationship with your manager?

You told to your manager that you are looking for a change?

Why Testing is Important?




Views: 539

Reply to This

Replies to This Discussion

Hi Folks,

   It would be great help to all if anybody post answers for this.So plese post answers for these questions on yr way.

Thanks in advance.



Aparna S



Hello bhagath,

Kindly search the quetions in qt before raising in forume,some of the questions are earlier discussed.


Anyways kindly find Answers for Your Questions


Qu.2 Your current role and responsibilities?


1)Understanding Requirements of the product
2)Based on those requirement i have to identify some test scenarios
3)w.r.t those scenarios i have to write test cases.
4)For keeping track of that particular requirement i have to Prepare requirement traciability matrix (RTM).
5)Performing Usability testing via control matrix
6)Execution of Test cases,defect reporting and tracking by Defect reporting tool Bugzilla
7)Performing Retesting and regresssion testing after resolution of the bugs.
8)Reporting to TL on dsily basis.
9)Performing Peer review in a team for better coverage.


Qu.3 how you says functionality as defect?

Ans : Any deviation from the requirement should be initially logged as a defect. In this particular case, the defect can be assigned to the Business Analyst (BA) or System Analyst (SA). Both BA & SA can mutually discuss the positive & negative impacts of the functionality in the system. If the new functionality can add value to the system, it can be included in the requirement. If not, it should be treated as a defect and removed from the system.

Qu.4 write one test case up to raise a defect?

Answer: Take a example of Login Page (Negative scenario)

           1)Enter Valid Username and Invalid password

 Expected result: is User should not be able to login

 Actual Result : User Login successfully with incorrect credencials

Qu.5 what is the Exit criteria for U.A.Testing?

Answer:  User acceptance testing is taking feedback from customers.

So its Exit Criteria are as follows:

(1) All Use Cases should be get passed

(2) The System is user friendly and there should not be any high severity defect open

I dont know exact exit documents

Qu.6 what is the Exit criteria for System testing?

Answer: (1)All Test Cases are passed

             (2)Build is stable

             (3) No Defects

Qu.7 what is the RTM (requirement Tracebility Matrix) ?

Answer: It is an Mapping between requirement and test cases

The main objective is to ensure requirement is not missed.

Qu.8 have you worked with Unit testing?

Answer: No

Qu.9 What is verification and validation?

Answer: Verification: (Static Testing) R we building r8 software

              Validation: (Dynamic Testing) R we building software r8.

Qu.10 What is regression testing?

Answer: Regression testing is the re-execution of some subset of tests that have already been conducted to ensure that changes have not propagated unintended side affects.

Regression Testing shall be carried out under the following circumstances, which are listed as follows...

Case 1:

When there has been change in existing requirements

Case 2:

When there is chance of issues re-surfacing after re-testing

Case 3:

When the system undergoes more than 2-4 releases ( ensure 0 latent issues).

Case 4:

When new requirements are incorporated ( to avoid negative Impact)

Case 5:

When there is a sudden drop in defect density.

Case 6:

When there is a change in Test/Dev environment

Qu.1 What is defect life cycle?


Bug Life Cycle:

In software development process, the bug has a life cycle.The bug should go through the life cycle to be closed. A specific life cycle ensures that the process is standardized. The bug attains different states in the life cycle. The life cycle of the bug can be shown diagrammatically as follows:

The different states of a bug can be summarized as follows:

1. New
2. Open
3. Assign
4. Test
5. Verified
6. Deferred
7. Reopened
8. Duplicate
9. Rejected and
10. Closed

Description of Various Stages:

1. New: When the bug is posted for the first time, its state will be ?NEW?. This means that the bug is not yet approved.

2. Open: After a tester has posted a bug, the lead of the tester approves that the bug is genuine and he changes the state as "OPEN"

3. Assign: Once the lead changes the state as "OPEN", he assigns the bug to corresponding developer or developer team. The state of the bug now is changed to "ASSIGN"

4. Test: Once the developer fixes the bug, he has to assign the bug to the testing team for next round of testing. Before he releases the software with bug fixed, he changes
the state of bug to "TEST". It specifies that the bug has been fixed and is released to testing team.

5. Deferred: The bug, changed to deferred state means the bug is expected to be fixed in next releases. The reasons for changing the bug to this state have many factors. Some of them are priority of the bug may be low, lack of time for the release or the bug may not have major effect on the software.

6. Rejected: If the developer feels that the bug is not genuine, he rejects the bug. Then the state of the bug is changed to "REJECTED"

7. Duplicate: If the bug is repeated twice or the two bugs mention the same concept of the bug, then one bug status is changed to "DUPLICATE".

8. Verified: Once the bug is fixed and the status is changed to "TEST", the tester tests the bug. If the bug is not present in the software, he approves that the bug is fixed and changes the status to "VERIFIED".

9. Reopened: If the bug still exists even after the bug is fixed by the developer, the tester changes the status to "REOPENED". The bug traverses the life cycle once again.

10. Closed: Once the bug is fixed, it is tested by the tester. If the tester feels that the bug no longer exists in the software, he changes the status of the bug to "CLOSED". This state means that the bug is fixed, tested and approved.

While defect prevention is much more effective and efficient in reducing the number of defects, most organization conducts defect discovery and removal. Discovering and removing defects is an expensive and inefficient process. It is much more efficient for an organization to conduct
activities that prevent defects.

Guidelines on deciding the Severity of Bug:

Indicate the impact each defect has on testing efforts or users and administrators of the application under test. This information is used by developers and management as the basis for assigning priority of work on defects.

A sample guideline for assignment of Priority Levels during the product test phase includes:

1. Critical / Show Stopper: An item that prevents further testing of the product or function under test can be classified as Critical Bug. No workaround is possible for such bugs. Examples of this include a missing menu option or security permission required to access a function under test.

2. Major / High : A defect that does not function as expected/designed or cause other functionality to fail to meet requirements can be classified as Major Bug. The workaround can be provided for such bugs. Examples of this include inaccurate calculations; the wrong field being updated, etc.

3. Average / Medium: The defects which do not conform to standards and conventions can be classified as Medium Bugs. Easy workarounds exists to achieve functionality objectives.
Examples include matching visual and text links which lead to different end points.

4. Minor / Low: Cosmetic defects which does not affect the functionality of the system can be classified as Minor Bugs.


Qu.11 Why are you looking for a change?

Answer: For Better future aspect

Qu.12 How is your relationship with your manager?

Answer: Relationship is gud

Qu.13 You told to your manager that you are looking for a change?

Answer; No

Qu.14 Why Testing is Important?

Answer: To Avoid future negative consequences (Risk) which may turn into revenue loss or loss of reputation for any organisation or loss of life or comes in the form of any other loss.

hi bhagath is it for 1+ interview questions did dey asked u

It is for 4+ exp

 Each and every question has been discussed earlier so kindly search for the same....

  @ Ajay ,

2) Your Current Role and Responsibility :--   This question has no specific answer ... very much person dependent ...

3) Extra Functionalities are always defects by keeping organization in mind...  and Missing functionalities are always defect by keeping Customer in mind... 

9) Verification and validation .. You made a mistake dude ...  I mean Right Software is Validation and Software Right is Verification ....

10) Regression testing :--  When You say you will run Subset of Regression pack then It comes under Sanity ...     In fact Subset of Test are executed to make it sure that the system ( after changes ) are in sane enough condition to be tested and we can proceed for Regression testing ......


Samrat Jha

Agreed Samrat... :)



 Welcome Ajay ...  and thanks for taking it positively...!


TTWT Magazine





© 2021   Created by Quality Testing.   Powered by

Badges  |  Report an Issue  |  Terms of Service