Modeliais paremtas testavimas tampa vis populiaresnis. Sudėtingos programinės įrangos kokybės užtikrinimas ir modeliais orientuotas sistemų kūrimas yra pagrindinės šio testavimo būdo išpopuliarėjimo priežastys. Pagrindiniai šio darbo tikslai yra modeliais paremtų testavimo įrankių analizė ir jų tobulinimo galimybės. Darbe naudojama daugiau nei dešimt įvairių įrankių vertinimo kriterijų. Analizuojama testų padengimo kriterijų pritaikymo ir tobulinimo galimybės. Analizuojamos modeliais paremto proceso problemos ir pateikiami sprendimo būdai. Atlikta detali testų kūrimo kriterijų ir modelio perėjimo algoritmų analizė. Atlikus detalę kriterijų ir modelio perėjimo algoritmų analizę, pateikiama kriterijų apjungimo privalumai ir kaip naudojant įvairius kriterijus galima valdyti testų kūrimo procesą ir siekti 100 procentinio modelio padengimo. Pateikiama ir detaliai išanalizuojama kriterijų kūrimo metodika, kurią galim taikyti testavimo įrankiuose. / Model-based testing has become increasingly popular in recent years. Major reasons include the need for quality assurance for increasingly complex systems and the emerging model-centric development paradigm. The present thesis aims at analysing model-based testing tools and presents the possibilities for their improvement. More than dozen criteria are applied in analysing selected tools. The paper analyses the application of testing coverage criteria and presents their possible improvements. The problems occurring in the model-based testing process are being analysed and the solutions presented. The study contains an in-depth analysis of test coverage criteria and model traversal algorithms. A thorough analysis of test criteria and model traversal algorithms being performed, the advantages of the integration of test criteria are presented. Furthermore, a solution for managing the development process of test cases as well as pursuing a hundred percent model coverage is proposed. The paper presents a comprehensive analysis of test criteria development methodology that could be applied in testing tools.

abstract: A Cyber Physical System consists of a computer monitoring and controlling physical processes usually in a feedback loop. These systems are increasingly becoming part of our daily life ranging from smart buildings to medical devices to automobiles. The controller comprises discrete software which may be operating in one of the many possible operating modes and interacting with a changing physical environment in a feedback loop. The systems with such a mix of discrete and continuous dynamics are usually termed as hybrid systems. In general, these systems are safety critical, hence their correct operation must be verified. Model Based Design (MBD) languages like Simulink are being used extensively for the design and analysis of hybrid systems due to the ease in system design and automatic code generation. It also allows testing and verification of these systems before deployment. One of the main challenges in the verification of these systems is to test all the operating modes of the control software and reduce the amount of user intervention. This research aims to provide an automated framework for the structural analysis and instrumentation of hybrid system models developed in Simulink. The behavior of the components introducing discontinuities in the model are automatically extracted in the form of state transition graphs. The framework is integrated in the S-TaLiRo toolbox to demonstrate the improvement in mode coverage. / Dissertation/Thesis / Masters Thesis Computer Science 2016

