CareerEnclave.Com Info

FOR MORE & MORE TECHNICAL INTERVIEW QUESTIONS …, Join Our Group now
http://in.groups.yahoo.com/group/knowledge-base/join/

What is 'configuration management'?
Configuration management covers the processes used to control, coordinate, and track: code, requirements, documentation, problems, change requests, designs, tools/compilers/libraries/patches, changes made to them, and who makes the changes. What if the software is so buggy it can't really be tested at all?
The best bet in this situation is for the testers to go through the process of reporting whatever bugs or blocking-type problems initially show up, with the focus being on critical bugs. Since this type of problem can severely affect schedules, and indicates deeper problems in the software development process (such as insufficient unit testing or insufficient integration testing, poor design, improper build or release procedures, etc.) managers should be notified, and provided with some documentation as evidence of the problem.
How can it be known when to stop testing?
This can be difficult to determine. Many modern software applications are so complex, and run in such an interdependent environment, that complete testing can never be done. Common factors in deciding when to stop are:
•   Deadlines (release deadlines, testing deadlines, etc.)
•   Test cases completed with certain percentage passed
•   Test budget depleted
•   Coverage of code/functionality/requirements reaches a specified point
•   Bug rate falls below a certain level
•   Beta or alpha testing period ends