Select Page

Static Testing

The primary objective of all static testing is to find errors as early as possible in the SDLC and thereby improve the quality of the end-product with the least amount of cost.

Industry Awards

Global Locations

Certified QA Professionals

Happy Clients

Completed Projects

Many people, even some testers, don’t realize that testing can and should start before a line of code is ever written. Static testing is that process, and it continues even after coding has started, but the execution of the code isn’t necessary for static testing. By thoroughly reviewing requirements, design documents, design specifications, and prototypes, static testing can unearth defects early in the SDLC where it’s more cost effective to fix them. Missing or incomplete requirements, poor design, or inconsistent interface specifications are contenders for the first round of issues. Even code reviews are considered a form of static testing, as they can reveal inconsistencies or lack of adherence to coding standards.

The primary objective of all static testing is to find errors as early as possible in the SDLC and thereby improve the quality of the end-product with the least amount of cost. Both formal and informal reviews of documentation, prototypes, code, or test cases are generally performed for thoroughness and appropriateness of the end goal of the product. Nearly half of production defects could have been found during proper static testing cycles.

Some types of documentation that are
commonly reviewed are

Business Requirement Specifications

Prototypes

Test Cases

System Use Cases

Functional Specifications

Prototype Specifications

Manual or Automated Test Scripts

Field Dictionaries

Design Documents or Mockups

Test Plans

Unit Test Cases

Help Documents or Training Guides

QA Mentor’s Static Testing and Inspection Service can help you perform walkthroughs, technical reviews, or formal inspections. For each document type, QA Mentor provides thorough checklists to ensure nothing is missed, and we provide you with a comprehensive report with all defects and findings attributed and mapped to a specific verification point within the corresponding checklist document. We look for document completeness and coverage to help you achieve lower production defect rates, shorter development and testing cycles, and a higher ROI.

How we do it

  • Review all documentation related to the project
  • Create comprehensive checklists for each document
  • Validate documents with the checklists
  • Discuss issues with your team

 

If you’re ready to take the next step and let QA Mentor help you with your NonFunctional Testing

Benefits to a Customer

  • Increased ROI
  • Decreased number of production defects
  • Better quality code for system and user acceptance testing environments
  • Higher quality end-product
  • Reduced time-to-market

We’re here when you need us. If you have questions about anything on our site or our services, or if you are ready to start a consultation, we want you to contact us so we’ve tried to make it easy.

GET IN TOUCH

Please complete the form and one of our QA Expert Specialists will be in contact within 24 hours.
Alternatively, drop us an email at support @qamentor.com or give us a call at 212-960-3812

Form Submitted Successfully.