Software development can be thought of in two fairly distinct ways: on one hand, it is a scientific area in which scientific method is applied in terms of quantifiable measurements and empirical studies. On the other hand (as with many other principles) it is based on craftsmanship in which the best practices emerge with experience.TDD is one such practice, emerging from the community of software developers as a means of developing higher quality software. This thesis aimed to study whether or not TDD actually leads to an increase in quality. This was conducted by developing a client application for a company in southern Sweden called TN Datakonsult AB. The application receives and visualizes signals from industrial processes. An API with the intent to capture this data over HTTP was developed in C#. This API was written by using TDD, while the client that consumed the API was written without tests as a control group. The code metrics that were calculated were cyclomatic complexity, lines of code, depth of inheritance, code coverage and class coupling. The results shows that many of the benefits associated with TDD are derived from the ability to track that the application under development is behaving as expected at any given time. This is a quality aspect which is particularly difficult to measure, even though the code metrics pre-sented will assist the developer to keep track of the state of the application.

Mutation testing is a powerful, but resource intense technique for asserting software quality. This report investigates two claims about one of the mutation operators on procedural logic, the relation operator replacement (ROR). The constrained ROR mutant operator is a type of constrained mutation, which targets to lower the number of mutants as a “do smarter” approach, making mutation testing more suitable for industrial use. The findings in the report shows that the hypothesis on subsumption is rejected if mutants are to be detected on function return values. The second hypothesis stating that a test case can only detect a single top-level mutant in a subsumption graph is also rejected. The report presents a comprehensive overview on the domain of mutation testing, displays examples of the masking behaviour previously not described in the field of mutation testing, and discusses the importance of the granularity where the mutants should be detected under execution. The contribution is based on literature survey and experiment. The empirical findings as well as the implications are discussed in this master dissertation.

No description available.

Recently, covering arrays have been the subject of considerable research attention as they hold both theoretical interest and practical importance due to their applications to testing. In this thesis, we perform the first comprehensive study of a generalization of covering arrays called variable strength covering arrays, where we dictate the interactions to be covered in the array by modeling them as facets of an abstract simplicial complex. We outline the necessary background in the theory of hypergraphs, combinatorial testing, and design theory that is relevant to the study of variable strength covering arrays. We then approach questions that arise in variable strength covering arrays in a number of ways. We demonstrate their connections to hypergraph homomorphisms, and explore the properties of a particular family of abstract simplicial complexes, the qualitative independence hypergraphs. These hypergraphs are tightly linked to variable strength covering arrays, and we determine and identify several of their important properties and subhypergraphs. We give a detailed study of constructions for variable strength covering arrays, and provide several operations and divide-and-conquer techniques that can be used in building them. In addition, we give a construction using linear feedback shift registers from primitive polynomials of degree 3 over arbitrary finite fields to find variable strength covering arrays, which we extend to strength-3 covering arrays whose sizes are smaller than many of the best known sizes of covering arrays. We then give an algorithm for creating variable strength covering arrays over arbitrary abstract simplicial complexes, which builds the arrays one row at a time, using a density concept to guarantee that the size of the resultant array is asymptotic in the logarithm of the number of facets in the abstact simplicial complex. This algorithm is of immediate practical importance, as it can be used to create test suites for combinatorial testing. Finally, we use the Lovasz Local Lemma to nonconstructively determine upper bounds on the sizes of arrays for a number of different families of hypergraphs. We lay out a framework that can be used for many hypergraphs, and then discuss possible strategies that can be taken in asymmetric problems.

In software development process, there can be misunderstandings, communication problems between individual members of the development team and mistakes when writing code or designing applications. These problems need to be resolved before the application is released into the production environment. To discover these errors it is necessary to properly test the software product. All these activities are engaged in discipline called Software Quality Assurance (SQA), which is an integral part of the software development process. The thesis discusses this discipline and procedures for software testing using the Microsoft Visual Studio 2008. The main objective of this work is to create comprehensive methodology for automated testing of web and Windows applications in Microsoft Visual Studio and to verify that procedures in practice. The reader will learn the theoretical basis of software testing at the beginning of the thesis. In next chapter, there are described various features that Microsoft Visual Studio 2008 offers for software testing. Following chapter describes the applications testing in IBM Rational Functional Tester, which is suitable for Windows applications testing (Microsoft Visual Studio 2008 does not support this kind of tests). In other part of the work -- Case Study -- the reader will learn web and Windows applications testing. Case study can serve as a basis for further methodological manual for teams engaged in software testing. The usage of instruments for testing is explained in real examples. At the end of the work there are set out recommendations for the team collaboration using Microsoft Team Foundation Server, and there are also compared the testing instruments and reviewed functions that will come up with Microsoft Visual Studio 2010.

