[pt] Esta dissertação apresenta uma solução para a geração e execução automática de testes funcionais a partir da descrição textual de casos de uso, visando verificar se determinada aplicação atende aos requisitos funcionais definidos por esta documentação. A ferramenta construída é capaz de gerar casos de teste semânticos valorados, transformá-los em código-fonte (para Java Swing e os frameworks de teste TestNG e FEST, na versão atual), executá-los, coletar os resultados e analisar se os casos de uso da aplicação atendem ou não a estes requisitos. Dentre os principais diferenciais da solução construída estão a cobertura de cenários de teste que envolvem múltiplos casos de uso, a cobertura de cenários envolvendo recursão, a possibilidade da definição de regras de negócio sobre dados existentes em bancos de dados de teste, a geração automática dos valores fornecidos nos testes e a geração de testes funcionais semânticos, num formato independente de linguagem de programação e frameworks de teste. / [en] This master s dissertation presents a solution for the automatic generation and execution of functional tests based on the textual use case description and aims to verify whether certain application matches its functional requirements defined by this documentation. The constructed tool is capable of generating valued semantic test cases, of transforming them into source code (for Java Swing and the TestNG and FEST frameworks, in the current version), of executing them, of collecting the results and of analyzing whether the application s use cases matches (or not) its requirements. The solution main differentials includes the coverage of test scenarios that involves more than one use case, the coverage of scenarios containing recursive flows, the possibility of defining business rules using data existing in test databases, as well as the automatic generation of test values, and the generation of semantic functional tests in a format independent of programming languages and frameworks.

In this study we examined dynamic visual acuity as a functional testing of the vestibulo- ocular reflex. Two groups were examined: 22 healthy seniors and 22 healthy young people as controls. We used two types of situations for testing: while walking on a treadmill at a speed of 2, 4 and 5 kmph, and with a subject's head passively moved in yaw and pitch plane. Visual acuity was measured with optotype charts (for the walking test it was a standard Snellen optotype chart at 6 m distance, for the test of head moves it was a Jaeger chart at 30 cm distance). The values obtained in these ways we related to values of a subject's static visual acuity, measured in the same conditions, just before the dynamic situations were examined. We found significant difference of dynamic visual acuity in senior group within each condition tested. We also found a significant decline as for difference of dynamic visual acuity in the senior group compared to young subjects - in the walking test at 4 and 5 kmph and in both head-moving conditions. These results indicate age-related impairment in function of vestibulo-ocular reflex. Based on our results, the test of passive head moves appears to be more suitable for ordinary clinical examination of dynamic visual acuity.

The topic of this thesis is the issue of software testing. The thesis places main emphasis on tools to support test management, manual and automated functional testing and last but not least the tools for defect tracking. The aim of this thesis is introduce readers with software testing, especially with tools that can be used to support testing. The aim is offer an overview of the basic commercial and freely distributed tools for test management, manual testing, automated functional testing and defect tracking. Another aim is design criteria that simplify selection of tool. The second aim of this thesis is practical example of the configuration and description of the basic work with tools IBM Rational - ClearQuest, ClearCase, Manual Tester and Functional Tester. The aims of this thesis were achieved by studying available sources and by own practical experience with the tools to support testing. The contribution of this thesis lies in the characteristics of the selected tools to support testing and especially in design of criteria by which tools can be selected. The last part of thesis provides practical instruction how to configure and work with the tools to support testing of IBM Rational. The thesis is conceived in three main parts. The first part attends to basic terms, which can be found in the area of testing, and to overview of types of tests. There are also described two most famous life-cycle models and methodology RUP. The second part attends to overview of tools to support testing, attention is given to areas: test management, manual testing, defect tracking, and automated functional testing. For each category of tools has been defined criteria according to which tools can be selected. The last part attends to practical example of setting and basic work with the selected tools to support testing of IBM Rational.

Goal of this thesis is to verify functions of hydraulic manifolds from new supplier, measure characteristics of pressure loss relative to flow rate and for proportional blocks also characteristics of flow rate relative to control voltage at constant inlet pressure. Verification will be carried out with proportional manifolds and on/off manifolds with different failure functions.

The diploma thesis is focused on an experimental design of low-noise asphalt mixtures. The theoretical part describes the problems of noise and methods for noise measurements. There are also specified the characteristics of various low-noise asphalt mixtures. The practical part addresses the experimental design of SMA 8 LA. Subsequently, the mixture is exposed to functional testing and the results are afterwards compared with the conventional type of stone mastix asphalt SMA 8 S. The second part is focused primarily on an experimental mixture design of a specific asphalt mixture type - coated macadam. There is especially solved the issue ofbinder drainage and the proportion of cracked grains during the compaction. The advantage of this mixture is the lower price demands cause by lower binder content and a smaller amount of fine aggregate. This mixture should be used as a base layer for low-loaded (traffic) roads. In the conclusion are thereafter evaluated the knowledge and the experience with the testing and designing of individual mixtures gained during the testing.

