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 “Integration testing”
Rogério Paulo · 2013
This document is written as a dissertation to complete the module “CS339 Advanced Topics in Computer Science: Testing ” in University of Wales Swansea. The referencing materials are mainly based on the book “Software Testing
Cited by 0
Chris Hobbs · 2019
Cited by 0
2002
Cited by 0
John Watkins, Simon Mills · Cambridge University Press eBooks · 2010
The objective of integration testing is to demonstrate that modules comprising the application under test (AUT) interface and interact together in a correct, stable, and coherent manner prior to system testing. Integration testing is typically conducted by the development team and involves independent observation of the testing process. Integration testing may also be termed link or module testing, but it should not be confused with systems integration testing (see Chapter 8).
Cited by 0
John T. Taylor, Wayne T. Taylor · Apress eBooks · 2024
Integration testing is where multiple components are combined into a single entity and tested. In theory, all of the components have been previously tested in isolation with unit tests, and the goal of the integration testing is to verify that the combined behavior meets the specified requirements. Integration testing also serves as incremental validation of the product as more and more functionality becomes available.
Cited by 0
Auerbach Publications eBooks · 2015
Cited by 0
SpringerReference · 2011
Cited by 0
Auerbach Publications eBooks · 2013
Cited by 0
A. Jefferson Offutt · 2005
Cited by 1
Mabrouk Mahdhi · Apress eBooks · 2025
Testing is a cornerstone of modern application development. As applications grow in size and complexity, manual verification becomes insufficient, error-prone, and slow. Automated testing provides a systematic way to ensure correctness, maintain quality, and evolve systems with confidence. In the world of ASP.NET Core, testing is not an afterthought but a built-in part of the framework’s philosophy. Dependency Injection, configuration patterns, and modular design all contribute to making ASP.NET Core applications inherently testable.
Cited by 0
Milk, Rene · Figshare · 2015
Presentation given at the 2015 software tools seminar at the institute for computational and applied mathematics at the university of Münster.
Cited by 0Open access
Mark Grechanik, Gurudev Devanla · 2016
In integration testing, integrated software modules or components are evaluated as a whole to determine if they behave correctly. Mutation testing is recognized as one of the strongest approaches for evaluating the effectiveness of test suites, and it is important to generate effective mutants efficiently for integration tests. However, it is difficult to generate integration mutants that create an error state in one component with certain assurances that this error state will affect computations in some other components. Unfortunately, little research exists that addresses this big and important problem to improve the quality of integration test suites. In this paper, we propose a theory and a solution for generating mutants that specifically target integration tests. We formulate a fault model for integration bugs that uses static dataflow analysis to obtain information about how integrated components interact in an application. Integration mutants are generated by applying mutation operators to instructions that lie in dataflow paths among integrated components. We implemented our approach and evaluated it on five open-source applications. In comparison to muJava, our approach reduces the number of generated mutants by up to approximately 19 times with a strong power to determine inadequacies in integration test suites.
Cited by 15
Milk, Rene · Figshare · 2015
Presentation given at the 2015 software tools seminar at the institute for computational and applied mathematics at the university of Münster.
Cited by 0Open access
ResearchSpace, Operations · California Digital Library · 2026
Testing integration with DMP for conference in September
Cited by 0Open access
Stephen Zachary Beauregard Mr. · QSpace (Queen's University Library) · 2017
Cited by 0
2004
Cited by 0
Nikitin, Andrii · TIB KMO / FLOWWORKS GmbH · 2021
Shareable scripting cross-product scenarios Do you know difference between starting mariadb vs postgres server as a regular user? Or apache vs nginx? Or maybe want to know specifics of working example of starting rsync server? There is no difference and no specifics - just use generated start / status / stop scripts. And there is more: (spawn as many services as needed(\*), configure ssl for cluster, build services from source, ...) - without affecting your system(*). environs framework suggests a universal approach for managing various services by generating bash wrappers, with following benefits: - object oriented approach - it hides internal specifics of service handling and allows an easy way to review and tweak them; - brief scripts for complex scenarios in complex topologies, without privileged access to the system; - easy to compare behavior of verious topologies; - demonstrate "how-to" behavior, share reproducible cross-product scripted scenarios in bug reports or TDD / BDD; - no OS flavor limit - run everywhere where shell is(*); - no extra dependencies - run in cloud, container, VM, CI or local machine. The main goal behind environs framework it to cover early integration testing and provide a way to script and share cross-product behavioral scenarios without root access to the system. So far the framework includes scripting possibility for postgresql, apache, nginx, rsync , mariadb(*), openQA, MirrorBrain, MirrorCache, zypper.
Cited by 0Open access
Pretschner, Alexander; Gregor, Lena · mediaTUM (Technical University of Munich)
Cited by 0Open access
Lawrence P Sweeney · 2015
Cited by 0
2011
This chapter contains sections titled: Some I&T Myths Managing the 3Ps: People Managing the 3Ps: Process Visibility: Testing Techniques and Details Configuration Management Standards: Documenting the Test Plan Key Thoughts in this Chapter This chapter contains sections titled: References
Cited by 6