This thesis is focused on software testing, primarily on practical use of testing support tool HP Quality Center 11. Theoretical part of the thesis explains the basic concepts of testing, introduces the types of testing and pursues the role of testing in project management. Practical part demonstrates real use of HP Quality Center 11 in SEPA Direct Debit project in a financial institution, evaluates its benefits and shortcomings and suggests possible improvements.

This study is primarily focused on software testing, especially on regression tests and their automation. The main objective is to introduce and verify a novel procedure for implementation and automation of software regression testing. Specific objectives include putting regression testing into the context of other types of tests applied to software testing, introduction of a novel Methodology for analysis of automation of regression tests, introduction of a novel Methodology for analysis of implementation of regression tests, practical verification of the applicability of both methodologies on a real project and a suggestion of how to adapt these methodologies on the basis of practical usage. The theoretical part of this study summarizes the basic theory of software testing, decomposing it in detail, and introducing its various levels, types and categories. It also presents the field of test automation, explains its advantages and disadvantages and introduces an overview of test types, which are generally recommended for automation. More attention is paid to regression testing and its prerequisites and potential for automation. The practical part of this study consists of the proposition of two methodologies, explaining their usage in a particular practical project and focuses on the evaluation of success of practical utilization of both methodologies. Based on this evaluation, these methodologies are consequently extended. Outputs of the study are also extended variants of Methodology for analysis of automation of regression tests and Methodology for analysis of implementation of regression tests, which are available for usage on other practical projects.

The quality is probably the most significant property of a successful software product. As experience with many software projects has already shown, leaving out testing and quality management from software development process can result in vast and critical customer issues, which usually invoke additional expenses for the software production company. In the course of time, software testing as a discipline has therefore seized an important position among other software development activities. And due to the fact that the software, thanks to rising customer demands and growing competing products portfolio, is getting more complex, the more advanced software testing procedures need to be implemented. Test strategy and iteration planning, implementation of multiple test types into the test suite, test automation, evaluation, administration and maintenance: these activities are commonly required within larger software development projects. Formalized software testing is, nevertheless, being introduced also to projects using agile management techniques which, by management decision or target user industry, are supposed to deliver products of highest quality. This initiates the high focus on the software testing discipline. The purpose of this thesis is to design and implement a new system of software testing within a real project in the CertiCon a.s. company, for which software development is the main business activity. Current issues and gaps for possible improvement, gathered both by project management and the author himself, are analyzed in the first major part of this work and transformed into testing system requirements, which should cover both process changes as well as implementation/development of needed software supporting the process. The second part of thesis is covering the design of the new software testing system, focusing mainly on the area of test management and selection of appropriate software management tool. The final part of the thesis is aimed at implementation of the designed solution within a real organization environment and evaluates its benefits against the previously set requirements.

Orientador: Ana Cervigni Guerra, Rogerio Drummond / Dissertação (mestrado profissional) - Universidade Estadual de Campinas, Instituto de Computação / Made available in DSpace on 2018-08-07T22:07:00Z (GMT). No. of bitstreams: 1 Silva_EduardodeVasconcelos_M.pdf: 694246 bytes, checksum: 7be11f3a0bafc2a11d2340ac3bdcdc26 (MD5) Previous issue date: 2006 / Resumo: A atividade da escrita de casos de testes para software é em sua essência não determinística e por conseguinte envolve riscos. Por outro lado, o grau de densidade de testes dos requisitos do sistema sofre influência da forma que esses requisitos são interpretados. Uma proposta para sistematizar o processo de criação de casos de teste encontra-se no uso de uma rede Bayesiana que modela a arquitetura de testes a ser implementada, aliada a uma ponderação estatística de riscos a cenários. A rede é muito adequada a problemas não determinísticos e que envolvam riscos. Aliada ao uso da rede Bayesiana, essa sistematização engloba o critério de adequação, cujo objetivo é minimizar o impacto da cobertura de requisitos. Cada requisito do sistema é interpretado segundo critérios pré definidos. Como produto final desta proposta sistêmica, além do ferramental gráfico que possibilita a descrição dos casos de testes segundo uma seqüência lógica e simulação de cenários, têm-se uma matriz que reúne todos os casos de testes obtidos da rede e demais oriundos da análise dos requisitos, segundo o enfoque do critério de adequação. O estudo experimental sinaliza um incremento de quatro vezes e meio na densidade de testes de requisitos comparativamente a técnica tradicional. Na fase de análise há uma tendência de redução de esforço em torno de um quarto. Um interessante resultado dessa técnica sistematizada, está na identificação de cenários não previstos pelos requisitos o que vem agregar na atualização da documentação de design / Abstract: The task of writing software use cases is in essence non deterministic and therefore involves risks. On the other hand, the coverage level of requirements depends the way of document requirements are interpreted.In order to bring a systematic approach in developing software use cases, the Bayesian network technique helps supporting with this problem. The current software test architecture is modeled in a graphical way, adding scenario simulation and risk statistic. The network addresses very well risks and non deterministic scenarios.Along with the Bayesian Network , the proposed systematic approach encompasses the adequacy criteria which main goal is to improve requirements coverage. Each system requirement is interpreted according to well defined criteria. A matrix will be the final product, as a result from the current systematic approach. All use cases obtained from the network and those discovered thanks of adequacy criteria can be seen together. In addition this, the technique allows scenarios simulation. The experimental results show an increase of four times and half in requirements coverage, as compared against the traditional technique. In the analysis phase , there is a trend of reducing the effort by a factor of 4.One interesting result using this technique is the amount of new scenarios identified. Most of them are not properly described in the requirement document. This brings a powerful tool to add value in updating the design document / Mestrado / Engenharia de Software / Mestre em Ciência da Computação

