81. On what basis you are fixing up the time for project completion?

Test strategy; Based on the test strategy and testing Approach

82. How u r breaking down the project among team members?

It can be depend on these following cases—-
1) Number of modules
2) Number of team members
3) Complexity of the Project
4) Time Duration of the project
5) Team member’s experience
etc……

83. Usually customers won’t give all the requirements. How will u manage & collect all the necessary information?

Sometimes customer may not produce all the requirements. At this situation Business analyst and project manager will use their experience which they handles this type of projects otherwise we will go through some reference sites where we will observe the functionality and they will prepare use cases and requirements.

or

I am agree with the above answer.
If we really face such a problem then it is better to get information from development team so that we can know the exact info Or else use Ad-hoc testing for the required job.

84. what are the Qualities needed by a software tester?

A software tester must have intent of showing the product is not working as specified.
Software tester have the basic attitude of showing the presence of errors. He must have perspective of customers i.e he has to use the system as he is the client of the system. He has to strive for the quality.

Or

Software Tester must has these qualities—
1)He/she must observe the problem from both the side say user and programmer.
2)Must has good under standing with other team members .
3)Able to understand programmers view.
4)Once start testing, do not put it remain.
5)First test requirements of the user.
6)Before start testing first analysis the project like ;
technology using in project, all the flow etc……

85. Did you write test cases of design phase?

Yes We can write test cases at the design phase

At the time of designing we should be ready with test cases

86. In Testing 10 cases you found 20 bugs then how will you know which bug is for which test case?

Each Bug Will Have a Unique Bug-ID which would be related to that particular Test Case. We also make use of the Matrix to keep track of bugs and test cases.

87. what is the path for test director,where the test cases are stored ?

c:\TDcomdir\TD_projectname\tests\test no

Usually test cases are stored in Test Plan in Test director

88. what is mean by test suite?

Test suit is “set of test cases”

Group of test cases is nothing but functional(+ve & -ve) and GUI

89. What is the diff. b/w Baseline and Traceability matrix?

Baseline : The point at which some deliverable produced during the software engineering process is put under formal change control

Traceability : Is used to check if some of the test cases are left out or not in Manual and automated testing.

Baseline is nothing but a software specification or functionality that is reviewed or accepted for development. Once the functionality is baseline, we can start developing of the functionality.

Where as a Traceability Matrix lists all the functionality or features and the test cases for each feature. By using the traceability matrix we can measure, when to stop testing of the project or application.
Generally Traceability Matrix contains:
1. UseCaseID(Functionality/Feature).
2. Description of the Feature.
3. Priority for the Feature.
4. TestCaseIDs for this Feature. (Once if the mapped testcases for each Feature meets Success criteria, then we can stop testing of the project)
5. In which phase is the Feature (Unit,Component,Integration,System)

90. what methodologies you are following?

Methodologies are considered in 2 accounts.

1) There are a few methodologies like : v-model,spiral (most common), waterfall, hybrid, prototype, etc depends on the company.
2) Depends on the clients and the requirements.

No. 2 is def related to no 1

Methodology means the way we are following while writing test cases . there are different ways like…
1. Functional Test cases
2. Equivalence Partitioning Test cases
3. Boundary value analysis
4. Cause Effect Graphing and Decision table