Automated verification of compliance of non-functional requirements on mobile applications through metamorphic testing

Costa, Misael Silva Ferreira

doi:10.1109/icst46399.2020.00053

Cited by 1 publication

(3 citation statements)

References 14 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…However, there are challenges to evaluate some types of NFRs in the industry (Karhapää et al 2021). As stated, many NFRs (for example, reliability (Chen 2015)), specify qualities that are influenced by many aspects of a system (Júnior 2020), thereby placing prerequisites on data capture and storage and even access to the entire system. This circumstance stands in contrast to functional testing, where a function is often isolated or restricted to the testing of a single software component.…”

Section: Related Workmentioning

confidence: 99%

“…Most frequently, NFRs define cross-functional quality aspects of a system and, in some instances, are viewed as being more important than the system's functionalities (Júnior 2020). Due to their cross-functional characteristics, NFR verification and validation (Karhapää et al 2021) is a challenging task (Alsaqaf et al 2019).…”

Section: Introductionmentioning

confidence: 99%

“…Due to their cross-functional characteristics, NFR verification and validation (Karhapää et al 2021) is a challenging task (Alsaqaf et al 2019). Therefore, conventional NFR testing practices are primarily performed manually, which is neither efficient nor effective (Júnior 2020). In fact, faulty NFRs produce additional work, which can account for 40% to 50% of the total work done in some software projects (Wagner 2006;Boehm and Basili 2005).…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Automated NFR testing in continuous integration environments: a multi-case study of Nordic companies

Yu,

Alégroth,

Chatzipetrou

et al. 2023

Empir Software Eng

View full text Add to dashboard Cite

Context Non-functional requirements (NFRs) (also referred to as system qualities) are essential for developing high-quality software. Notwithstanding its importance, NFR testing remains challenging, especially in terms of automation. Compared to manual verification, automated testing shows the potential to improve the efficiency and effectiveness of quality assurance, especially in the context of Continuous Integration (CI). However, studies on how companies manage automated NFR testing through CI are limited. Objective This study examines how automated NFR testing can be enabled and supported using CI environments in software development companies. Method We performed a multi-case study at four companies by conducting 22 semi-structured interviews with industrial practitioners. Results Maintainability, reliability, performance, security and scalability, were found to be evaluated with automated tests in CI environments. Testing practices, quality metrics, and challenges for measuring NFRs were reported. Conclusions This study presents an empirically derived model that shows how data produced by CI environments can be used for evaluation and monitoring of implemented NFR quality. Additionally, the manuscript presents explicit metrics, CI components, tools, and challenges that shall be considered while performing NFR testing in practice.

show abstract

Section: Related Workmentioning

confidence: 99%