White Paper in Integration Testing - Report Example

White Paper on Integration Testing Name of student Institution affiliation Date Table of Contents Table of Contents 2 Abstract 3 Problem Statement 3 Testing Method 4 How the Testing Method Solves the Problem 8 Conclusion 9 References 10 Abstract Integration testing is a widely used methodology is software development for testing code units or individual components of a software in order to detect various interface defects and verify how different software components interact. The different components can be tested either as single group or arranged in an iterative way. Once integration testing is done on all the components, it makes them ready for overall system testing. The testing process ensures the passage of information from one level to another and in the correct order. The modules are integrated and tested so that the entire software can eventually run successful. Therefore, the rationale of this white paper is to explain to the reader how integration testing is useful in solving probable problems in software development and more precisely to examine the testing process in detail, by exploring the various integration testing methods used, their merits and demerits, their diagrammatical representation and clearly draw reasons as to why the integration process is necessary to software developers. Problem Statement Software development requires several components or modules put together to function as a whole ( Langer, 2012). Were it not for integration testing, the combination and arrangement of individual units of code to function as a whole would look complicated or rather impossible. Thus, integration testing ensures harmony of the various components before the product can be released. There are several rules and guidelines followed in testing to ensure that every software component has been checked thoroughly and have no errors, so that, the software can perform its intended function. In the real world, software failures resulting from insufficient testing and quality checks is a critical problem to many businesses as it leads to heavy financial losses that hurts the brand identity and the companies. Among the software failure cases that should be solved using integration testing comprise of failures in automated transaction systems at stock exchange markets, patients prolonged exposure during radiotherapy as once experienced in Canada, faulty baggage handling systems at major airports, among others. Testing Method There are different methods used in integration testing. These include: big bang method, top-down method and the bottom-up method (Lau, 2004). Some integration patterns are also used and include the backbone integration, collaboration integration, integration of distributed services, layer integration, high-frequency integration and server integration. Big band method The big bang integrating testing approach is performed after completion of all the components or modules. Though it is most common, the ‘big bang,’ approach makes the problems almost impossible to determine. This method brings all points of integration together to facilitate end-to-end testing ( Langer, 2012). This test method has a threshold point at which more test cases can be run. A proactive approach supports a controlled incremental approach of integration testing that helps to keep the costs of testing lower. Figure 1 illustrate the big bang method of integration. Figure 1: Big Band Integration Method The big band method works well with small systems but has a number of disadvantages. For instance, localization of fault is difficult, and since a large number of interfaces are to be tested under this approach, some interface links can be missed easily. Bottom-up Testing In this approach, the lowest components are prioritized in testing and then used to assist in the testing of the higher components ( Langer, 2012). This process is repeated continually till the topmost component on the hierarchy has been tested. The entire process can presented by the diagram shown in Figure 2. Figure 2: Bottom Up Method of Integration Testing The merit of this method is that both the programming and the testing activities are done simultaneously, thus leading to improved efficiency in the development of the software (Summers, 2013). Further, unit testing of individual modules easily becomes successful. However, the disadvantage of this method is that the key interface defects may be trapped when the cycle has come to an end and we test the program in the actual environment in which to run, thus consuming a lot of time. Top-Down Testing This approach involves the testing of the top modules and the branches of the module are then tested stepwise up to the end of all the related modules. Figure 3: Top Down Integration Testing Method This approach of testing is carried out in an environment that is very close to reality, thus making the tested product more reliable. However, the basic functionality test is done at the end of the cycle. Irrespective of the testing method used, some overall procedure should be observed. This entails the preparation of integration test plans, design of the cases, scripts, and test scenarios, execution of the test cases and reporting of the defects, and continuous re-testing of the defects and tracking till the entire process of integration testing is completed successfully. How the Testing Method Solves the Problem Integration is a crucial step that we should focus on in software development. Prior to integration of a larger system, the smaller systems should be integrated. A large system might fail at various points and this can lead to waste of time and effort in debugging, and it may not be an easy task to fix the errors (Naik & Tripathy, 2008). Therefore, in order to come up with a large system successfully, the individual modules should be tested and assembled into subsystems and the subsystems are then assembled to come up with the entire system. Despite the fact that the software modules are tested, defects are bound to occur due to a number of reasons. For example, modules are developed by individual software developers whose programming and understanding differs from that of other programmers within the same team. Therefore, testing enables verification so that the separate modules can work together. Further, during the various stages of module development, the client may decide to come up with different requirements, thus necessitating the testing of these requirements at the end of the process, especially on where the modifications were done. Further, the testing is important because of the existence of external hardware whose interfaces may result in some errors. Conclusion Due to the changing technology, manufactured products and applications are becoming complex are a result of dependency and connectivity between processes, systems and infrastructure. Further, integration testing continues to bring to the testing community new challenges. Attempts to incorporate new components and services to the existing ones often bring about situations in which the user interface does not exist within the limits of the change. As discussed herein, the methods for integration testing are limited to big bang, top down, and bottom up methods. Each of the methods has its advantages and disadvantages, and which may be determined by the complexity of the problem. In the current competitive environment where time is a crucial commodity and where reduction in operational costs act as differentiating edge for a business, the demand for automated integrated testing is on the increase. Among the problems it addresses include decreasing the workforce needed in testing task, minimizing errors and reducing the troubleshooting time, hastening the testing process, ensuring compliance of the software and high quality. References Langer, A. M. (2012). Guide to software development: Designing and managing the life cycle. London: Springer. Retrieved from: http://site.ebrary.com/id/10523860 on 23rd September, 2014. Lau, K.-K. (2004). Component-Based Software Development: Case Studies. World Scientific. Retrieved from http://www.books24x7.com/marc.asp?bookid=11319 on 23rd September, 2014. Naik, K., & Tripathy, P. (2008). Software testing and quality assurance: Theory and practice. Hoboken, N.J: John Wiley & Sons. Retrieved from http://site.ebrary.com/id/10345897 on 23rd September, 2014. Summers, B. L. (2013). Effective methods for software and systems integration. Boca Raton, FL: CRC Press. Retrieved from http://www.crcnetbase.com/isbn/978-1-4398-7662-6 on 23rd September, 2014. Read More