Studien undersöker de automatiserade testverktygen: Ghost Inspector och Selenium. En limiterad litteraturstudie och två fallstudier görs, för att undersöka och utvärdera testverktygen. Detta för att kunna tillgodose riktlinjer som är användbara, vid val av ett verktyg för att utföra regressionstestning på webbapplikationer.IStone använder Ghost Inspector som verktyg vid regressionstest på webb applikationer, eftersom det ger dem en effektiv konfigurering och underhålls- process. Selenium kräver mer ansträngning för konfigurering och underhåll, eftersom verktygen inte är en tjänst. Miljön i Ghost Inspector underlättar för iStone att exekvera test kontinuerligt och förser projektteamet med det senaste testresultatet. / The study evaluates the automatic testing tools: Ghost Inspector and Selenium. and focuses on comparing them in terms of the set up and maintenance processes. The study includes a limited literature study and two case studies. The purpose is to evaluate the tools and provide guidelines for choosing a regression testing tool when testing the functionality of web applications.IStone use Ghost Inspector as regressions testing tool on web applications, since it offers an effective set up and maintenance process. Selenium requires more effort to set up and maintain, since Selenium is not a service. The Ghost Inspector environment comforts iStone with the ability of executing test continuously and supplies the latest test results to the project team.

O Teste de software é uma atividade de garantia da qualidade que tem por finalidade diminuir o número de defeitos do software. Esta atividade contribui para redução do custo de manutenção e para a melhora da qualidade do software, durante o processo de desenvolvimento. Isso tem motivado a investigação e proposta de estratégias, técnicas, critérios e ferramentas de teste para diferentes paradigmas de desenvolvimento, tais como procedimental, orientado a objetos e orientado a aspectos. Vários estudos experimentais têm sido desenvolvidos para avaliar e comparar critérios de teste. Grande parte desses experimentos foram realizados com programas construídos sob um mesmo paradigma ou desconsiderando a influência do mesmo sobre os resultados. Entretanto, é importante avaliar o impacto de um paradigma específico sobre a atividade de teste uma vez que alguns defeitos podem estar relacionados ao seu uso. Este trabalho apresenta um estudo experimental realizado para caracterizar e avaliar o custo de aplicação e a dificuldade de satisfação de critérios de teste, comparando dois paradigmas: o orientado a objetos e o procedimental. O estudo considera critérios de teste funcionais e estruturais e utiliza um conjunto de programas do domínio de Estrutura de Dados. Os termos e fases do processo de experimentação controlada foram usados, à medida em que estes se mostraram adequados, para definir e executar o presente estudo. Os objetivos com a execução dessa pesquisa foram obter resultados iniciais sobre as questões investigadas bem como gerar artefatos que sirvam de base para a definição e condução de futuros experimentos e a criação de pacotes de laboratório. Além disso, pretende-se apoiar, por meio dos materiais gerados, o treinamento e o ensino da atividade do teste de software / Software Testing is a quality assurance activity that aims at reducing the number of software faults. This activity contributes for the reduction of maintenance costs and for software quality improvement during the development process. These factors have motivated the investigation and proposal of several testing strategies, techniques, criteria and tools for different programming paradigms, such as procedural, object-oriented and aspect-oriented. Regarding testing criteria, many experimental studies have been performed to evaluate and compare them. In general, these experiments comprise programs developed under the same paradigm or this influence over the results. However, some faults can be paradigm-related and it is important to evaluate its impact on the testing activity. This work presents an experimental study developed to characterize and evaluate the application cost and strength of testing criteria, comparing two programming paradigms: object-oriented and procedural. This study considers functional and strutural testing criteria and uses a set of programs from the data structure domain. Terms and phases from controlled experimentation process were used, as long as they showed to be adequated, to define and execute the present study. The research aims at obtaining initial results about the questions investigated as well as generating artifacts which support the definition and conduction of future experiments and the creation of laboratory packages. In addition, it intends to support, through the materials generated, the training and teaching of software testing activity

