Static Testing Methodology

Static testing is time consuming and can be costly, and it requires complete buy-infrom the management team.

Static testing > Better Documentation > Better Code > Fewer Defects > Faster Delivery > Higher Quality > Happier Customers

Download Brochure

Goals of Static Testing

  • Identify defects early, when they’re easiest to fix
  • Anticipate and correct defects before they’re coded
  • Reduce defects in production
  • Save both time and money

Get a Free Quote

Static Testing Methods

Inspections

Formal software inspections involve peer reviews of parts of the application that have been fully designed and documented. This is the most formal and time-consuming method.

Reviews

The application or module is analyzed to ensure that it meets the business needs.

Walkthroughs

This method helps to find anomalies, consider alternative approaches, and evaluate conformance to business or industry standards.

What’s Tested

  • Business Requirements Document (BRD)
  • Use Cases
  • System/Functional Requirements
  • Prototype
  • Prototype Specification Document
  • DB Fields Dictionary Spreadsheet

  • Unit Test Cases
  • Traceability Matrix Document
  • Test Plan Strategy Document/Test Cases
  • Test Data
  • Automation/Performance Test Scripts
  • User Manual/Training Guides/Documentation

How Static Testing is Performed

Use Cases Requirements Validation Checklist

Used to validate that all end-user actions are identified, as well as any input and output related to them.

Functional Requirements Validation Checklist

This checklist makes sure that the Functional Requirements identify all necessary elements such as constraints, calculation methods, and user characteristics.

Prototype/Screen Mock-up Validation Checklist

This document looks for matches to the use cases and requirements and verifiesusability.

Field Dictionary Validation Checklist

This checklist verifies that every field in the UI is defined well enough to create field level validation test cases.

Architecture Review Checklist

With this checklist, the architecture is reviewed for completeness and clarity.

Start a Free Pilot Project

Static ROI Calculation

  1. Calculate total # of hours spent static testing
  2. Convert those hours into a dollar amount – this is the amount of money invested in static testing
  3. Convert the # of defects found in static testing  into the number of hours that would have been needed to fix them if they had been found in traditional testing (1 defect = 10 hours to fix/test traditionally)
  4. Convert number of proposed hours fixing/testing defects into a dollar amount that would have been spent
  5. Subtract the amount invested in static testing in step 2 from the proposed amount calculated in step 4 to see the amount saved by static testing

Let us help you today to save money and achieve higher quality by staring the QA process at the earliest possible time. Even if you’re still unclear about how Static Testing is performed, our QA specialists can explain it to you in detail at no cost to you. Don’t waste time and money fixing defects that could have been prevented with an up-front investment in Static Testing.

Scroll Up

Enter your name and email address to Download Brochure


Your Name

Your Email

Enter your name and email address to Download Brochure


Your Name

Your Email

Enter your name and email address to Download Brochure


Your Name

Your Email