O desenvolvimento de software baseado no paradigma Orientado a Objetos (OO) e baseado em componentes é uma realidade. Este trabalho trata de teste e validação dentro desse contexto. Observa-se que diversos trabalhos relacionados ao teste de programas OO vêm sendo desenvolvidos. Apesar de ser um ponto controverso, alguns pesquisadores consideram que critérios de teste desenvolvidos para o teste de programas procedimentais podem ser facilmente estendidos para o teste de programas OO, pelo menos para o teste de métodos. Ainda são poucas as iniciativas de estender critérios de fluxo de dados e critérios baseados em mutação, tradicionalmente utilizados no teste de programas procedimentais, para o teste de programas OO. O presente trabalho visa a contribuir na identificação e definição de recursos de teste e validação que possam ser utilizados no teste de programas OO, com ênfase nos critérios de teste baseados em fluxo de dados e em mutação, cobrindo as fases do teste de unidade e de integração. Além disso, para apoiar a aplicação desses critérios, é de fundamental importância o desenvolvimento de ferramentas automatizadas que permitam a realização de estudos comparativos e a transferência tecnológica para a indústria. Em suma, o presente trabalho traz contribuições teóricas, com a definição de critérios de teste; empírica, com a realização de estudos empíricos; e de automatização, com a definição e implementação de um ambiente integrado de teste e validação para programas OO. Exemplos são utilizados para ilustrar as idéias e ferramentas apresentadas neste trabalho. / The development of Object-Oriented (OO) and component-based software is a reality. This work investigates software testing and validation in this context. Several studies related with OO testing have been carried out. In spite of being a controversial point, some researchers state that the procedural testing criteria can be easily extended to OO program testing, for instance to the testing of methods. There are few initiatives aiming at applying data-flow and mutation-based criteria, traditionally used for procedural testing, to the test of OO programs. The present work aims at contributing to identify and define resources for OO program testing and validation, considering data-flow and mutation based testing criteria, involving the unit and integration testing phases. An integrated environment for testing and validation has been developed to support the application of these criteria. This environment provides means to comparative studies amongst the criteria and to technology transfer processes. This work provides contributions to the following testing perspectives: theoretical -- with the definition of testing criteria; empirical -- with the conduction of empirical studies; and to testing automation -- with the specification and implementation of an integrated environment for testing and validation of OO programs. Examples are provided to illustrate the ideas and tools presented in this work.

Användandet av mobila applikationer har växt radikalt de senaste åren och de samverkar med många system. Därför ställs det högre krav på kvaliteten och att applikationen ska anpassas till många olika enheter, operativsystem samt plattformar. Detta gör att test av mobila applikationer blivit viktigare och större. Detta arbete har bedrivits som en jämförande fallstudie inom området test av mobila applikationer samt testverktyg. Syftet har varit att beskriva hur testning av mobila applikationer sker idag vilket gjorts genom litteraturstudier och intervjuer med IT-företag. Ett annat syfte har varit att utvärdera fyra testverktyg, deras för- och nackdelar samt hur de kan användas vid testning av mobila applikationer och jämföras mot manuell testning utan testverktyg. Detta har gjorts genom att skapa förstahandserfarenheter baserat på användandet av testverktygen. Under arbetet har vi utgått från mobila applikationer som vi fått tillgång till av Triona, som varit vår samarbetspartner.Idag finns många olika testverktyg som kan användas som stöd för testningen men få företag har implementerat något eftersom det kräver både tid och kompetens samt valet av testverktyg kan vara svårt. Testverktygen har olika för- och nackdelar vilket gör att de passar olika bra beroende på typ av projekt och applikation. Fördelar med att använda testverktyg är möjligheten att kunna automatisera, testa på flera enheter samtidigt samt få tillgång till enheter via molnet. Utmaningarna är att det kan vara svårt att installera och lära sig testverktyget samt att licenserna kan vara dyra. Det är därför viktigt att redan innan implementationen veta vilka tester och applikationer testverktygen ska användas till samt vem som ska använda det. Utifrån vår studie kan slutsatsen dras att inget testverktyg är helt komplett men de kan bidra med olika funktioner vilket effektiviserar delar av testningen av mobila applikationer. / The use of mobile applications has grown dramatically in recent years and they interact with many systems. Therefore the requirement on the quality is higher and the application must often be adapted to many devices, operating systems and platforms. This means the testing of mobile applications becomes more and more important. This study has been conducted as a comparative case study in the field testing of mobile applications and testing tools. The aim has been to describe how the testing of mobile applications takes place today which have been made through literature studies and interviews with IT-companies. Another aim was to evaluate four testing tools, their advantages and disadvantages and how they can be used in the testing of mobile applications and compared to manual testing without testing tools. This was done by using and experience the testing tools. During the study, we have used mobile applications that we got access from Triona, who has been our partner.Today there are many different testing tools that can be used to support testing, but few companies have implemented these because it requires both time and expertise as well as the selection of testing tools can be difficult. Testing tools have different advantages and disadvantages which make them fit differently depending on the type of project and application. Advantages of using testing tools is the ability to automate, test on multiple devices simultaneously and get access to physical devices via the cloud. The challenges are that it can be difficult to install and learn the testing tool and that the licenses can be expensive. It is therefore important that even before implementation to know which tests and applications the testing tools will be used in and who will use it. Based on our study we can conclude that no testing tools are complete but they may contribute with different features which streamlines parts of the mobile applications testing.

