Testing within Constraints: a Practical Approach

  • Juliana Herbert UFCSPA
  • Silvia Nane Make It Work

Resumo


Being able to assure and evaluate system functionality and reliability is essential when we consider the concept of software quality. Although the concept of quality is broader, all the other criteria are secondary if a system fails performing its functions. Software testing is one of the primary methods used in the validation and verification of output in software development industry. However, software testing is considered an expensive process, accounting for as much as 50% of the cost of developing software based systems. Considering this situation, this discipline is often under pressure due time, cost and skills constraints. Although software testing must be optimized, the idea of just adding these constraints affects negatively the effectiveness of the process. The optimization must be done using systematic testing, with the purpose to select reliable test cases. As it is not possible to assure that all the defects of the software under test were identified, it is important to be able to prioritize testing activities. This paper presents a practical approach to test within constraints. Using this approach, the "testing combo", it is possible to define 40 hours testing projects, prioritizing test cases based on the identified risks and on the business value. It is a collaborative approach, where testers and customers work together through daily reports evaluation. The paper also presents a case study where this approach was used in five different projects, in the context of a testing factory.
Palavras-chave: Engenharia de Software Baseada em Evidências, Gerência de Riscos, Métodos Ágeis de Desenvolvimento de Software, Teste Baseado em Riscos, Teste de Software
Publicado
19/09/2016
HERBERT, Juliana; NANE, Silvia. Testing within Constraints: a Practical Approach. In: SIMPÓSIO BRASILEIRO DE TESTES DE SOFTWARE SISTEMÁTICO E AUTOMATIZADO (SAST), 1. , 2016, Maringá/PR. Anais [...]. Porto Alegre: Sociedade Brasileira de Computação, 2016 . p. 136-145.