Skip to content
Free planNo credit card requiredStart writing
AI for Research home
AI for Research home
Dashboard
Sign inGet started

Search 250 million research papers

Read the abstract, see who wrote it and who cites it, and get the citation in APA, MLA, Chicago or Harvard.

About 10,000 papers for “System integration testing”

System integration testing by SoapUI

Jakub Petržilka · Digital Repository (National Repository of Grey Literature) · 2015

This diploma thesis is focused on software testing, especially on System integration testing phase and automatization of this process. The main objective of this thesis is to create case study, in which the open source system SugarCRM is fully tested via testing tool SoapUI. Testing process in case study is executed according to methodology, which is focused mainly on testing of web services by SoapUI testing tool. Theoretical part of the thesis is dedicated to explanation of testing process, test automation and terms, which are commonly used in testing. Next part is devoted to integration of infor-mation systems. Practical part is dedicated to creation of the case study. In this part, the SoapUI testing tool and system SugarCRM, are described. In the case study, all testing activities are presented.

Cited by 0

Testing Techniques in Continuous Integration System

Shpak, Yuliia · Brno University of Technology Digital Library (Brno University of Technology) · 2020

S vývojem informací, komunikací a technologií se moderní průmyslové řídicí systémy (ICS) potýkají čím dál více s otázkami automatického testováni pro zabezpečení stability a bezpečnosti systému. Z tohoto důvodu se testování stalo jednou z nejdůležitějších částí životního cyklu všech softwarů. V této diplomové práci budu zvažovat možnost využití stávajících zkušebních metod a nástrojů pro získání dostatečné jakosti a bezpečnosti softwaru v kontinuálních integračních systémech.

Cited by 0

System Integration Development and Testing Process

Vairio, Santeri · UTUPub (University of Turku) · 2023

Organizations' decision making and business operations are more efficient when all of the data that is available for the organization can be used for them. System integrations are used to transfer the data between all of the relevant systems as a solution to this. Even though system integrations have a lot in common with other types of software development, they have differences and unique characteristics. An integration platform that consists of numerous integrations is developed to the City of Espoo and issues were discovered during the development and testing activities of them. This thesis was done to find solutions for those found problems and to make the processes smoother and more cost effective. Espoo has multiple integration platforms, the one studied in this thesis is only one of them. In this thesis the system integration specific challenges are looked into and reflected to other types of software development using literature concerning the subjects. After that a case study was done in the integration platform project and as a result process models of current development and testing processes were done. Using literature, interviews and personal experience improvement ideas were made and applied to form an improvement development process model for the project as it was discovered that the testing process itself had no significant flaws as the problems were inherited from the development process before it. The results can be applied to all kinds of system integration projects, as the problems seem to be universal and found in pretty much every integration project.

Cited by 0Open access

IMPLEMENTASI UNIT TESTING, INTEGRATION TESTING, SYSTEM TESTING, DAN VALIDATION TESTING PADA APLIKASI BERBASIS WEBSITE

Alvin Valerian, Delon Bernady, Ferry Wahyudi et al. · JATI (Jurnal Mahasiswa Teknik Informatika) · 2025

Perkembangan teknologi informasi mendorong adopsi aplikasi berbasis website dalam mendukung operasional bisnis, termasuk di sektor kuliner seperti Kafe Saturdays. Dalam implementasinya, sistem kafe ini menghadapi sejumlah permasalahan, seperti kesalahan dalam proses pemesanan, ketidaksesuaian data stok, serta gangguan saat sistem digunakan secara bersamaan. Penelitian ini bertujuan untuk menguji kualitas sistem melalui empat metode pengujian perangkat lunak, yaitu unit testing, integration testing, system testing, dan validation testing. Unit testing dilakukan dengan pendekatan white box testing untuk memastikan bahwa setiap fungsi CRUD berjalan dengan benar. Sementara itu, integration testing, system testing, dan validation testing menggunakan pendekatan black box testing untuk menguji integrasi antar modul, stabilitas sistem secara menyeluruh, dan kesesuaian fitur sistem dengan kebutuhan pengguna akhir. Proses pengujian dilakukan secara sistematis dengan skenario yang mewakili kondisi nyata penggunaan aplikasi. Hasil pengujian menunjukkan bahwa sebagian besar fitur berjalan sesuai spesifikasi, modul berfungsi dengan baik, dan data tetap konsisten. Namun, ditemukan kendala pada validasi input dan penurunan performa ketika sistem menerima beban tinggi. Penelitian ini menyimpulkan bahwa penerapan metode pengujian yang terstruktur mampu meningkatkan kualitas perangkat lunak serta memberikan pengalaman pengguna yang lebih optimal.