Submitted by PPG Ci?ncia da Computa??o (ppgcc@pucrs.br) on 2018-05-21T13:19:36Z No. of bitstreams: 1 FELIPE_AUGUSTO_KUENTZER_TES.pdf: 3277301 bytes, checksum: 7e77c5eb72299302d091329bde56b953 (MD5) / Approved for entry into archive by Sheila Dias (sheila.dias@pucrs.br) on 2018-06-01T12:13:22Z (GMT) No. of bitstreams: 1 FELIPE_AUGUSTO_KUENTZER_TES.pdf: 3277301 bytes, checksum: 7e77c5eb72299302d091329bde56b953 (MD5) / Made available in DSpace on 2018-06-01T12:33:57Z (GMT). No. of bitstreams: 1 FELIPE_AUGUSTO_KUENTZER_TES.pdf: 3277301 bytes, checksum: 7e77c5eb72299302d091329bde56b953 (MD5) Previous issue date: 2018-03-28 / ? medida que o projeto de VLSI avan?a para tecnologias ultra submicron, as margens de atraso adicionadas para compensar variabilidades de processo de fabrica??o, temperatura de opera??o e tens?o de alimenta??o, tornam-se uma parte significativa do per?odo de rel?gio em circuitos s?ncronos tradicionais. As arquiteturas resilientes a varia??es de atraso surgiram como uma solu??o promissora para aliviar essas margens de tempo projetadas para o pior caso, melhorando o desempenho do sistema e reduzindo o consumo de energia. Essas arquiteturas incorporam circuitos adicionais para detec??o e recupera??o de viola??es de atraso que podem surgir ao projetar o circuito com margens de tempo menores. Os sistemas ass?ncronos apresentam potencial para melhorar a efici?ncia energ?tica e o desempenho devido ? aus?ncia de um sinal de rel?gio global. Al?m disso, os circuitos ass?ncronos s?o conhecidos por serem robustos a varia??es de processo, tens?o e temperatura. Blade ? um modelo que incorpora as vantagens de projeto ass?ncrono e resilientes a varia??es de atraso. No entanto, o Blade ainda apresenta desafios em rela??o ? sua testabilidade, o que dificulta sua aplica??o comercial ou em larga escala. Embora o projeto visando testabilidade com Scan seja amplamente utilizado na ind?stria, os altos custos de sil?cio associados com o seu uso no Blade podem ser proibitivos. Por outro lado, os circuitos ass?ncronos podem apresentar vantagens para testes funcionais, enquanto o circuito resiliente fornece feedback cont?nuo durante o funcionamento normal do circuito, uma caracter?stica que pode ser aplicada para testes concorrentes. Nesta Tese, a testabilidade do Blade ? avaliada sob uma perspectiva diferente, onde o circuito implementado com o Blade apresenta propriedades de confiabilidade que podem ser exploradas para testes. Inicialmente, um m?todo de classifica??o de falhas que relaciona padr?es comportamentais com falhas estruturais dentro da l?gica de detec??o de erro e uma nova implementa??o orientada para teste desse m?dulo de detec??o s?o propostos. A parte de controle ? analisada para falhas internas, e um novo projeto ? proposto, onde o teste ? melhorado e o circuito pode ser otimizado pelo fluxo de projeto. Um m?todo original de medi??o de tempo das linhas de atraso tamb?m ? abordado. Finalmente, o teste de falhas de atrasos em caminhos cr?ticos do caminho de dados ? explorado como uma consequ?ncia natural de um circuito implementado com Blade, onde o monitoramento cont?nuo para detec??o de viola??es de atraso fornece a informa??o necess?ria para a detec??o concorrente de viola??es que extrapolam a capacidade de recupera??o do circuito resiliente. A integra??o de todas as contribui??es fornece uma cobertura de falha satisfat?ria para um custo de ?rea que, para os circuitos avaliados nesta Tese, pode variar de 4,24% a 6,87%, enquanto que a abordagem Scan para os mesmos circuitos apresenta custo que varia de 50,19% a 112,70% em ?rea, respectivamente. As contribui??es desta Tese demonstraram que, com algumas melhorias na arquitetura do Blade, ? poss?vel expandir sua confiabilidade para al?m de um sistema de toler?ncia a viola??es de atraso no caminho de dados, e tamb?m um avan?o para teste de falhas (inclusive falhas online) de todo o circuito, bem como melhorar seu rendimento, e lidar com quest?es de envelhecimento. / As the VLSI design moves into ultra-deep-submicron technologies, timing margins added due to variabilities in the manufacturing process, operation temperature and supply voltage become a significant part of the clock period in traditional synchronous circuits. Timing resilient architectures emerged as a promising solution to alleviate these worst-case timing margins, improving system performance and/or reducing energy consumption. These architectures embed additional circuits for detecting and recovering from timing violations that may arise after designing the circuit with reduced time margins. Asynchronous systems, on the other hand, have a potential to improve energy efficiency and performance due to the absence of a global clock. Moreover, asynchronous circuits are known to be robust to process, voltage and temperature variations. Blade is an asynchronous timing resilient template that leverages the advantages of both asynchronous and timing resilient techniques. However, Blade still presents challenges regarding its testability, which hinders its commercial or large-scale application. Although the design for testability with scan chains is widely applied in the industry, the high silicon costs associated with its use in Blade can be prohibitive. Asynchronous circuits can also present advantages for functional testing, and the timing resilient characteristic provides continuous feedback during normal circuit operation, which can be applied for concurrent testing. In this Thesis, Blade?s testability is evaluated from a different perspective, where circuits implemented with Blade present reliability properties that can be explored for stuck-at and delay faults testing. Initially, a fault classification method that relates behavioral patterns with structural faults inside the error detection logic and a new test-driven implementation of this detection module are proposed. The control part is analyzed for internal faults, and a new design is proposed, where the test coverage is improved and the circuit can be further optimized by the design flow. An original method for time measuring delay lines is also addressed. Finally, delay fault testing of critical paths in the data path is explored as a natural consequence of a Blade circuit, where the continuous monitoring for detecting timing violations provide the necessary feedback for online detection of these delay faults. The integration of all the contributions provides a satisfactory fault coverage for an area overhead that, for the evaluated circuits in this thesis, can vary from 4.24% to 6.87%, while the scan approach for the same circuits implies an area overhead varying from 50.19% to 112.70%, respectively. The contributions of this Thesis demonstrated that with a few improvements in the Blade architecture it is possible to expand its reliability beyond a timing resilient system to delay violations in the data path, but also advances for fault testing (including online faults) of the entire circuit, yield, and aging.

