Explain Bug Life cycle
What is integration testing and regression testing
What is verification and validation
How does winrunner recognizes the project which is in
custom build
What is expert view and tree view
How does QTP identifies the project
What is the difference between Winrunner and QTP
What is Test Director and which version of test director
your are using in your project
What is a test plans
what are the contents present in a test plan
What is the risk of testing a project
- 4 Answers
- 9052 Views
- Mphasis, I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / shyam
bug life cycle:
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.
| Is This Answer Correct ? | 5 Yes | 1 No |
Answer / gayathri
What is integration testing and regression testing ?What is
verification and validation ?
Integration testing :
The integration Testing is doing for integrated modules
with the intension of finding interface errors.
Here we have to check whether the integrated modules are
Working properly or not. This can be do through the
integration test cases.
For example: Creating a user account and login to the
system
are two modules.
Here u can see the Create User is a module and Login user
is another module. So First we create a user then with the
new username and password we logon to the system. If it is
working as per the expectation then the test is pass.
we can follow the two approaches in Integration Testing-
Bottom up Integration and Top Down Integration....
regression testing :Test the newversion of the application
with previous version of same application.
After fixing the bug the developer send application to
tester.tester test the application .new functionality of
application have n't create any problem on prevoius
appliction
| Is This Answer Correct ? | 4 Yes | 2 No |
Answer / kshama
Integration testing : Testing Perform to Expose defects in
the Interface & in the Interaction between Integrated
component or system.
1)Component integration Testing
2)System Interaction Testing
Regression Testing : Testing of Previously Tested Program
following Modification to ensure that defects have not been
Introduced or uncover in unchanged area of Software as a
Result of the Changes made. It is Performed when the
software or its Environment Changed.
| Is This Answer Correct ? | 1 Yes | 0 No |
Answer / gayathri
verification:To check the appliction is right or wrong.
It is static testing code is doesn't
execute.reviews,meetings,Auditings,walkthrought ....comes
under verification.
validation:To check the appliction is right or wrong
according to the customer expectations.It is static testing
code is execute.all testings like unit testing,system
testing,security testings.....comes under validation
| Is This Answer Correct ? | 3 Yes | 6 No |
what are the possible test cases for online jobs search portal..if its a job seeker module and any 1 if u had worked on this proj pls share the bugs with sev and priority pls frends i need replies for these queries ..thanks in advance
How do tou design a good test case?
How to do the performance testing Manualy? Do u have a test case for that?
Can any one tell me the contents in Traceability Matrix
You may undergone many projects. Do all the projects match up with customer’s expectations?
What are the differences in testing a client-Server and a web Application
How could you handle the situation when you get the high seveority bug when the application is going to deliver by today night?
what do you mean by Personel Effectiveness and how much it will be affected to Test engineer
Do you handle deployment? How?
How to test login page or web login page? are they difference?
what is differance between smoke testing and sanity testing?
What are the Test case for the file transfer.
Automation Testing 