Cited by 0Open access

Advanced Portable Life Support System Component Integration and System Testing

W. D. Coleman, Dan Reynolds · SAE technical papers on CD-ROM/SAE technical paper series · 1989

<div class="htmlview paragraph">A facility has been designed and built to perform the first integrated testing of Space Station Freedom Extravehicular Mobility Unit Portable Life Support System. The test articles are a non-venting thermal sink, a metal oxide CO<sub>2</sub> absorber, a quaternary amine CO<sub>2</sub> absorber, and a fast response CO<sub>2</sub> sensor. The water loop and vent loop of the EMU are simulated using facility fluid movers. Minimum volume and thermal mass were also drivers. Difficulties in system design and the resolution of each are discussed.</div>

Cited by 1

Industrial Ray DR / ICT integration inspection testing system (2) Software and Testing

Liang Lihong, Ding Kejian, Ding Keqin et al. · 2012

The paper introduces the component and function of the system software. The software adopts modular design as a detection system software development platform, which can develop professional testing software for the specific targets according to the user's requirements. The system testing showed that it can realize high quality image covering film radiography three class(A-class, AB class, B-class)according to the detection rate of speed and size of the acquisition frame rate. 1

Cited by 0

Industrial ray DR / ICT integration inspection testing system (1) Hardware system

Keqin Ding, Lihong Liang, Jian Fu · 2012

The multi-detector, multi-ray source switching function ray DR / ICT integration testing system has been developed, which covers international strongly development of ray digital imaging detection technology. Development of the test system forms the ray digital imaging product development capability of independent property serialization, and provides the conditions for the ray imaging detection technology.

Cited by 0

NASA's Space Launch System Moves into Testing and Integration

Lyles, Garry, Honeycutt, John, Cook, Jerry · NASA STI Repository (National Aeronautics and Space Administration)

NASA's Space Launch System (SLS) has moved from design and manufacturing into testing and integration for its first flight as early as December 2019. In 2017, the NASA/industry team completed manufacturing of all major structural elements for the launch vehicle for Exploration Mission-I (EM-1 ). That work included shipping the first major flight hardware element to the launch site. The team processed all four RS-25 engines for stage integration, cast all 10 booster flight motor segments, and manufactured all five major sections of the core stage. The program also completed major structural work on the B-2 test stand at Stennis Space Center, which will be used for the core stage "green run" test; delivered the core stage and engine simulators used for training; and much of the transportation equipment for the core stage. Engineers completed structural testing on the upper stage/payload section of the vehicle as well as the engine section test article. In 2018, the program will deliver the Orion Stage Adapter (OSA) to Exploration Ground Systems (EGS) at KSC and send the test articles for the core stage liquid hydrogen tank, liquid oxygen tank, and intertank to NASA's Marshall Space Flight center for structural testing. Additionally, workers will begin the challenging process of integrating the major sections of the 212-foot EM-1 core stage. This work is focused on the initial Block 1 variant of SLS, capable of launching more than 70 metric tons (t) to low Earth orbit (LEO). However, work concurrently is underway on the Block lB variant, which will enable 105 t to LEO and more than 37t to trans-lunar injection (TLI). Block lB will be the workhorse vehicle of NASA's lunar exploration plans. As the needs of the nation's deep space exploration program grow, SLS performance is designed to evolve to a payload mass of 130 t to LEO and up to 45t to TLI. The advantages of this mass - as well as volume- are critical to the entire exploration architecture for deep space exploration. They translate to greater capability, greater infrastructure and operational simplicity, less overall mission risk, and opportunities to accomplish unprecedented exploration and discovery. This paper will discuss SLS progress to date and planned future work.

Cited by 0Open access

Integration and Testing of Optical Imaging System for RASAT

Ee-Eul Kim, Young‐Wan Choi, Woong Choi et al. · 2007

