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

When can FMEA be of help to developers?

The Failure Mode and Effect Analysis is most effective when we are dealing with software products that have similarity to the previously developed applications. The experience of the developers/team other members in similar products can come in handy. The similarity of usage specifics and the structure of the design when identified implies we can have the FMEA oriented testing.

While at the stages of QA, QC and other testing phases what are the main documents that are referred?

The Quality related testing and testing phase in general requires each and every aspect of the project from customer specifications to developer designs. So the documents that are used can be summed up as:

SRS & Business requirements doc.

Functional/Technical documentation that was initially prepared.

Documents pertaining to the various modules – used for White Box testing.

Use case & other representative documents for program flow.

Test plan and other test case/script related documents.

What is SDLC?

The Software Development Life Cycle refers to the overall development cycle of the software from the eyes of the System Analyst. The various stages of the development right from the requirements gathering the final delivery after testing are included in the SDLC. The SDLC can further be defined as specific methodology that is incorporated as the way to proceed in the development of a specific software product.

What are the things that are to be present in a good test process?

A good a valid test process should contain various aspects of testing and attributes that are configurable from the tester. The effect of each of the test cases should be clearly shown by the test process with a clear outlook given to the results as to which test conforms to which case of testing. The understanding of the results should be clearly brought out. These when done can give a good test process. If you are going to better it, then the test process can also specify the possible causes of the error that has occurred.

Page 1 of 3123
eXTReMe Tracker