Orientador: Eliane Martins / Dissertação (mestrado) - Universidade Estadual de Campinas, Instituto de Computação / Made available in DSpace on 2018-08-18T15:53:22Z (GMT). No. of bitstreams: 1 Ferreira_Jeferson_M.pdf: 10344068 bytes, checksum: f13e5d139255d50754dc668d1bbf3fc6 (MD5) Previous issue date: 2011 / Resumo: Para a construção de sistemas robustos, devem ser utilizadas técnicas de tolerância a falhas que podem ser implementadas através de mecanismos de tratamento de exceções. Esses mecanismos possibilitam o tratamento de possíveis exceções, ou até mesmo a continuação da execução das funcionalidades do sistema mesmo na presença de uma exceção. O uso dos mecanismos de tratamento de exceções para desenvolver sistemas de software em larga escala, juntamente com o fato de ser implementado por diversas linguagens modernas, confirma a importância desta prática de desenvolvimento. Por outro lado, o uso desses mecanismos tem suas desvantagens, impactando principalmente na complexidade dos sistemas. Um problema que ocorre com muita frequência é efetuar a validação do fluxo excepcional somente na fase de implementação. A detecção de um problema de especificação nesta etapa do processo, pode acarretar em um aumento nos custos e prazos para a entrega do software. Este trabalho apresenta uma abordagem que utiliza as técnicas de análise estática, normalmente empregadas para detectar falhas no código fonte, para antecipar a validação do fluxo excepcional de um componente de software durante o ciclo de desenvolvimento. A solução proposta utiliza as informações do fluxo de controle e fluxo de dados obtidas a partir de um modelo comportamental. O modelo utilizado nesta abordagem é o diagrama de atividades da UML, que passa por uma série de transformações até gerar um grafo de fluxo de controle interprocedimental. Durante este processo são executadas análises de fluxo de dados para inferir com precisão quais são os tipos de exceções podem ser lançadas em dado ponto do modelo. Também faz parte deste trabalho a apresentação de uma ferramenta de apoio para o processo de validação do fluxo excepcional. Esta ferramenta, denominada ADEX (Activity Diagram EXceptional flow analyzer), implementa os algoritmos utilizados para a conversão do diagrama de atividades no grafo de fluxo de controle interprocedimental. A ferramenta também oferece recursos para a visualização do fluxo de controle normal e excepcional do modelo / Abstract: In order to develop robust software, should be used fault tolerant techniques that can be implemented by exception handling mechanisms. These mechanisms allow the handling of possible exceptions or even the continued of execution of the system's functionalities, even in the presence of an exception. The use of exception handling mechanisms to develop large scale software systems together with the fact that several modern programming languages provide these mechanisms, confirm the importance of these mechanisms in practice. On the other hand, the use of these mechanisms has some disadvantages, principally impacting on the complexity of the systems. One problem that occurs very often is performing the validation of the exceptional flow only during the implementation phase. The detection of a specification problem at this stage of the process can lead the increasing of costs and delays to delivery the software. This paper presents an approach that uses static analysis techniques, usually used to detect anomalies in the source code, to antecipate the validation of the exceptional flow of a software component in the development cycle. The proposed solution uses the information of control flow and data flow gathered from a behavioral model. The model used in this approach is the UML activity diagram, which undergoes a series of transformations to generate a interprocedural control flow graph. During this process are performed data flow analysis to inferring precisely what kind of exceptions can be thrown at a specific point of the model. The presentation of a tool to support the validation of the exceptional flow, also is part of this work. This tool, called ADEX (Activity Diagram EXceptional flow analyzer), implements the algorithms used to convert the activity diagram in the interprocedural control flow graph. The tool also provides features for visualization of normal and exceptional control flow of the model / Mestrado / Ciência da Computação / Mestre em Ciência da Computação