How to Review

-
How to review? – The following are the list of activities involved:
  1. Define the criteria – Have a checklist of what to look for?
  2. Perform the check
  3. Record your results
  4. Share, discuss and implement the changes required
  5. Version control the documents involved
  6. Sign off and use the doc as intended.

Comments

Post a Comment

Popular posts from this blog

Retesting vs Regression Testing ( Difference between retesting and regression testing )

-
Retesting: Retesting is functional testing type In this type of testing, the tester re tests the application which was earlier reported as a bug and now fixed by the developer. This bug can be due to functionality issues as well as design issues. Retesting the functionality of a link which was previously not working or testing the link accessibility issues of a page etc can be listed as examples for retesting. Regression testing: Regression is a testing of the unchanged area of software or application to ensure working with new changes.Regression testing is done to test whether the changes made on the site have any impact on other modules which were earlier working fine. New requirement change, implementation of new functionality are some of the scenarios where regression testing is effective. Regression testing can be automated using effective automated tools such as Selenium, Quick Test Professional etc.
Read more

Static testing technique

-
Static testing is the testing of the software work products manually, or with a set of tools, but they are  not executed . It starts early in the Life cycle and so it is done during the verification process. It does not need computer as the testing of program is done without executing the program.  For example:  reviewing, walk through, inspection, etc. Most static testing techniques can be used to ‘test’ any form of document including source code, design documents and models, functional specifications and requirement specifications.
Read more