Atenção!


O atendimento às questões referentes ao Repositório Institucional será interrompido entre os dias 20 de dezembro de 2025 a 4 de janeiro de 2026.

Pedimos a sua compreensão e aproveitamos para desejar boas festas!

Logo do repositório

Prioritizing Test Cases with Markov Chains: A Preliminary Investigation

dc.contributor.authorRebelo, Luciana
dc.contributor.authorSouza, Érica
dc.contributor.authorBerkenbrock, Gian
dc.contributor.authorBarbosa, Gerson [UNESP]
dc.contributor.authorSilva, Marlon
dc.contributor.authorEndo, André
dc.contributor.authorVijaykumar, Nandamudi
dc.contributor.authorTrubiani, Catia
dc.contributor.institutionGran Sasso Science Institute - GSSI
dc.contributor.institutionUniversidade Tecnológica Federal do Paraná - UTFPR
dc.contributor.institutionUniversidade Federal de Santa Catarina (UFSC)
dc.contributor.institutionUniversidade Estadual Paulista (UNESP)
dc.contributor.institutionCiência e Tecnologia de São Paulo - IFSP
dc.contributor.institutionUniversidade Federal de São Carlos (UFSCar)
dc.contributor.institutionInstituto Nacional de Pesquisas Espaciais - INPE
dc.date.accessioned2025-04-29T20:15:33Z
dc.date.issued2023-01-01
dc.description.abstractTest Case Prioritization reduces the cost of software testing by executing earlier the subset of test cases showing higher priorities. The methodology consists of ranking test cases so that, in case of a limited budget, only the top-ranked tests are exercised. One possible direction for prioritizing test cases relies on considering the usage frequency of a software sub-system. To this end, a promising direction is to identify the likelihood of events occurring in software systems, and this can be achieved by adopting Markov chains. This paper presents a novel approach that analyzes the system scenarios modeled as a Markov chain and ranks the generated test sequences to prioritize test cases. To assess the proposed approach, we developed an algorithm and conducted a preliminary and experimental study that investigates the feasibility of using Markov chains as an appropriate means to prioritize test cases. We demonstrate the strength of the novel strategy by evaluating two heuristics, namely H1 (based on the transition probabilities) and H2 (based on the steady-state probabilities), with established metrics. Results show (i) coverage of 100% for both H1 and H2, and (ii) efficiency equal to 98.4% for H1 and 99.4% for H2, on average.en
dc.description.affiliationGran Sasso Science Institute - GSSI
dc.description.affiliationUniversidade Tecnológica Federal do Paraná - UTFPR
dc.description.affiliationUniversidade Federal de Santa Catarina - UFSC
dc.description.affiliationUniversidade Estadual Paulista - Unesp
dc.description.affiliationInstituto Federal de Educação Ciência e Tecnologia de São Paulo - IFSP
dc.description.affiliationUniversidade Federal de São Carlos - UFSCar
dc.description.affiliationInstituto Nacional de Pesquisas Espaciais - INPE
dc.description.affiliationUnespUniversidade Estadual Paulista - Unesp
dc.format.extent219-236
dc.identifierhttp://dx.doi.org/10.1007/978-3-031-43240-8_14
dc.identifier.citationLecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics), v. 14131 LNCS, p. 219-236.
dc.identifier.doi10.1007/978-3-031-43240-8_14
dc.identifier.issn1611-3349
dc.identifier.issn0302-9743
dc.identifier.scopus2-s2.0-85174440212
dc.identifier.urihttps://hdl.handle.net/11449/309433
dc.language.isoeng
dc.relation.ispartofLecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics)
dc.sourceScopus
dc.subjectMarkov chain
dc.subjectSoftware Testing
dc.subjectTest Case Prioritization
dc.titlePrioritizing Test Cases with Markov Chains: A Preliminary Investigationen
dc.typeTrabalho apresentado em eventopt
dspace.entity.typePublication
unesp.author.orcid0000-0002-5193-6218[1]
unesp.author.orcid0000-0001-7262-7863[2]
unesp.author.orcid0000-0001-8071-1723[3]
unesp.author.orcid0000-0002-1147-2519[4]
unesp.author.orcid0000-0002-6413-7888[5]
unesp.author.orcid0000-0002-8737-1749[6]
unesp.author.orcid0000-0002-9025-0841[7]
unesp.author.orcid0000-0002-7675-6942[8]

Arquivos

Coleções