Student or educator? Sign up with your school email and get 6 months of Pro free.
CoChat

The DOI matches its Crossref record; 83 of the 94 references it cites were found in a registry or an index; 7 of the 99 sources its claims cite were checked for support.

Challenges and Solutions in Implementing Continuous Integration and Continuous Testing for Agile Quality Assurance

Open access
Bhanushali, Amit · 2023 · International Journal of Science and Research (IJSR)

Abstract

As software development undergoes a transformation, it necessitates a corresponding adaptation on the part of quality specialists. The fundamental feature of agile approach is quality, which is assessed by both developers and customers in order to enhance the system's overall quality. This approach has the potential to enhance the quality of output, but at the expense of less involvement from the quality assurance team. The Agile methodology places emphasis on expediting the software development process while also reducing costs. Additionally, within the framework of Agile Quality Assurance (QA) and software development, Continuous Integration (CI) and Continuous Testing are key methodologies. The programmers ensure that changes to the code are regularly applied, examined, and verified throughout the whole development cycle. Within the Agile Quality Assurance (QA) paradigm, continuous integration and continuous testing are important approaches that offer routine code integration, automated testing, and quick feedback. They play a key role in the swift and iterative delivery of software of the highest calibre in Agile development setups. This study's major goal is to address the Problems and Solutions of Putting Continuous Integration and Continuous Testing intoPractise for Agile Quality Assurance.Agile techniques, agile software quality assurance, continuous integration practices of agile software development, difficulties, and solutions for these practises have all been covered in this review article.Additionally, the practises for continuous testing in agile quality assurance, difficulties, and solutions have been studied in the following part.

Overview

CoChat Summary

TL;DR

This review examines challenges and solutions in implementing continuous integration (CI) and continuous testing (CT) for agile quality assurance, with attention to DevOps and agile testing practices. It synthesizes literature on CI/CT, agile QA time horizons, and reported benefits such as reduced development time and improved software quality.

Key findings

  • CI and CT are presented as key agile QA practices: CI involves frequent code integration, automated builds/tests, and quick feedback, while CT automates testing to provide continuous feedback and detect defects earlier.
  • The paper identifies agile testing challenges and solutions, including testing activities in the agile lifecycle, distributed agile testing, regression testing, and test-case prioritization; proposed solutions include stakeholder engagement, a distributed-environment framework, regression test selection using user-story graphs, and linguistic/risk-based prioritization.
  • Reported quantitative claims include: Saff’s estimate that continuous testing removes 92–98% of waste; an experiment showing continuous testing reduced overall development time by around 15%; DevOps use by several European banks yielded a 25% enhancement in online services; and Silva et al. found development–operations interaction lowered operational effort by 50% and DevOps reduced failures by 3%.
  • QA coverage varies by time horizon: heartbeat has the most QA practices (e.g., unit testing, continuous integration, pair programming), iteration has fewer, and release-level QA processes are difficult to locate; the paper proposes an independent tester role for the iteration horizon and session-based exploratory testing for the heartbeat horizon.

Methods

  • Design: a review article covering agile techniques, agile software quality assurance, CI practices, CT practices, and associated challenges and solutions.
  • Data/sample: existing literature and prior studies on agile QA, CI, CT, DevOps, and software testing; no primary empirical sample is reported.
  • Main analysis: thematic synthesis and comparison of agile QA practices using Itkonen et al.’s temporal pacing/time-horizon model and the Cycles of Control framework, with tables summarizing QA procedures, quality elements, and challenge–solution mappings.

Limitations

  • Stated: the study focuses only on continuous integration and testing methods in agile software development; future work could explore other agile methods such as pair programming and combine affected quality criteria into a single quality framework.
  • Stated: there is a lack of comprehensive guidance on integrating destructive and independent testing into agile development, a dearth of research on architecture’s impact on CT/CD in production settings, and a need for empirical evidence on TDD+CT synergy in industrial settings.
  • Evident: as a review, it does not provide primary empirical data or a systematic review protocol, and several conclusions rely on secondary literature and reported claims rather than new experiments conducted by the author.

Model-written summary. Check it against the paper before relying on it.

Integrity signals

Registry

Crossref · 10.21275/sr231021114758

Cites

83 of 83 references verified0 citation errors · 0 not checkable

Statistics

Nothing to recompute.

Figures

Image 1
From the PDF
Figure 2 Timeline of Cycles of Control [37]
Figure 2 Timeline of Cycles of Control [37]From the PDF
Image 3
From the PDF

Verification

Claims the paper makes

7 Valid · 16 Not valid · 84 Not checked · 84 Own results and interpretations

28 more claims

Create a free account to see all 191 claims and every source verdict.

See all claims — free account
  • Probably not a substantial claim. 148
  • It may state two separate claims as one. 48
  • The quote only partly states this claim. 1

Create a free account to see these claims.

Self-check

Percentages, sums and reported differences re-computed from the paper’s own numbers.

Each contradiction between two passages listed here was confirmed by an independent check.

3 of 3

Citations

Cites

Show all 94 references

Cited by

See all 11

Metadata

Authors
Bhanushali, A.
Affiliations
West Virginia University (US)
Corresponding author
Bhanushali, Amit
Venue
International Journal of Science and Research (IJSR)
Published
2023-10-05
Volume
12
Issue
10
Pages
1626-1644
ISSN
2319-7064 (ISSN-L)
OpenAlex
W4388193285
Cited by
11
References
94
Citations by year
2026: 2 · 2025: 4 · 2024: 3 · 2023: 2
FWCI
2.58
Type
journal article
Language
en
Open access
Licence
cc-by-sa
Locations
International Journal of Science and Research (IJSR) (publishedVersion, cc-by-sa)
Topics
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
  • Physical Sciences › Computer Science › Software › Software Testing and Debugging Techniques
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Research
Keywords
continuous integration, continuous testing, test automation, software quality, agile software development, implementation barriers

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

The claim verdicts this report counts are experimental: their accuracy is not yet measured.

A language model drew the claims from the paper on 2026-09-28, under version 3 of the claim definition (prompt extract-v3).

A second model labelled each claim on 2026-09-28 (model jev-1.13-20260917, definition revision gold-guideline-v0.2).

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review

How to cite

Cite CoChat for the checks on this page, and the paper for its own findings.

This page
CoChat. (2026). Citation check: Challenges and Solutions in Implementing Continuous Integration and Continuous Testing for Agile Quality Assurance. https://app.cochat.ai/papers/10.21275/sr231021114758
The paper
Bhanushali, A. (2023). Challenges and Solutions in Implementing Continuous Integration and Continuous Testing for Agile Quality Assurance. International Journal of Science and Research (IJSR). https://doi.org/10.21275/sr231021114758

Data sources

Bibliographic data: Semantic Scholar, OpenAlex, Crossref.

Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).

Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.