An advanced imaging system, the optical imaging system (OIS) is being developed for a small Earth observation satellite, RASAT. OIS will produce high-resolution images in panchromatic and multi-spectral bands and it consists of one optical and one electronics units. Recently, we have completed the development of the OIS engineering/qualification model (EQM). As part of verification of EQM, functional and environmental tests were performed. Key system features of OIS and test result for EQM are summarized.

Cited by 3

Integration testing based on indirect interaction for embedded system

Muhammad Iqbal Hossain, Woo Jin Lee · International Journal of Reconfigurable and Embedded Systems (IJRES) · 2019

<span>Embedded systems comprise several modules that exchange data by interacting among themselves. Exchanging wrong resource data among modules may lead to execution errors or anomalies. Interacting resources produce dependencies between two modules where any change of resources by one module affects the functionality of another module. Several investigations of the embedded system such as aerospace or automobile system show interaction faults between modules are one of the major cause of critical software failures. Therefore, interaction testing is an essential phase to reduce the interaction faults and minimize the risk. The direct and indirect interaction between modules generates interaction faults where indirect interaction is made underneath the interface in which data dependence relationship with resources may cause a different outcome. We investigate errors based on the indirect interaction between modules and introduce a new test criterion for finding errors detectable by existing approaches in unit level but not in integration level. In this paper, we propose a noble approach to generate an interaction model using indirect interaction pattern and design test criteria based on different interaction errors to generate test cases. Finally, we use fault injection and data flow coverage techniques to evaluate the feasibility and effectiveness of our approach</span>

Cited by 0Open access

Selecting a suitable system architecture for testing and integration

Jong, ISM Ivo de, Boumen, R Roel, Mortel-Fronczak, JM Asia van de et al. · TU/e Research Portal (Eindhoven University of Technology) · 2007

A system architecture is selected in the early design phases of a product. A trade-off is made between the most important architectural views during this selection process. The required system functionality is realized in an architecture which is maintainable, extendible, manufacturable, testable and integratable. This work investigates how an architecture can be selected, such that it is testable and integratable. The elements of an architecture which is suitable for testing and integration are introduced first. These elements are: components, interfaces between components and a layering. The division of the system into components determines how the system can be integrated and how many integration steps are required. Next to that, not all components need to be selected for system level integration and testing. Some, low-risk, components are integrated and tested on a lower level or not tested at all. The selection of components to be considered for integration and testing also influences which interfaces are considered. The selection of an interface infrastructure influences integration and testing, next to the interfaces which result from component and interface selection. The interface infrastructure can reduce or increase the number of interfaces in the system. An interface infrastructure could also introduce that specific connectors need to be developed resulting in additional risk and more required testing. And finally, a layering defines how the system, consisting of components and interfaces, is clustered. This layering reduces the complexity of the system and therefore the complexity of the integration and test plan. The layering for integration and testing can be defined fairly late in the development process just before integration and testing begins. Next to that, the layering for integration and testing can be different than the normal organizational or functional layerings of a system. More layerings can be defined and used next to each other. Guidelines and examples of suitable selections of components, interface infrastructure and layerings will be given in the presentation.

Cited by 0

Integration of Artificial Intelligence in Manufacturing Lab Testing System

Dipak Kumar Banerjee, Ashok Kumar · Journal of Materials Processing and Design · 2024

This paper explores the integration of Artificial Intelligence (AI) in manufacturing lab testing systems, focusing on how AI can revolutionize traditional testing methods to enhance product quality, efficiency, and reliability. Traditional lab testing in manufacturing is often marred by inefficiencies, human error, and lengthy processing times, which can adversely affect production throughput and quality. With the advent of AI, new possibilities have arisen to automate and optimize these processes. This research provides a comprehensive review of current AI applications, case studies, and empirical data to demonstrate the potential of AI in addressing existing challenges in lab testing. By employing machine learning, neural networks, and computer vision, AI technologies enable enhanced precision, predictive insights, and reduced operational costs in lab testing. The paper further examines the future implications of AI integration in the industry, aiming to provide a clearer understanding of its benefits and the challenges that lie ahead. Through a systematic methodology that includes a robust literature review and data analysis, this study contributes significant insights into the transformative impact of AI on manufacturing lab testing systems.

Cited by 0Open access

Automated functional system integration testing of Suomi 100 satellite

Juha Lukkari · Aaltodoc (Aalto University) · 2018

