component testing) development life cycle or system level (after system testing) performed on a different object (system work product) tests interfaces between items different objectives what is a test level? integration testing concentrates on the interactions between different requirements items, rather than functionality group of test activities that are organised can involve both functional & structural approaches & managed together
concerned with the behaviour of the whole product
their generic objectives test environment should represent live the work product from which test cases are derived (the test basis) end-to-end, business process testing system testing the test object (what is being tested) functional and non-functional testing for each test level we can identify Test Levels typical defects & failure found often done by independent test team tools required specific approaches & responsibilities typically done by customers and / or users goal is to establish confidence in the software module, program, unit, class, object finding defects is not the main focus testing of software bits that are separately testable can involve functional & non-functional testing searches for defects & verifies functionality user acceptance testing acceptance testing includes structural testing of code component testing operation acceptance testing may include non-functional aspects 4 types contract & regulation acceptance testing (memory leaks) alpha is conducted at development site usually done by developers alpha and beta testing beta is conducted at customer site