Analytical Review on Test Cases Prioritization Techniques: An Empirical Study

Abstract

Abstract-For conclusively predicting the quality of any software system, software testing plays an important but a vital role. For finding faults early and to observe failures (anomalies) before implementation stage, software testing is done and if bugs (defects) are detected then software is passed through maintenance phase. The success and failure of a software project is often attributed to the development methodology used. It is also observed that in many scenarios, the software engineering methods are not implemented in their true spirit. Moreover, many of the development methodologies don't cater the change very well, because they follow a predefined development path which allows very less deviation. In software testing, regression testing is the important type of software testing. When any change made on the software then regression testing is done to check that it doesn't influence other parts of software. In regression testing, test cases are prioritized in order to reuse new test cases and existing test cases. Test case prioritization is done by using different techniques. This paper presents a review of different test case prioritization techniques.

Metodología para elaboración de requerimientos en aplicaciones con servicios web

“…Analizando la literatura sobre metodologías ágiles, se puede apreciar la forma en que estas implementan fases de captura de requerimientos que distan un poco del mismo proceso sobre metodologías tradicionales, en el sentido de que se enfatiza en la elicitación de los aspectos más relevantes a nivel de negocio en las primeras etapas y de los aspectos más dependientes de la plataforma en las últimas etapas. Obviamente la evolución de las metodologías [ ágiles altera y modifica la forma en que se realiza la captura de requerimientos [6], la elicitación de requerimientos enfocada a metodologías ágiles está en crecimiento y cada vez se esperan teóricos que aterricen aspectos tenidos en cuenta cuando surgen cambios de paradigmas en los desarrollos de software; en este sentido, uno de estos paradigmas es el desarrollo orientado a servicios, el cual ha revolucionado la forma en la que se elicitan requerimientos y exige que la elicitación tenga en cuenta no solo a los usuarios de la aplicación, sino a los usuarios que son afectados indirectamente por el desarrollo de tales sistemas. La Tabla 1 expone los diferentes enfoques producto del análisis realizado.…”

Impact and Challenges of Requirement Engineering in Agile Methodologies: A Systematic Review

“…Extreme Programming (XP) depends on values of correspondence, simplicity, courage, and criticism [6]. Purpose of XP is to associate old and tested methods in manner that they strengthen each other.…”

“…412 | P a g e www.ijacsa.thesai.org [6] Whole team works together by using practices and feedback makes it possible to know status of work. XP discusses general practices and processes of software product development and what could possibly be done during procedure, it does not unequivocally discuss requirement techniques in detail.…”

Optimized Quality Model for Agile Development: Extreme Programming (XP) as a Case Scenario

“…FURPS model [4], classify attributes into two unique requirements, for example, Functional Requirements (F) which is characterized by predictable input and output and Non Functional Requirements in which U represents Usability, R represents Reliability, P represents Performance (incorporates practical prerequisites) and S represents Supportability (incorporates reinforcement, essential of plan, execution, interface) [9]. One drawback of the FURPS model is that it doesn't reflect the portability perspective, which might be a vital basis for application advancement, particularly for programming based frameworks [11].…”