Abstract
Currently, software tends to assume increasingly critical roles in our society so assuring its quality becomes ever more crucial. There are several tools and processes of software testing to help increase quality in virtually any type of software. One example is the so called Model-Based Testing (MBT) tools, that generate test cases from models. However, most of these tools have a configuration phase, where test input data is provided manually by the tester, which influences the quality of the test suite generated. By adding coverage analysis to MBT tools it is possible to give feedback and help the tester to define the configuration data needed to achieve the most valuable test suite as possible. This paper presents a tool, PARADIGM-COV, that produces coverage information both over the PARADIGM model elements (to assess if input data is adequate to cover the test goals and assess if preconditions are achievable), and during test case execution (to identify the parts of the model/code that were actually exercised).

Abstract
The incorrect requirements elicitation, requirements changes and evolution during the project lifetime are the main causes pointed out for the failure of software projects. The requirements in the context of Software as a Service are in constant change and evolution which makes even more critical the attention given to Requirements Engineering (RE). The dynamic context evolution due to new stakeholders needs brings additional challenges to the RE such as the need to review the prioritization of requirements and manage their changes related to their baseline. It is important to apply methodologies and techniques for requirements change management to allow a flexible development of SaaS and to ensure their timely adaptation to change. However, the existing techniques and solutions can take a long time to be implemented so that they become ineffective. In this work, a new methodology to manage functional requirements is proposed. This new methodology is based on collecting and analysis of information about the usage of the service to extract pages visited, execution traces and functionalities more used. The analysis performed will allow review the existing requirements, propose recommendations based on quality concerns and improve service usability with the ultimate goal of increasing the software lifetime. Copyright © 2014 SCITEPRESS - Science and Technology Publications.

Abstract
This paper presents a study aiming to assess the feasibility of using the Pattern Based GUI Testing approach, PBGT, to test mobile applications. PBGT is a new model based testing approach that aims to increase systematization, reusability and diminish the effort in modelling and testing. It is based on the concept of User Interface Test Patterns (UITP) that contain generic test strategies for testing common recurrent behaviour, the so-called UI Patterns, on GUIs through its possible different implementations after a configuration step. Although PBGT was developed having web applications in mind, it is possible to develop drivers for other platforms in order to test a wide set of applications. However, web and mobile applications are different and only the development of a new driver to execute test cases over mobile applications may not be enough. This paper describes a study aiming to identify the adaptations and updates the PBGT should undergo in order to test mobile applications.

Abstract
This paper presents a tool to filter/configure the test cases generated within the Model-Based Testing project PBGT. The models are written in a Domain Specific Language called PARADIGM and are composed by User Interface Test Patterns (UITP) describing the testing goals. To generate test cases, the tester has to provide test input data for each UITP in the model. After that, it is possible to generate test cases. However, without a filter/configuration of the test case generation algorithm, the number of test cases can be so huge that becomes unfeasible. So, this paper presents an approach to define parameters for the test case generation in order to generate a feasible number of test cases. The approach is evaluated by comparing the different test strategies and measuring the performance of the modeling tool against a capture-replay tool used for web testing.

Abstract
Pattern Based GUI Testing (PBGT) is a new methodology that aims at systematizing and automating the GUI testing process. It is supported by a Tool (PBGT Tool) which provides an integrated modeling and testing environment that supports the crafting of test models based on UI Test Patterns, using a GUI modeling DSL called PARADIGM. The tool is freely available as an Eclipse plugin, developed on top of the Eclipse Modeling Framework. This paper presents PBGT Tool, which has been successfully used in several projects, and more recently at industry level.

Abstract
A mudança climática não pode ser desmentida. Desde que a humanidade adquiriu o conhecimento da eletricidade que tem transformado todo o seu modo de viver em seu redor. Para a produção de eletricidade recorre-se, em parte, à combustão de materiais que libertam CO2 e que, pela quantidade emitida, potencialmente degrada o ambiente. Noutra perspetiva, em certas zonas geográficas, o acesso à energia elétrica é escasso. É neste contexto que surge a profissão de Software Testing. Neste artigo procura-se quantificar o contributo dos testes de software no desenvolvimento de aplicações que tenham em conta um consumo energético mais reduzido. Para atingir esse objetivo é proposta e aplicada uma metodologia para a medição de consumo e é definida uma fórmula matemática para apuramento da viabilidade económica dos testes. As consequências de um software que consuma menos energia serão de três ordens: a ambiental – na redução da emissão de CO2; a humana – pela possibilidade de mais pessoas utilizarem a capacidade energética instalada; e a financeira – na redução direta do custo do consumo.;Climate change cannot be ignored any longer. Since humanity has developed the knowledge of electricity and has shaped his existence in a way that we are all dependent on it. The generation of electricity is linked to the combustion of products that release CO2 into the atmosphere which has the potential to degrade the environment. On the other hand, some countries have a restricted access to electricity. It is in this context that a new profession emerges – the software testing. This article aims at quantifying the contribution of Software Testing in the energy consumption of software. To achieve this goal it is proposed and applied a simplified methodology for measuring consumption of software and it is defined a mathematical formula to calculate the economic viability of the tests. The consequences of an optimized software in its energy consumption will be: environmental – by reducing CO2 emissions; human – by allowing more people to use the already installed power capacity; and financial – by reduction of economical expenditure.