Development Testing

Different Types of Development Testing

unit testing

testing individual program units in isolation, focus on functionality

unit test case

when used as expected, the component being tested does what it is supposed to do

unit test case type 1

normal operation of a program showing the component works as expected

unit test case type 2

using abnormal inputs to show they are properly processed and don’t crash the component

partition testing

identify groups of inputs that have common characteristics and should be processed in the same way

path-based testing

ensure each path through the code is executed at least once

guideline based testing

use testing guidelines to choose test cases

component testing

showing the component interface behaves according to its specification

interface testing

aims to detect faults due to interface errors or invalid assumptions about interfaces

parameter interface

data passed from one procedure to another

shared memory interface

block of memory is shared between procedures

procedural interfaces

sub-system encapsulates a set of procedures to be called by other sub-systems

message passing interface

sub-systems request services from other sub-systems

system testing

testing the integrated system as a whole, testing the interactions between components

acceptance testing

provide a way to define “done”

regression testing

testing to check that changes have not broken previously working code

release testing

testing a particular release of a system that is intended for use outside of the dev team

performance testing

testing emergent properties of a system

user testing

users and customers provide input on system testing

alpha testing

users work with the dev team to test software

beta testing

a release of the software is made available to users to experiment with

acceptance testing

customers test a system to decide whether it is ready to be deployed