O Teste de software é uma atividade de garantia da qualidade que tem por finalidade diminuir o número de defeitos do software. Esta atividade contribui para redução do custo de manutenção e para a melhora da qualidade do software, durante o processo de desenvolvimento. Isso tem motivado a investigação e proposta de estratégias, técnicas, critérios e ferramentas de teste para diferentes paradigmas de desenvolvimento, tais como procedimental, orientado a objetos e orientado a aspectos. Vários estudos experimentais têm sido desenvolvidos para avaliar e comparar critérios de teste. Grande parte desses experimentos foram realizados com programas construídos sob um mesmo paradigma ou desconsiderando a influência do mesmo sobre os resultados. Entretanto, é importante avaliar o impacto de um paradigma específico sobre a atividade de teste uma vez que alguns defeitos podem estar relacionados ao seu uso. Este trabalho apresenta um estudo experimental realizado para caracterizar e avaliar o custo de aplicação e a dificuldade de satisfação de critérios de teste, comparando dois paradigmas: o orientado a objetos e o procedimental. O estudo considera critérios de teste funcionais e estruturais e utiliza um conjunto de programas do domínio de Estrutura de Dados. Os termos e fases do processo de experimentação controlada foram usados, à medida em que estes se mostraram adequados, para definir e executar o presente estudo. Os objetivos com a execução dessa pesquisa foram obter resultados iniciais sobre as questões investigadas bem como gerar artefatos que sirvam de base para a definição e condução de futuros experimentos e a criação de pacotes de laboratório. Além disso, pretende-se apoiar, por meio dos materiais gerados, o treinamento e o ensino da atividade do teste de software / Software Testing is a quality assurance activity that aims at reducing the number of software faults. This activity contributes for the reduction of maintenance costs and for software quality improvement during the development process. These factors have motivated the investigation and proposal of several testing strategies, techniques, criteria and tools for different programming paradigms, such as procedural, object-oriented and aspect-oriented. Regarding testing criteria, many experimental studies have been performed to evaluate and compare them. In general, these experiments comprise programs developed under the same paradigm or this influence over the results. However, some faults can be paradigm-related and it is important to evaluate its impact on the testing activity. This work presents an experimental study developed to characterize and evaluate the application cost and strength of testing criteria, comparing two programming paradigms: object-oriented and procedural. This study considers functional and strutural testing criteria and uses a set of programs from the data structure domain. Terms and phases from controlled experimentation process were used, as long as they showed to be adequated, to define and execute the present study. The research aims at obtaining initial results about the questions investigated as well as generating artifacts which support the definition and conduction of future experiments and the creation of laboratory packages. In addition, it intends to support, through the materials generated, the training and teaching of software testing activity

Today’s massive usage of smartphones has put a high demand on all application developers in the matter of security. For us to be able to keep using all existing and new applications, a process that removes significant security vulnerabilities is essential. To remove these vulnerabilities, the applications have to be tested. In this thesis, we identify six methods for functional and security testing of client-server applications running Android and Python Flask. Regarding functional testing, we implement Espresso testing and RESTful API testing. In regards to the security testing of the system, we do not only implement fuzz testing, sniffing, reverse engineering and SQL injection testing on a system developed by a student group in a parallel project, but also discover a significant security vulnerability that directly affects the integrity and reliability of this system. Out of the six identified testing techniques, reverse engineering exposed the vulnerability. In conjunction with this, we verified that the system’s functionality works as it is supposed to.