En la etapa de prueba de software, es posible beneficiarse de la combinación de los requisitos con las actividades de especificación de prueba. Por un lado, la especificación de las pruebas requerirá un menor esfuerzo manual, ya que se definen o generan automáticamente a partir de la especificación de requisitos. Por otro lado, la propia especificación de requisitos terminará teniendo una mayor calidad debido al uso de un lenguaje más estructurado, reduciendo problemas típicos como ambigüedad, inconsistencia e inexactitud. Esta investigación propone un framework basado en modelos que promueve la práctica de generar casos de prueba basados ​​en la especificación de historias de usuario ágiles para validar que los requisitos funcionales estén incluidos en la versión final de las interfaces de usuario del software desarrollado. Para mostrar la aplicabilidad del enfoque, se utilizan una especificación de requisitos basada en historias de usuarios, un modelo de tarea que utiliza ConcurTaskTree y el lenguaje Sikulix para generar pruebas a nivel de interfaz gráfica. El enfoque incluye transformaciones; como modelos de tareas en scripts de prueba. Luego, estos scripts de prueba son ejecutados por el marco de automatización de pruebas de Sikulix.

While modern software development technologies enhance the capabilities of model-based/driven development, they introduce challenges for testers such as how to perform early testing at model level to ensure the quality of the model. In this context, we have developed an early testing technique supported by the CoSTest tool to validate requirements at model level. In this paper we describe an empirical evaluation of CoSTest with respect to its effectiveness in terms of its fault detection and test suite adequacy. This evaluation is carried out by model-level mutation testing using first order mutants (created by injection of a single fault) and high order mutants (containing more than one fault) with seven conceptual schemas (of different sizes) that represent the functionality of different software systems in different domains. Our findings show that the tests generated by CoSTest are effective at killing a large number of mutants. However, there are also some fault types (e.g. delete the references to a class attribute or an operation call in a constraint) that our test suites were not able to detect. CoSTest was more effective in terms of detecting fault types using high order mutants that first order mutants. Thus, CoSTest's effectiveness is affected by the mutant type tested.

We present CoSTest, a tool that supports the validation of Conceptual Schemas by using testing. The tool implements techniques for transforming instantiations from a Requirements Model into test case implementations by supporting a Model-driven architecture.

In Model-Driven Development (MDD), defects are managed at the level of conceptual models because the other artefacts are generated from them, such as more refined models, test cases and code. Although some studies have reported on defect types at model level, there still does not exist a clear and complete overview of the defect types that occur at the abstraction level. This paper presents a systematic mapping study to identify the model defect types reported in the literature and determine how they have been detected. Among the 282 articles published in software engineering area, 28 articles were selected for analysis. A total of 226 defects were identified, classified and their results analysed. For this, an appropriate defect classification scheme was built based on appropriate dimensions for models in an MDD context.