It doesn’t matter to me if the developer is aggressive or not, as long as I ensure my communication is professional. I always ensure that I communicate all the issues in a clearly documented from through email or through the bug tracking tool. In case of difference in opinion, I try to add business cases, which demands the fixing of bug raised by me. Though I provide all necessary information, if the developer is not taking it professionally, I try to work with that bug through my lead. However I ensure my best not to involve my lead since he has to spend his valuable time to work on this issue.

Ans:
Quality center
Test director
Rational clear quest
PVCS tracker

The following are the steps that I follow during retesting the bug:

I understand the bug description and steps to reproduce the bug from the Bug tracking tool. Optionally I also try to understand the root cause given by developer for this bug.

I identify the test conditions to be used for verifying this bug.

I will run the test case which found this bug and ensure that this bug is not appearing.

I also run the test cases which cover all the test conditions that are identified for verifying this bug. In case some test conditions are not part of any test case. I update the test case document with these additional conditions.

After completion of test case execution. I document the tests executed to verify this defect in the comments section of the Bug tracking tool with my time stamp.

I will send the tests I executed to retest the bug for peer review and based on the approval, I update the status of the bug to ‘closed’

 Critical bug means the business cannot run without fixing it. It is also called as show stopper.

Major bug means it requires to be fixed as early as possible. But the business cannot be continued.

It helps in tracking the bug status from identification to closure.

It acts as a communication tool between development and testing teams for bug related discussions

It keeps the track of the number of bugs identified, verified and rejected by each tester which helps in performance appraisal of the testers. It also logs the number of bugs fixed by each developer.

It helps in analyzing the stability of each feature.

It acts as an online database for bug fixes i.e. the developer ca read the fix procedure of similar bugs before he fixes a bus.

Ans: The business requirement document is important to formulate test plan

Ans: The collection of information should be done from following parties:
Business analyst
Developers
Documentation of previous versions
Stake holders
Any prototypes.

 Build process consists of various phases below Source code server: The developer develops the code and runs the unit test, integration tests and puts in to Master server/source code server which controls the source code with version cont...  

Step 1: Understand the project by going through use cases

Step 2: Prepare the test condition for normal, additional and exceptional flow

Step 3: Prepare additional test conditions based on experience

Step 4: Convert these test conditions in to test cases

Ans: Another name of user acceptance testing is Beta testing.