Integral part of all systematically managed software development or maintenance projects is emphasis on continuous quality of all project activities. Because final quality of project deliverables (new or enhanced applications, preconfigured solutions as ie. SAP) is a very big influencer of project success and therefore also important influencer of long-term relationship between customer and contractor(s), this document focuses on ways how to proactively prevent from mistakes (within the whole software development lifecycle) and on techniques helping to establish better quality control of important deliverables through systematic approach, high quality tools and suitable metrics in software testing discipline. This document gradually exposes typical project areas where it is necessary to keep control on quality of project members' outputs, perceives testing in context of typical project consequences, offers practical recommendations in testing methodology, tools as well as widely tested technologies, and explains trends and risks in testing domain. The goal of this document is not only to document a wide range of possibilities given by frequently used testing techniques or tools but also to offer a practical guidance in deployment of test discipline. This document was written by comparing author's professional experience in software quality management with knowledge gathered by reading information sources attached to this document. This document consists of concrete conclusions of this comparison.

The Master thesis deals with the selection of test management tool for the type of project and an overview of these tools. The subject of the theoretical part is to familiarize reader with the concept of testing, its effect on the quality and risk, describe it as a process and what principles are used for testing. In the theoretical part we also focus on the division of testing by the model of the project life cycle and test levels and the description of the tools that are used for testing. In the practical part we describe agent for multi-criterial selection of test management tool, which have we created, preceded by a specification of the projects for which the agent was tested. In the next section we describe the test management tools, which were selected for comparison based on research. In the last part of the practical part the agent for multi-criterial selection is subjected to the test on three projects. The test has proven the agent to be correct and on that basis we were able to choose three specific tools for the three projects.

Testing is a crucial process for organizations to identify any defects, ensure high-quality standards, enhance customer experience, mitigate risks, and comply with regulations. With proactive identification and resolution of problems, efficient testing saves time, money, and effort, ultimately contributing to the organization's overall success. The ABB Robotics Quality Management team for New Product Development projects identified that the current testing is process-oriented which results in overlapping test activities, delays, and increased costs. The lack of a holistic approach was identified as the main problem for the testing processes. Testing for New Product Development in the robotics industry is a time-consuming and costly activity. To deliver high-quality and reliable robot solutions, it is essential to test the right items at the right stage of development. The purpose of this research is to build a Test Strategy for New Product Development projects at ABB Robotics. The major objectives for the generated test strategy include identification of the right test methodologies, early identification of bugs and failures, achieving sufficient test coverage through component, module, integration, and system levels of testing, testing at the right level and stage, early verification of all requirements, better product quality, accelerated time to market, and superior customer experience. This research will focus on the mentioned aspects and won't address certain areas such as how suppliers conduct their testing, how test data is transferred from suppliers to ABB Robotics, processes after new product development projects are completed, and the testing processes in customer service. The research methodology involves a thorough literature review, an analysis of internal documents, international standards, and interviews within ABB Robotics, as well as external interviews and benchmarking with three well-known companies in the industry. With the support of the findings, recognized patterns, and analysis, a test strategy with its three major key strategic themes aligned with ABB Robotics' research objectives was generated with an implementation plan.

