System Testing – Integration Testing and Release Testing | Software Engineering

Download our Android App from Google Play Store and start reading Reference Notes Offline.

system testingSystem Testing – Integration Testing and Release Testing,
Software Engineering Notes | Sixth Semester,
BSc.CSIT | Tribhuvan University (TU)

System testing
System testing of software is testing conducted on a complete, integrated system to evaluate the system’s compliance with its specified requirements. It involves integrating components to create a system or sub-system and may involve testing an increment to be delivered to the customer. System testing falls within the scope of black-box testing, and as such, should require no knowledge of the inner design of the code or logic.

System testing involves two phases and they are as follows;

  1. Integration testing
  2. Release testing

1. Integration testing:
Integration testing is the phase in software testing in which individual software modules are combined and tested as a group. It occurs after unit testing and before validation testing. Integration testing takes as its input modules that have been unit tested, groups them in larger aggregates, applies tests defined in an integration test plan to those aggregates, and delivers as its output the integrated system ready for system testing. The test teams have access to the system source code. It involves building a system from its components and testing it for problems that arise from component interactions.

Top-down integration

  • Develops the skeleton of the system and populate it with components.
  • Start with high-level system and integrate from the top-down replacing individual components by stubs where appropriate.

Bottom-up integration

  • Integrate infrastructure components then add functional components.
  • Integrate individual components in levels until the complete system is created.

Testing approaches

  • Architectural validation
    -> Top-down integration testing is better at discovering errors in the system architecture.
  • System demonstration
    -> Top-down integration testing allows a limited demonstration at an early stage in the development.
  • Test implementation
    -> Often easier with bottom-up integration testing.
  • Test observation
    -> Problems with both approaches. Extra code may be required to observe tests.

2. Release testing:

  • The test team tests the complete system to be delivered as a black-box.
  • The process of testing a release of a system that will be distributed to customers.
  • Primary goal is to increase the supplier’s confidence that the system meets its requirements.
  • Release testing is usually black-box or functional testing
  • Based on the system specification only;
  • Testers do not have knowledge of the system implementation
(Visited 76 times, 1 visits today)

Posted By : Digvijay | Comment RSS | Category : Sixth Semester
Tag :

Post a Comment

Your email is never published nor shared. Required fields are marked *

*
*

Wordpress DMCA
Community | Toolbar | Android App | Founder/Developer : Hari Prasad Chaudhary | CSIT Portal Manager : Digvijay Chaudhary