A large portion of launched CubeSats have failed early on their missions. Potential
\nsource of failures has been identified from statistical data of CubeSat missions
\nas being inadequate functional system integration testing. In this thesis test
\nautomation was used to perform functional system integration testing for the
\nSuomi 100 CubeSat. Reusable software library, called CubeSatAutomation, was
\ndeveloped for test automation and testing was conducted with a widely used
\nopen source test automation framework known as Robot Framework. With the
\nperformed tests proper functionality was verified for essential satellite features such
\nas radio communication, telemetry, safe resets and battery recharging through the
\nsolar panels among others. The testing however identified certain issues in the
\nintegration of the payload radio instrument. The tests included the “Day in the
\nlife” testing and it is possible to anticipate that this test can increase the overall
\nsuccess rate of CubeSat missions. A testing guideline that includes this test is
\nrecommended to be added to the CubeSat project.

Cited by 1

Optimizing software testing life cycle : reducing effort use in integration- and system testing

Vänskä, Teemu · Theseus (Ammattikorkeakoulujen) · 2009

For a software company, it is very important to have a functional process that guarantees smooth work flow, and that is comprehensive for all roles of the company. But not all processes are suitable for real life; they only sound good in theory. I decided to make a research on different processes to see if it was possible to create a custom process to a company that is in a need for one.
\n
\nTo narrow the subject to be more specific, it was necessary to specify the target areas of the research, system testing and integration testing. For the research it was also important to consider the possible company roles this investigation would probably affect the most. Those roles were a software tester, a software developer, and a software specification writer.
\n
\nBefore the actual “brain storming” for the new solution could even take place, it was clear that some of the well known and already made software development processes would have to be reviewed and studied in order to have a better picture of the composition of a development process. Just studying processes and models wouldn’t have been enough; also the question “What kind of tests are there, and how are they done?” should be answered. That’s why I had to review different testing methods for this project also.
\n
\nAfter studying processes and models, testing methods, it was time to see how all the theories differed from reality, and what parts were the most likely reasons for those differences. Only after those analyzes it was possible to pursue the ultimate goal of this research.
\n
\nBut the result wasn’t what I at first expected. It wasn’t a magnificent scientific breakthrough, but vice versa; it was a moment of clarification. Only a theory of an improvement was achieved during this research, a collaboration of different process models mixed as a hybrid version, but the lesson itself was far greater than I would’ve ever imagined. It also made me see that I clearly wasn’t the only one thinking about these things.
\n
\nThere was no time for real life experiments. Continuing this project in the future would be interesting indeed, to see if my theory would actually work in practice. But that would require a lot more time, and I definitely would like to hear a second opinion of the theory.

Cited by 0Open access

<i>Traffic Service Position System No. 1B</i>: Integration and System Testing

Reza Ahmari, R. S. DiPietro, Steven Reed et al. · Bell System Technical Journal · 1983

The integration testing and system testing strategies used in the development of the Traffic Service Position System No. 1B (TSPS No. 1B) are described in this article. It discusses novel methods developed for the integration and testing of the first embedded application of the 3B20D Processor and DMERT operating system. The new testing techniques and project management aides, which were vital to the achievement of system quality for the Bell System service, are described. The first TSPS No. 1B went into service on November 20, 1981, in Fresno, California.

Cited by 1

Just TestIt! An SBST Approach To Automate System-Integration Testing

Terzano, Tommaso, Giuffrida, Luigi, Sapriza, Juan et al. · ArXiv.org · 2025

This paper introduces TestIt, an open-source Python package designed to automate full-system integration testing using a Software-Based Self-Test (SBST) approach. By dynamically generating test vectors and golden references, TestIt significantly reduces development time and complexity while supporting both simulation and FPGA environments. Its flexible design positions TestIt as a key enabler for the widespread adoption of CI/CD methodologies in open-source RTL development. A case study on the X-HEEP RISC-V microcontroller (MCU), which integrates a custom accelerator, showcases TestIt's ability to detect hardware and software faults that traditional formal methods may overlook. Furthermore, the case study highlights how TestIt can be leveraged to characterize system performance with minimal effort. By automating testing on the PYNQ-Z2 FPGA development board, we achieved a 11x speed-up with respect to RTL simulations.

Cited by 0Open access