Testing Methodologies

At Avion, we adhere to the following testing methodologies:

Avion's unit test cases embody characteristics that are critical to the success of the unit. These characteristics can indicate appropriate/inappropriate use of a unit as well as negative behaviors that are to be trapped by the unit. A unit test case, in and of itself, documents these critical characteristics, although many software development environments do not rely solely upon code to document the product in development.

Integration testing (sometimes called Integration and testing and abbreviated I&T) is the phase of software testing in which individual software modules are combined and tested as a group. It follows unit testing and precedes system testing.

The purpose of Integration testing is to verify functional, performance and reliability requirements placed on major design items.The different types of integration testing followed at Avion are Big Bang, Top Down, Bottom Up, and Back bone

System testingis testing conducted on a complete, integrated system to evaluate the system's compliance with its specified requirements.

As a rule, System testing takes, as its input, all of the "integrated" software components that have successfully passed Integration testing and also the software system itself integrated with any applicable hardware system(s).

System testing is actually done to the entire system against the Functional Requirement Specification(s) (FRS) and/or the System Requirement Specification (SRS). Moreover, the System testing is an investigatory testing phase, where the focus is to have almost a destructive attitude and test not only the design, but also the behavior and even the believed expectations of the customer. It is also intended to test up to and beyond the bounds defined in the software/hardware requirements specification(s).

An acceptance test is jointly performed by users or sponsors with manufacturers or producers through black-box testing(i.e., the testers need not know anything about the internal workings of the system). The results will determine acceptance of the system.

It may also be referred to as a functional test, beta test, QA test, application test, confidence test, end user test, final test, validation test, factory acceptance test or site or field acceptance test.

Acceptance tests take the form of a suite of tests designed to be run on the completed system. Each individual test, known as a case, exercises a particular operating condition of the user's environment or feature of the system, and will result in a pass or fail boolean outcome.

Testing Mechanisms | Testing Methodologies | Testing Types | Testing Tools