Tendo em vista a grande atenção e aceitação que vem sendo dadas ao Paradigma Orientado a Objetos (OO) por parte de pesquisadores e desenvolvedores de software, uma das preocupações atuais do grupo de Engenharia de Software do ICMC-USP é o estabelecimento e validação de estratégias de teste de programas OO. Entre os interesses de pesquisa do grupo de Engenharia de Software do ICMC estão o Teste Baseado em Fluxo de Dados e o Teste de Mutação, que tiveram sua origem na década de 70. Considerando que o paradigma OO vem se destacando como uma das tendências de desenvolvimento de software, o que pode ser observado pelo grande número de programas desenvolvidos à luz desse paradigma, o presente trabalho visa a caracterizar o estado atual do teste de software OO tanto em termos de técnicas e critérios correntemente utilizados como em termos de ferramentas de teste de software disponíveis. A identificação e avaliação de critérios e ferramentas de suporte para o teste de software OO darão subsídios para a definição de novos estratégias de teste e para a especificação e implementação de ferramentas de apoio no contexto de software OO. / Having in mind the great attention and acceptance that have been given to de Object-Oriented (OO) paradigm by researches and developers, one of the current concerns of the ICMC-USP Software Engineering Group is the establishment and validation of testing strategies of OO programs. Among the research interests of the ICMC-USP Software Engineering Group are the Data Flow and Mutation based testing that had their origin in the 70 s. Considering that the paradigm OO has been highlighted as one of the software development tendencies, what can be observed by the great number of programs developed in the light of this paradigm, the aim of this work is to characterize the current state of OO software test both in terms of available tools and the underlying techniques and criteria. The identification and evaluation of criteria and tools for the OO software test will provide subsidies for the definition of new testing strategies and for the specification and implementation of supporting tools in the context of OO software.

Software testing is widely considered to be one of the most important parts of software development life-cycle. In this research, we investigated potential improvements in the testing process and design of automated test scripts inside Bombardier Transportation. For the creation of automated test scripts BT is using a group of programs called TAF (Test Automation Framework). These scripts are used for testing Train Control Management System (TCMS), software that is used for managing the train. TAF can export its test scripts in XML format. XML scripts are analyzed in order to identify the most frequent changes. To better understand the life cycle of automated Test scripts official documentation that defines the Verification and Validation process inside BT was analyzed. Also, an interview was conducted with one of the responsible persons for testing. We believe that we have found a possible solution for improving testing process and creation of automated test scripts in BT, and to evaluate it proof of concept tool was developed. The main idea behind the tool is to write the test script using keywords which are based on analysis that was conducted on test specification documentation. These keywords represent frequent actions that are being tested on the train. By storing those actions in keywords re-usability of test script is being increased. Also, because they are based on naturally language, they are having positive effect on readability and maintenance of the test script.

Tendo em vista a grande atenção e aceitação que vem sendo dadas ao Paradigma Orientado a Objetos (OO) por parte de pesquisadores e desenvolvedores de software, uma das preocupações atuais do grupo de Engenharia de Software do ICMC-USP é o estabelecimento e validação de estratégias de teste de programas OO. Entre os interesses de pesquisa do grupo de Engenharia de Software do ICMC estão o Teste Baseado em Fluxo de Dados e o Teste de Mutação, que tiveram sua origem na década de 70. Considerando que o paradigma OO vem se destacando como uma das tendências de desenvolvimento de software, o que pode ser observado pelo grande número de programas desenvolvidos à luz desse paradigma, o presente trabalho visa a caracterizar o estado atual do teste de software OO tanto em termos de técnicas e critérios correntemente utilizados como em termos de ferramentas de teste de software disponíveis. A identificação e avaliação de critérios e ferramentas de suporte para o teste de software OO darão subsídios para a definição de novos estratégias de teste e para a especificação e implementação de ferramentas de apoio no contexto de software OO. / Having in mind the great attention and acceptance that have been given to de Object-Oriented (OO) paradigm by researches and developers, one of the current concerns of the ICMC-USP Software Engineering Group is the establishment and validation of testing strategies of OO programs. Among the research interests of the ICMC-USP Software Engineering Group are the Data Flow and Mutation based testing that had their origin in the 70 s. Considering that the paradigm OO has been highlighted as one of the software development tendencies, what can be observed by the great number of programs developed in the light of this paradigm, the aim of this work is to characterize the current state of OO software test both in terms of available tools and the underlying techniques and criteria. The identification and evaluation of criteria and tools for the OO software test will provide subsidies for the definition of new testing strategies and for the specification and implementation of supporting tools in the context of OO software.