<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Hugo Bandeira Tavares on Medium]]></title>
        <description><![CDATA[Stories by Hugo Bandeira Tavares on Medium]]></description>
        <link>https://medium.com/@HugoSaxTavares?source=rss-4bf118ee381a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Y-4VTH8FaQ5gjdUk64Y4bw.jpeg</url>
            <title>Stories by Hugo Bandeira Tavares on Medium</title>
            <link>https://medium.com/@HugoSaxTavares?source=rss-4bf118ee381a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 08:49:56 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@HugoSaxTavares/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[What is Hexagonal Architecture…]]></title>
            <link>https://medium.com/@HugoSaxTavares/what-is-hexagonal-architecture-bdea81770b0e?source=rss-4bf118ee381a------2</link>
            <guid isPermaLink="false">https://medium.com/p/bdea81770b0e</guid>
            <category><![CDATA[hexagonal-architecture]]></category>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[software-patterns]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[architectural-patterns]]></category>
            <dc:creator><![CDATA[Hugo Bandeira Tavares]]></dc:creator>
            <pubDate>Thu, 25 May 2023 11:04:20 GMT</pubDate>
            <atom:updated>2023-05-25T16:57:16.259Z</atom:updated>
            <content:encoded><![CDATA[<h4>…and when to use and <strong>not to</strong> use it</h4><p>Hexagonal Architecture provides a strategy to design an application such that it remains loosely coupled with its external services and systems, improving maintainability, testability, and decoupling. It can be particularly useful for complex, business-oriented applications. However, it also requires a careful consideration of its potential complexity and the learning curve for developers.</p><h4><strong>History and Context</strong></h4><p>Hexagonal Architecture, also known as Ports and Adapters Architecture, was developed by Alistair Cockburn. The concept aims to create a loosely coupled application that can be easily connected to its software environment. This is achieved by isolating the application core (business logic) from external concerns through ports and adapters.</p><p>In Hexagonal Architecture:</p><ol><li><strong>Core</strong>: This is the inside part of the hexagon and consists of the business logic of the software. It is technology-agnostic and doesn’t depend on databases, UI, or external systems.</li><li><strong>Ports</strong>: These define the boundary or interface for the interactions between the core and the outside world. They could be divided into Primary (driving) ports and Secondary (driven) ports. Primary ports represent the API of the application (what the application can do), and secondary ports represent the outside services that the application needs (what the application needs).</li><li><strong>Adapters</strong>: Adapters are the outside part of the hexagon and provide the connection to the core. They translate the external world’s language (HTTP requests, database reads/writes, etc.) into the core’s language and vice versa.</li></ol><p>Hexagonal Architecture was developed to solve problems related to:</p><ol><li><strong>Maintainability</strong>: Hexagonal architecture allows you to change your database, UI, or any external services without affecting the core logic.</li><li><strong>Testability</strong>: Since the core logic is isolated from the outer world, it can be tested independently. It also makes it easy to simulate the outside world in tests using test doubles.</li><li><strong>Decoupling</strong>: It separates the concerns and makes the system less entwined and dependent on specific technologies, frameworks, and external systems. This allows more flexibility in choosing or replacing external components or services.</li></ol><h4>When to use</h4><p>Hexagonal Architecture should be used when:</p><ol><li>You anticipate the need to <strong>switch out databases, UIs, or other external services</strong>.<br>Alternatively, the same can be achieved through the usage of other architectural patterns such as <strong>Clean Architecture, Microservices Architecture, Service-Oriented Architecture (SOA), and Plugin Architecture</strong>.</li><li>You want to isolate your application from potential changes in the external world.<br>Alternatively, the same can be achieved through the usage of other architectural patterns such as <strong>Clean Architecture, Microservices Architecture, Service-Oriented Architecture (SOA), Layered or n-Tier Architecture, Event-Driven Architecture (EDA), and Domain-Driven Design (DDD)</strong>.</li><li>You want to maintain testability of the core business logic without needing a fully integrated environment.<br>Alternatively, the same can be achieved through the usage of other architectural patterns such as <strong>Clean Architecture, Microservices Architecture, Service-Oriented Architecture (SOA), Layered or n-Tier Architecture, Domain-Driven Design (DDD), and Test-Driven Design (DDD)</strong>.</li></ol><p>Regarding implementation, Hexagonal Architecture is more of a design philosophy than a specific framework or tool. However, there are many projects and systems where it’s been successfully implemented. It’s commonly applied in the development of enterprise and business-oriented applications where business rules and logic are complex and need to be isolated from external services or systems.</p><h4>Industry usage</h4><p>The implementation of this architecture is not tied to any specific technology stack; it’s more about the organization of the code and the management of dependencies.</p><ol><li><strong>Banking Systems<br></strong>Banking systems often have complex business rules that need to be isolated from external concerns such as user interfaces, databases, and external systems. Hexagonal Architecture is a suitable fit for such an environment. These systems interact with multiple different external systems, such as currency exchange rates services, fraud detection services, other banks, etc., all through the means of adapters. This architecture ensures the core application isn’t affected by the specifics of each external system but only their contracts as defined by the ports. This facilitates a system that is flexible, testable, and easily maintainable.</li><li><strong>Telecommunications Systems</strong><br>Telecom software often has to interface with a variety of subsystems and external services, from network hardware, billing systems, to customer support systems. Hexagonal Architecture can effectively isolate the core logic of the telecommunication system (like call routing, network management, or balance tracking) from these varying interfaces. If a new type of network hardware is introduced or a different billing system is adopted, this can be handled at the adapter level, minimizing the impact on the core system.</li><li><strong>Medical Systems</strong><br>Medical systems often have complex business rules and need to integrate with various external systems like patient databases, other hospital systems, insurance systems, etc. These systems can significantly benefit from Hexagonal Architecture by isolating the core business logic from the specifics of these external systems. It enhances the flexibility, testability, and maintainability of such systems.</li></ol><h4>Pros and Cons</h4><p>Pros of Hexagonal Architecture:</p><ol><li><strong>Flexibility</strong>: Allows you to easily switch out databases, UIs, or other external services.</li><li><strong>Testability</strong>: Makes it easier to test the core application without the need for an integrated environment.</li><li><strong>Decoupling</strong>: The core application becomes less entwined and dependent on specific technologies, which can be especially helpful for future-proofing your application.</li></ol><p>Cons of Hexagonal Architecture:</p><ol><li><strong>Overengineering</strong>: For simple applications, Hexagonal Architecture may be too complex and overengineered. If your application doesn’t require interactions with multiple types of databases, user interfaces, or external systems, this architectural pattern might add unnecessary complexity and development time.</li><li><strong>Learning Curve</strong>: Developers might need time to understand and implement the Hexagonal Architecture properly. It requires a shift from traditional layered architecture and demands a solid understanding of the concept of ports and adapters.</li><li><strong>Lack of Concrete Guidelines</strong>: Hexagonal Architecture provides a high-level design guideline rather than specific implementation details. This leaves a lot of decisions to the developers, which can lead to inconsistencies in implementation if not properly managed.</li><li><strong>Potential for Misuse</strong>: Misunderstanding or misusing the principles of Hexagonal Architecture can lead to issues like unnecessary abstractions, too many layers, or overuse of interfaces, resulting in an overly complex system that is hard to maintain and understand.</li><li><strong>Performance Trade-offs</strong>: Depending on the nature and requirements of your system, the extra layer of abstraction and indirection introduced by Hexagonal Architecture might have an impact on performance. This impact is generally negligible, but it’s something to consider for highly performance-sensitive systems.</li></ol><h4>Alternatives to Hexagonal Architecture</h4><p>Many of the benefits provided by the Hexagonal Architecture <strong>can also be achieved through the implementation of other architectural patterns</strong>, practices, or methods, albeit with their nuances. Here are some of the most commonly employed alternatives:</p><ol><li><strong>Clean Architecture</strong>: This is a pattern proposed by Robert C. Martin, also known as “Uncle Bob”. It is similar to Hexagonal Architecture in that it focuses on separation of concerns and decoupling of software elements. The main idea is that dependencies should point inwards towards higher-level policies, and the application should not depend on the database or any other external agency.</li><li><strong>Microservices Architecture</strong>: In a microservices architecture, each service is a separate, self-contained component. Each service can use a different database or interact with different external services without affecting the others. This architecture allows for a high degree of modularity and flexibility, but it comes with its own set of challenges like service orchestration and data consistency across services.</li><li><strong>Service-Oriented Architecture (SOA)</strong>: SOA is a design pattern where services are provided to other components through a communication protocol over a network. The services are loosely coupled, which means they can be replaced or changed without affecting the rest of the system.</li><li><strong>Layered or n-Tier Architecture</strong>: Layered Architecture also focuses on separation of concerns by categorizing the application functionality into distinct layers, such as presentation, business logic, and data access layers. This separation can help isolate the core application from changes in the UI or database.</li><li><strong>Event-Driven Architecture (EDA)</strong>: In an EDA, components communicate through events. The application core can be insulated from external changes by changing how events are handled or produced, without affecting the core business logic.</li><li><strong>Domain-Driven Design (DDD)</strong>: DDD is not an architecture itself, but a methodology that can be used with an architecture like Hexagonal or Clean Architecture. It focuses on the domain model, which can be isolated from infrastructure concerns. This means changes to external systems can be managed within the infrastructure layer.</li><li><strong>Test-Driven Development (TDD)</strong>: Although not an architectural pattern, TDD is a development practice that significantly enhances the testability of your code. It involves writing tests before writing the application code and can be combined with any architectural style.</li><li><strong>Dependency Injection</strong>: This is a technique whereby one object (or static method) supplies the dependencies of another object. It is a form of Inversion of Control (IoC) and can improve decoupling and testability.</li><li><strong>Plugin Architecture</strong>: This architecture is built around a core system with plugins providing additional functionality. Each plugin is isolated and can be swapped out without affecting the core system or other plugins.</li></ol><h4>Final words</h4><p>In this document we examined Hexagonal Architecture, an architectural pattern designed for flexibility and isolation from external factors. We emphasized that while this pattern aids in creating decoupled, easily testable applications, its complexity can be a hindrance. We strongly suggest considering alternatives that have proven effective and are easier to implement, being Clean Architecture, Layered Architecture, and Microservices as viable alternatives.</p><p>In short:</p><ul><li><strong>Clean Architecture</strong>, much like Hexagonal, allows for independent testing and decoupling, but with less cognitive overhead.</li><li><strong>Layered or n-Tier Architecture</strong>, a time-tested pattern, provides simplicity and directness, reducing the learning curve.</li><li><strong>Microservices</strong> offer independent testing and flexibility, with added advantages of scalability and fault isolation.</li></ul><p>Although the choice of architecture largely depends on specific project requirements, we underscore the importance of simplicity, proven effectiveness, and a shorter learning curve as compelling reasons to consider these alternatives to Hexagonal Architecture.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bdea81770b0e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[O StayAwayCovid vai nú?]]></title>
            <link>https://medium.com/@HugoSaxTavares/o-stayawaycovid-vai-n%C3%BA-88adfc14e6a3?source=rss-4bf118ee381a------2</link>
            <guid isPermaLink="false">https://medium.com/p/88adfc14e6a3</guid>
            <category><![CDATA[covid19]]></category>
            <category><![CDATA[portugal]]></category>
            <category><![CDATA[software]]></category>
            <category><![CDATA[aplicação]]></category>
            <category><![CDATA[software-test-automation]]></category>
            <dc:creator><![CDATA[Hugo Bandeira Tavares]]></dc:creator>
            <pubDate>Thu, 10 Sep 2020 16:30:30 GMT</pubDate>
            <atom:updated>2020-09-11T15:45:11.013Z</atom:updated>
            <content:encoded><![CDATA[<h3>O StayAway Covid vai nú?</h3><p>Está lançado o braço de ferro entre a comunidade <em>open-source</em> e os criadores da aplicação “<a href="https://stayawaycovid.pt/"><strong>StayAway Covid</strong></a>”, a aplicação que pretende proteger os portugueses do contágio do COVID-19, pela alegada ausência de testes na aplicação.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/660/1*CZiQB8K40vFUPGce1abAAA.jpeg" /><figcaption>Fonte: <a href="https://www.deco.proteste.pt/tecnologia/telemoveis/noticias/stayaway-covid-nao-recolhe-dados-mas-suscita-reservas">https://www.deco.proteste.pt/tecnologia/telemoveis/noticias/stayaway-covid-nao-recolhe-dados-mas-suscita-reservas</a></figcaption></figure><p>Publicado recentemente por uma equipa ligada ao INESC TEC, o projecto tem o seu código disponível no repositório <a href="https://github.com/stayawayinesctec/stayaway-app">StayAway-App</a> no Github, plataforma que aloja imensos projectos <em>open-source </em>e onde está também alojado o código do StayAway Covid.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*_AJ65Kvq3RcKg-FWA7Gd3Q.png" /><figcaption><a href="https://github.com/stayawayinesctec/stayaway-app">https://github.com/stayawayinesctec/stayaway-app</a></figcaption></figure><p>Antes de relatar a polémica “técnica” que envolve o projecto, precisamos de motivar a existência dos testes a uma aplicação e qual a razão para os automatizar.</p><ol><li><strong>A necessidade de procedimentos de teste que permitam verificar e validar o funcionamento de uma plataforma ou aplicação informática pode ser comparada à necessidade dos processos de qualidade que</strong>, por exemplo, <strong>a indústria farmacêutica exerce sobre os medicamentos que produz</strong>: mesmo as versões genéricas da Aspirina estão sujeitas ao controlo de qualidade e, assim sendo, a testes laboratoriais antes de serem lançadas para o mercado.</li><li>Já no que concerne à <strong>pertinência e relevância dos testes automáticos no contexto do desenvolvimento software, podemos compará-las àquilo que as empresas da indústria automóvel fazem antes de lançar novos veículos para o mercado</strong>: num ambiente controlado, praticamente isento de factores e intervenção humanos, colocam <em>crash dummies</em> ao volante dos veículos sob teste, os quais fazem mover-se autonomamente e em diversas configurações, por forma a obter os resultados das colisões e para que lhes sejam conferidos pontuações, como por exemplo a Euro NCAP. A utilização <em>crash dummies</em>, além de não suscitar questões éticas, traduz-se num custo baixo dos testes de colisão (<em>crash tests</em>), imprimem maior rigor e detalhe na análise dos dados antes, depois e após o impacto, bem como possbilitita a repetição exaustiva dos testes dado o relativo baixo custo dos <em>crash dummies</em>.</li></ol><p>Toda a polémica começou quando um utilizador do Github lançou um <em>issue</em> no qual questionava como poderia correr testes automáticos, para validar e verificar o funcionamento da aplicação.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*AVHCpALZuxIXq0i49aZ9TQ.png" /><figcaption>Fonte: <a href="https://github.com/stayawayinesctec/stayaway-app/issues/3">https://github.com/stayawayinesctec/stayaway-app/issues/3</a></figcaption></figure><p>Após algumas interacções, um dos membros da equipa responde algo que pode ser considerado alarmante para qualquer profissional do software: os componentes (<a href="https://github.com/DP-3T/">servidor DP-3T</a> e os SDKs, Software Development Kits) já seriam devidamente cobertos por testes.</p><p>Ainda assim, e mesmo depois de um elemento da equipa do StayAway Covid ter “fechado” o <em>issue</em>, a discussão prosseguiu pela comunidade. Para melhor entender esta situação, pode traçar-se o paralelo com a seguinte metáfora da vida real:</p><ul><li>um cliente de uma operadora de telecomunicações dirige-se à loja para se queixar que não lhe estão a fornecer um serviço o qual existe por omissão,</li><li>um funcionário da operadora diz-lhe que “não é suposto ter o serviço” enquanto fecha a porta na cara do cliente, mesmo quando vários outros clientes se queixam da ausência do mesmo serviço pelo qual pagam mensalmente.</li></ul><h4>A diferença entre o mundo virtual e o mundo real ou físico é que no Github não existe uma autoridade como a ANACOM à qual os clientes acorrem quando têm um problema que não foi solucionado pela sua operadora.</h4><p>Ora qualquer programador com alguma experiência em campo entende várias coisas:</p><ul><li>A primeira é que, e por mais robustos e seguros sejam os componentes que utiliza, a integração destes é bastante susceptível a falhas, daí a necessidade da implementação de testes e que possam correr de forma automatizada, sejam eles testes de componentes, de integração e de sistemas. <strong>Os testes automáticos não são um capricho da qualidade: são sobretudo uma garantia de que há uma especificação que está a ser cumprida e, entre outros factores, que nenhuma alteração é feita ao código sem que esta seja verificada e validada por via dos testes automáticos, seja ela para resolução de um bug ou implementação de uma nova funcionalidade.</strong></li><li>A outra é que, em virtude do cariz deste projeto, <strong>os critérios de aceitação para publicar e distribuir uma aplicação destas deverão ser mais rigorosos do que um mero exercício académico ou que uma prova-de-conceito montada numa </strong><a href="https://pt.wikipedia.org/wiki/Hackathon"><strong><em>hackathon</em></strong></a><em>.</em> Em última instância, temos que considerar que um número substancial das pessoas que irão usar uma aplicação como o StayAway Covid não dispõe da literacia e do conhecimento técnico que lhes permita entender as consequências de uma aplicação não ter testes automáticos.</li><li>Por último, <strong>a confiança da própria comunidade <em>open-source</em> na equipa que desenvolve e mantém a aplicação</strong>: quando questionados sobre a pertinência dos testes, a resposta dada pela equipa do StayAway Covid, que insistiu em “fechar” o <em>issue</em> (o que significa que não é um problema que tenha que ser resolvido) indicia negligência das mais elementares prácticas de desenvolvimento de software.</li></ul><p>Mais adiante, um utilizador da comunidade Github, conscienciosamente apelando à relevância do tema, volta a abrir um <em>issue</em> subjacente aos testes automáticos:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*85WtCm-hfasd-sxO3akTxw.png" /><figcaption>Fonte: <a href="https://github.com/stayawayinesctec/stayaway-app/issues/7">https://github.com/stayawayinesctec/stayaway-app/issues/7</a></figcaption></figure><p>E aqui encontra-se uma referência para um outro <em>issue</em> o qual aponta a ausência de um procedimento, que já se tornou prática comum em diversos projectos de desenvolvimento de software, que visa corrigir vulnerabilidades nas <a href="https://npm.github.io/how-npm-works-docs/"><em>dependências NPM</em></a> usadas pelo StayAwayCovid. Estas dependências NPM podem ser vistas como os ingredientes para cozinhar a aplicação e, tal como qualquer chef deve verificar se os ingredientes, originários de produtores terceiros, estão dentro do prazo de validade ou têm a consistência e aspecto desejados para a confecção dos seus pratos, também na confecção do software o mesmo princípio deve ser aplicado, descartando ou substituindo as dependências NPM que não se encontram em condições para integrar na aplicação.</p><p>A equipa do StayAway Covid, considerando esta sugestão pertinente, estará eventualmente a desenvolver esforços no sentido de incorporar tal procedimento, dado o estado “aberto” (<em>open</em>) do <em>issue</em>, tendo mesmo classificado como “melhoria” (<em>enhancement</em>) do projecto.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*ZtVVShF9Hetl5xmyyvm8Iw.png" /><figcaption>Fonte: <a href="https://github.com/stayawayinesctec/stayaway-app/issues/8">https://github.com/stayawayinesctec/stayaway-app/issues/8</a></figcaption></figure><p>Já relativamente aos testes ao nível da Interface de Utilizador (em inglês <em>User Interface</em>, de onde vem a sigla “UI”), a equipa parece discordar também da sua pertinência, pelo menos, como parte integrante do projecto StayAway-app. Esta discussão surge no <em>issue #21</em>, no qual um novo utilizador do Github reitera a importância dos testes automáticos à interface. Novamente, a acção escolhida pela equipa do StayAwayCovid foi descartar a sugestão, com uma justificação pouco sólida e em seguida fechar o <em>issue</em>.</p><p>Existe uma diversidade enorme de produtos que podem responder a este desafio, o de criar testes unitários automáticos para o UI, tanto proprietários como <em>open-source</em> e que podem ser usados, desde <a href="http://appium.io/">Appium</a> a <a href="https://www.katalon.com/">Katalon Studio</a>, ou até mesmo <a href="https://www.browserstack.com/">BrowserStack</a> ou <a href="https://saucelabs.com/">Sauce Labs</a>, simulando as acções de um utilizador-final de forma repetida, autónoma e automática.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*JbDYd8rdIJ9hwImTihJmkw.png" /><figcaption>Fonte: <a href="https://github.com/stayawayinesctec/authcode-ui/issues/21">https://github.com/stayawayinesctec/authcode-ui/issues/21</a></figcaption></figure><p>Sem nos debruçarmos sobre decisões técnicas e dos comentários que a equipa do StayAway Covid apresenta, os quais programadores de carreira tentariam mitigar com o maior profissionalismo possível, acredito que há muito a considerar do ponto de vista técnico. Até porque numa primeira imersão em código de um projecto <em>open-source</em>, como é o caso do StayAway Covid, os programadores tendem a fazê-lo através dos testes automáticos, nomeadamente a partir dos <a href="https://glossary.istqb.org/en/search/component%20testing">testes unitários ou de componentes</a><a href="https://glossary.istqb.org/en/search/component%20testing).">.</a></p><p>Por outro lado, e enquanto gestor de qualidade de software, considero o impacto dos seguintes pontos:</p><p>1. <strong>Testes Automáticos ajudam a poupar tempo e dinheiro num projecto, uma vez que evitam que os programadores e os <em>testers</em> repitam de forma exaustiva as baterias de testes</strong>, sejam eles para confirmar as correcções ou garantir que as novas funcionalidades não afectam o comportamento das anteriores. Bastará pensarmos no tempo que demora a testar uma aplicação e multiplicar este tempo pelo número de versões ou as chamadas <em>releases</em> (que têm que funcionar de forma consistente), que logo chegaremos a números grandes o suficiente para frustrar o mais persistente dos <em>testers</em>.<br>Ou seja: como habitualmente o desenvolvimento de software decorre de forma incremental, os testes validam e verificam que as funcionalidades não são afectadas negativamente, ao passar de uma versão X para uma versão X+1 (garantia de retro-compatibilidade) ou então que as correcções feitas a uma funcionalidade A surtiram efeito (os chamados “testes de confirmação”) e que as mesmas correcções não afectaram as restantes funcionalidades (conhecidos como “testes de regressão”), reutilizar testes para os repetir de forma automática logra-se numa poupança de tempo e recursos muito significativa para os projectos.</p><p>2. <strong>Testes automáticos ajudam aumentar a percentagem de código que já foi auditada, sem qualquer intervenção humana</strong>. Por exemplo: se concebermos um projecto que têm 1000 linhas de código e, para o qual, criámos testes que cobrem 85% dessas linhas de código (i.e.: 850 linhas de código que são “corridas” durante os testes), o esforço de aumentar a cobertura de 85% para os 95% não é, por norma, significativo e não implica mais do que a implementação de um número relativamente pequeno de linhas de teste para cobrir as 100 linhas de código que queremos atingir.</p><p>3. <strong>Testes automáticos traduzem-se em precisão, uma vez que até o <em>tester</em> mais diligente está sujeito a falhar durante os monótonos testes manuais</strong>. Uma ferramenta de testes automáticos é responsável por repetir nominal e uniformemente os testes, como já foi dito, e a maior parte delas produz relatórios que revelam o estado das aplicações e do seu código. Assim, os <em>testers</em> podem dedicar o seu tempo a automatizar novos testes ou até a melhorar o processo de qualidade subjacente a um projecto de software.</p><p>4. <strong>Testes automáticos fazem o que os testes manuais não conseguirão fazer em muitas situações, especialmente quando estamos a falar de testes de carga</strong> (que respondem a perguntas como por exemplo: “quantos utilizadores podem simultaneamente usar uma aplicação?”)<strong>, testes de performance </strong>(e.g.: “os tempos de resposta da aplicação são aceitáveis?”)<strong> e testes de stress</strong> (e.g: “qual o número mínimo de pedidos-por-segundo a partir do qual a aplicação deixa de dar resposta?”). Escalar uma plataforma ou aplicação pode representar por si só um desafio ao nível dos testes e esse desafio não é, usualmente, desempenhado pelos agentes humanos ou os <em>testers</em>.</p><p>5. <strong>Testes automáticos são uma das boas práticas que todo e qualquer projecto de software deve ter em consideração</strong>. Em particular, e já que estamos em 2020, <strong>espera-se que os projectos de software predominantemente sigam a filosofia <em>Agile</em></strong> e, por omissão, façam uso de <a href="https://www.agilealliance.org/glossary/tdd/"><strong>TDD, Test Driven Development</strong></a>. No âmbito do TDD, espera-se que um programador implemente o código de uma forma cíclica, seguindo a metáfora “<strong>RED-GREEN-REFACTOR</strong>”:</p><p>a. <strong>RED</strong> (vermelho): o programador implementa um teste unitário, que descreve um aspecto ou requisito da aplicação. O teste deverá ser corrido e falhar, de onde vem o “RED”, pois a aplicação ainda não tem a funcionalidade implementada.</p><p>b. <strong>GREEN </strong>(verde): o programador implementa então a versão mais simples do código que faça passar o teste, daí o “GREEN”.</p><p>c. <strong>REFACTOR </strong>(<em>refactorização</em>): o programador revê e altera o código até se encontrar em conformidade com os critérios de simplicidade do mesmo (passa a testes, não existe duplicação de código, o código é a expressão de uma ideia ou responsabilidade e, finalmente, é composto por um número mínimo de componentes).</p><p>d. Repetir o ciclo, acumulando testes ao longo do projecto.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*aWKa228igWcNrjdh9G8FLQ.jpeg" /><figcaption>Fonte: <a href="https://blog.cleancoder.com/uncle-bob/2014/12/17/TheCyclesOfTDD.html">https://blog.cleancoder.com/uncle-bob/2014/12/17/TheCyclesOfTDD.html</a></figcaption></figure><p>Finalmente, restará sublinhar que <strong>o custo da implementação dos testes automáticos é marginal quando numa fase inicial do projecto</strong>: se estes testes não forem implementados em tempo oportuno (i.e.: no arranque do projecto), o seu custo cresce exponencialmente, assim como o custo decorrente da não aplicação os mesmo em caso de falha da aplicação ou plataforma em causa. Esses custos tendem a ser monetários, contudo há também a mencionar custos legais, de reputação e da confiança para os criadores da dita aplicação ou plataforma, entre outros.</p><p>Resta questionarmo-nos quem, em última instância, vai custear as eventuais consequências da ausência de testes automáticos no StayAway Covid: será o INESC TEC, será o Estado Português ou serão os portugueses que instalaram a aplicação nos seus telemóveis?</p><blockquote>Notas finais:</blockquote><blockquote>1. Por opção pessoal, o artigo não obedece às normas do Novo Acordo Ortogáfico.</blockquote><blockquote>2. Uma das minhas preocupações enquanto <a href="https://www.linkedin.com/in/htavares/">Director de QA</a> na <a href="https://www.claritergroup.com/">Clariter Group</a> é <strong>informar os consumidores sobre Qualidade nos produtos e serviços digitais </strong>e consequentemenete <strong>alertar para importância e impacto dos processos de Qualidade no desenho e desenvolvimento dos mesmos</strong>. Não hesite em contactar-me caso pretenda obter mais informações sobre os serviços que prestamos, via <a href="https://www.linkedin.com/in/htavares/">LinkedIn</a> ou <a href="/service/mailto:hugo.tavares@claritergroup.com">email</a>.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=88adfc14e6a3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ISTQB Foundation Level Syllabus, Chapter 5 of 6: Test Management]]></title>
            <link>https://medium.com/@HugoSaxTavares/istqb-foundation-level-syllabus-chapter-5-of-6-test-management-a6b594135f09?source=rss-4bf118ee381a------2</link>
            <guid isPermaLink="false">https://medium.com/p/a6b594135f09</guid>
            <category><![CDATA[test-management]]></category>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[quality-software]]></category>
            <category><![CDATA[itsqb]]></category>
            <category><![CDATA[itsqb-certification]]></category>
            <dc:creator><![CDATA[Hugo Bandeira Tavares]]></dc:creator>
            <pubDate>Tue, 03 Dec 2019 00:42:37 GMT</pubDate>
            <atom:updated>2019-12-03T00:42:37.652Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Disclaimer: this article is a copy from the original document available <a href="https://www.istqb.org/downloads/send/2-foundation-level-documents/281-istqb-ctfl-syllabus-2018-v3-1.html">here</a>.<br>All rights belong to International Software Testing Qualifications Board (hereinafter called ISTQB®). ISTQB is a registered trademark of the International Software Testing Qualifications Board.</blockquote><blockquote>This is only here for study purposes of the author.</blockquote><h3>Keywords</h3><p>configuration management, defect management, entry criteria, exit criteria, product risk, project risk, risk, risk level, risk-based testing, test approach, test control, test estimation, test manager, test monitoring, test plan, test planning, test progress report, test strategy, test summary report, tester</p><h3>5.1 Test Organization</h3><h4>5.1.1 Independent Testing</h4><p>Testing tasks may be done by people in a specific testing role, or by people in another role (e.g., customers). A certain degree of independence often makes the tester more effective at finding defects due to differences between the author’s and the tester’s cognitive biases (see section 1.5). Independence is not, however, a replacement for familiarity, and developers can efficiently find many defects in their own code.</p><p>Degrees of independence in testing include the following (from low level of independence to high level):</p><ul><li>No independent testers; the only form of testing available is developers testing their own code.</li><li>Independent developers or testers within the development teams or the project team; this could be developers testing their colleagues’ products.</li><li>Independent test team or group within the organization, reporting to project management or executive management.</li><li>Independent testers from the business organization or user community, or with specializations in specific test types such as usability, security, performance, regulatory/compliance, or portability.</li><li>Independent testers external to the organization, either working on-site (insourcing) or off-site (outsourcing).</li></ul><p>For most types of projects, it is usually best to have multiple test levels, with some of these levels handled by independent testers. Developers should participate in testing, especially at the lower levels, so as to exercise control over the quality of their own work.</p><p>The way in which independence of testing is implemented varies depending on the software development lifecycle model. For example, in Agile development, testers may be part of a development team. In some organizations using Agile methods, these testers may be considered part of a larger independent test team as well. In addition, in such organizations, product owners may perform acceptance testing to validate user stories at the end of each iteration.</p><p>Potential benefits of test independence include:</p><ul><li>Independent testers are likely to recognize different kinds of failures compared to developers because of their different backgrounds, technical perspectives, and biases.</li><li>An independent tester can verify, challenge, or disprove assumptions made by stakeholders during specification and implementation of the system</li></ul><p>Potential drawbacks of test independence include:</p><ul><li>Isolation from the development team, leading to a lack of collaboration, delays in providing feedback to the development team, or an adversarial relationship with the development team.</li><li>Developers may lose a sense of responsibility for quality.</li><li>Independent testers may be seen as a bottleneck or blamed for delays in release.</li><li>Independent testers may lack some important information (e.g., about the test object).</li></ul><p>Many organizations are able to successfully achieve the benefits of test independence while avoiding the drawbacks.</p><h4>5.1.2 Tasks of a Test Manager and Tester</h4><p>In this syllabus, two test roles are covered, test managers and testers. The activities and tasks performed by these two roles depend on the project and product context, the skills of the people in the roles, and the organization.</p><p>The test manager is tasked with overall responsibility for the test process and successful leadership of the test activities. The test management role might be performed by a professional test manager, or by a project manager, a development manager, or a quality assurance manager. In larger projects or organizations, several test teams may report to a test manager, test coach, or test coordinator, each team being headed by a test leader or lead tester.</p><p>Typical test manager tasks may include:</p><ul><li>Develop or review a test policy and test strategy for the organization.</li><li>Plan the test activities by considering the context, and understanding the test objectives and risks. This may include selecting test approaches, estimating test time, effort and cost, acquiring resources, defining test levels and test cycles, and planning defect management.</li><li>Write and update the test plan(s).</li><li>Coordinate the test plan(s) with project managers, product owners, and others.</li><li>Share testing perspectives with other project activities, such as integration planning.</li><li>Initiate the analysis, design, implementation, and execution of tests, monitor test progress and results, and check the status of exit criteria (or definition of done).</li><li>Prepare and deliver test progress reports and test summary reports based on the information gathered.</li><li>Adapt planning based on test results and progress (sometimes documented in test progress reports, and/or in test summary reports for other testing already completed on the project) and take any actions necessary for test control.</li><li>Support setting up the defect management system and adequate configuration management of testware.</li><li>Introduce suitable metrics for measuring test progress and evaluating the quality of the testing and the product.</li><li>Support the selection and implementation of tools to support the test process, including recommending the budget for tool selection (and possibly purchase and/or support), allocating time and effort for pilot projects, and providing continuing support in the use of the tool(s).</li><li>Decide about the implementation of test environment(s).</li><li>Promote and advocate the testers, the test team, and the test profession within the organization.</li><li>Develop the skills and careers of testers (e.g., through training plans, performance evaluations, coaching, etc.).</li></ul><p>The way in which the test manager role is carried out varies depending on the software development lifecycle. For example, in Agile development, some of the tasks mentioned above are handled by the Agile team, especially those tasks concerned with the day-to-day testing done within the team, often by a tester working within the team. Some of the tasks that span multiple teams or the entire organization, or that have to do with personnel management, may be done by test managers outside of the development team, who are sometimes called test coaches. See Black 2009 for more on managing the test process.</p><p>Typical tester tasks may include:</p><ul><li>Review and contribute to test plans.</li><li>Analyze, review, and assess requirements, user stories and acceptance criteria, specifications, and models for testability (i.e., the test basis).</li><li>Identify and document test conditions, and capture traceability between test cases, test conditions, and the test basis.</li><li>Design, set up, and verify test environment(s), often coordinating with system administration and network management.</li><li>Design and implement test cases and test procedures.</li><li>Prepare and acquire test data.</li><li>Create the detailed test execution schedule.</li><li>Execute tests, evaluate the results, and document deviations from expected results.</li><li>Use appropriate tools to facilitate the test process.</li><li>Automate tests as needed (may be supported by a developer or a test automation expert).</li><li>Evaluate non-functional characteristics such as performance efficiency, reliability, usability, security, compatibility, and portability.</li><li>Review tests developed by others.</li></ul><p>People who work on test analysis, test design, specific test types, or test automation may be specialists in these roles. Depending on the risks related to the product and the project, and the software development lifecycle model selected, different people may take over the role of tester at different test levels. For example, at the component testing level and the component integration testing level, the role of a tester is often done by developers.</p><p>At the acceptance test level, the role of a tester is often done by business analysts, subject matter experts, and users. At the system test level and the system integration test level, the role of a tester is often done by an independent test team. At the operational acceptance test level, the role of a tester is often done by operations and/or systems administration staff.</p><h3>5.2 Test Planning and Estimation</h3><h4>5.2.1 Purpose and Content of a Test Plan</h4><p>A test plan outlines test activities for development and maintenance projects. Planning is influenced by the test policy and test strategy of the organization, the development lifecycles and methods being used (see section 2.1), the scope of testing, objectives, risks, constraints, criticality, testability, and the availability of resources.</p><p>As the project and test planning progress, more information becomes available and more detail can be included in the test plan. Test planning is a continuous activity and is performed throughout the product’s lifecycle. (Note that the product’s lifecycle may extend beyond a project’s scope to include the maintenance phase.) Feedback from test activities should be used to recognize changing risks so that planning can be adjusted. Planning may be documented in a master test plan and in separate test plans for test levels, such as system testing and acceptance testing, or for separate test types, such as usability testing and performance testing. Test planning activities may include the following and some of these may be documented in a test plan:</p><ul><li>Determining the scope, objectives, and risks of testing.</li><li>Defining the overall approach of testing.</li><li>Integrating and coordinating the test activities into the software lifecycle activities.</li><li>Making decisions about what to test, the people and other resources required to perform the various test activities, and how test activities will be carried out.</li><li>Scheduling of test analysis, design, implementation, execution, and evaluation activities, either on particular dates (e.g., in sequential development) or in the context of each iteration (e.g., in iterative development).</li><li>Selecting metrics for test monitoring and control.</li><li>Budgeting for the test activities.</li><li>Determining the level of detail and structure for test documentation (e.g., by providing templates or example documents).</li></ul><p>The content of test plans vary, and can extend beyond the topics identified above. Sample test plans can be found in ISO standard (ISO/IEC/IEEE 29119–3).</p><h4>5.2.2 Test Strategy and Test Approach</h4><p>A test strategy provides a generalized description of the test process, usually at the product or organizational level. Common types of test strategies include:</p><ul><li><strong>Analytical</strong>: This type of test strategy is based on an analysis of some factor (e.g., requirement or risk). Risk-based testing is an example of an analytical approach, where tests are designed and prioritized based on the level of risk.</li><li><strong>Model-Based</strong>: In this type of test strategy, tests are designed based on some model of some required aspect of the product, such as a function, a business process, an internal structure, or a non-functional characteristic (e.g., reliability). Examples of such models include business process models, state models, and reliability growth models.</li><li><strong>Methodical</strong>: This type of test strategy relies on making systematic use of some predefined set of tests or test conditions, such as a taxonomy of common or likely types of failures, a list of important quality characteristics, or company-wide look-and-feel standards for mobile apps or web pages.</li><li><strong>Process-compliant </strong>(or standard-compliant): This type of test strategy involves analyzing, designing, and implementing tests based on external rules and standards, such as those specified by industry-specific standards, by process documentation, by the rigorous identification and use of the test basis, or by any process or standard imposed on or by the organization.</li><li><strong>Directed</strong> (or consultative): This type of test strategy is driven primarily by the advice, guidance, or instructions of stakeholders, business domain experts, or technology experts, who may be outside the test team or outside the organization itself.</li><li><strong>Regression-averse</strong>: This type of test strategy is motivated by a desire to avoid regression of existing capabilities. This test strategy includes reuse of existing testware (especially test cases and test data), extensive automation of regression tests, and standard test suites.</li><li><strong>Reactive</strong>: In this type of test strategy, testing is reactive to the component or system being tested, and the events occurring during test execution, rather than being pre-planned (as the preceding strategies are). Tests are designed and implemented, and may immediately be executed in response to knowledge gained from prior test results. Exploratory testing is a common technique employed in reactive strategies.</li></ul><p>An appropriate test strategy is often created by combining several of these types of test strategies. For example, risk-based testing (an analytical strategy) can be combined with exploratory testing (a reactive strategy); they complement each other and may achieve more effective testing when used together.</p><p>While the test strategy provides a generalized description of the test process, the <strong>test approach tailors the test strategy for a particular project or release</strong>. The test approach is the starting point for selecting the test techniques, test levels, and test types, and for defining the entry criteria and exit criteria (or definition of ready and definition of done, respectively). The tailoring of the strategy is based on decisions made in relation to the complexity and goals of the project, the type of product being developed, and product risk analysis. The selected <strong>approach depends on the context</strong> and may <strong>consider factors such as risks, safety, available resources and skills, technology, the nature of the system (e.g., custom-built versus COTS), test objectives, and regulations</strong>.</p><h4>5.2.3 Entry Criteria and Exit Criteria (Definition of Ready and Definition of Done)</h4><p>In order to exercise effective control over the quality of the software, and of the testing, it is advisable to have criteria which define when a given test activity should start and when the activity is complete. Entry criteria (more typically called definition of ready in Agile development) define the preconditions for undertaking a given test activity. If entry criteria are not met, it is likely that the activity will prove more difficult, more time-consuming, more costly, and more risky. Exit criteria (more typically called definition of done in Agile development) define what conditions must be achieved in order to declare a test level or a set of tests completed. Entry and exit criteria should be defined for each test level and test type, and will differ based on the test objectives.</p><p>Typical <strong>entry criteria</strong> include:</p><ul><li>Availability of testable requirements, user stories, and/or models (e.g., when following a modelbased testing strategy).</li><li>Availability of test items that have met the exit criteria for any prior test levels Availability of test environment.</li><li>Availability of necessary test tools.</li><li>Availability of test data and other necessary resources</li></ul><p>Typical <strong>exit criteria</strong> include:</p><ul><li>Planned tests have been executed.</li><li>A defined level of coverage (e.g., of requirements, user stories, acceptance criteria, risks, code) has been achieved.</li><li>The number of unresolved defects is within an agreed limit.</li><li>The number of estimated remaining defects is sufficiently low.</li><li>The evaluated levels of reliability, performance efficiency, usability, security, and other relevant quality characteristics are sufficient.</li></ul><p>Even without exit criteria being satisfied, it is also common for test activities to be curtailed due to the budget being expended, the scheduled time being completed, and/or pressure to bring the product to market. It can be acceptable to end testing under such circumstances, if the project stakeholders and business owners have reviewed and accepted the risk to go live without further testing.</p><h4>5.2.4 Test Execution Schedule</h4><p>Once the various test cases and test procedures are produced (with some test procedures potentially automated) and assembled into test suites, the test suites can be arranged in a test execution schedule that defines the order in which they are to be run. The test execution schedule should take into account such factors as prioritization, dependencies, confirmation tests, regression tests, and the most efficient sequence for executing the tests.</p><p>Ideally, test cases would be ordered to run based on their priority levels, usually by executing the test cases with the highest priority first. However, this practice may not work if the test cases have dependencies or the features being tested have dependencies. If a test case with a higher priority is dependent on a test case with a lower priority, the lower priority test case must be executed first.</p><p>Similarly, if there are dependencies across test cases, they must be ordered appropriately regardless of their relative priorities. Confirmation and regression tests must be prioritized as well, based on the importance of rapid feedback on changes, but here again dependencies may apply.<br>In some cases, various sequences of tests are possible, with differing levels of efficiency associated with those sequences. In such cases, trade-offs between efficiency of test execution versus adherence to prioritization must be made.</p><h4>5.2.5 Factors Influencing the Test Effort</h4><p>Test effort estimation involves predicting the amount of test-related work that will be needed in order to meet the objectives of the testing for a particular project, release, or iteration. Factors influencing the test<br>effort may include characteristics of the product, characteristics of the development process, characteristics of the people, and the test results, as shown below.</p><p><strong>Product characteristics.</strong></p><ul><li>The risks associated with the product.</li><li>The quality of the test basis.</li><li>The size of the product.</li><li>The complexity of the product domain.</li><li>The requirements for quality characteristics (e.g., security, reliability).</li><li>The required level of detail for test documentation.</li><li>Requirements for legal and regulatory compliance.</li></ul><p><strong>Development process characteristics.</strong></p><ul><li>The stability and maturity of the organization.</li><li>The development model in use.</li><li>The test approach.</li><li>The tools used.</li><li>The test process.</li><li>Time pressure.</li></ul><p><strong>People characteristics.</strong></p><ul><li>The skills and experience of the people involved, especially with similar projects and products (e.g., domain knowledge).</li><li>Team cohesion and leadership.</li></ul><p><strong>Test results.</strong></p><ul><li>The number and severity of defects found.</li><li>The amount of rework required.</li></ul><h4><strong>5.2.6 Test Estimation Techniques</strong></h4><p>There are a number of estimation techniques used to determine the effort required for adequate testing.</p><p>Two of the most commonly used techniques are:</p><ul><li>The metrics-based technique: estimating the test effort based on metrics of former similar projects, or based on typical values.</li><li>The expert-based technique: estimating the test effort based on the experience of the owners of the testing tasks or by experts.</li></ul><p>For example, in Agile development, burndown charts are examples of the metrics-based approach as effort is being captured and reported, and is then used to feed into the team’s velocity to determine the amount of work the team can do in the next iteration; whereas planning poker is an example of the expert-based approach, as team members are estimating the effort to deliver a feature based on their experience (ISTQB-AT Foundation Level Agile Tester Extension Syllabus).</p><p>Within sequential projects, defect removal models are examples of the metrics-based approach, where volumes of defects and time to remove them are captured and reported, which then provides a basis for estimating future projects of a similar nature; whereas the Wideband Delphi estimation technique is an example of the expert-based approach in which groups of experts provides estimates based on their experience (ISTQB-ATM Advanced Level Test Manager Syllabus).</p><h3>5.3 Test Monitoring and Control</h3><p>The purpose of test monitoring is to gather information and provide feedback and visibility about test activities. Information to be monitored may be collected manually or automatically and should be used to assess test progress and to measure whether the test exit criteria, or the testing tasks associated with an Agile project’s definition of done, are satisfied, such as meeting the targets for coverage of product risks, requirements, or acceptance criteria.</p><p>Test control describes any guiding or corrective actions taken as a result of information and metrics gathered and (possibly) reported. Actions may cover any test activity and may affect any other software lifecycle activity.</p><p>Examples of test control actions include:</p><ul><li>Re-prioritizing tests when an identified risk occurs (e.g., software delivered late).</li><li>Changing the test schedule due to availability or unavailability of a test environment or other resources.</li><li>Re-evaluating whether a test item meets an entry or exit criterion due to rework.</li></ul><h4>5.3.1 Metrics Used in Testing</h4><p>Metrics can be collected during and at the end of test activities in order to assess:</p><ul><li>Progress against the planned schedule and budget.</li><li>Current quality of the test object.</li><li>Adequacy of the test approach.</li><li>Effectiveness of the test activities with respect to the objectives</li></ul><p>Common test metrics include:</p><ul><li>Percentage of planned work done in test case preparation (or percentage of planned test cases implemented).</li><li>Percentage of planned work done in test environment preparation.</li><li>Test case execution (e.g., number of test cases run/not run, test cases passed/failed, and/or test conditions passed/failed).</li><li>Defect information (e.g., defect density, defects found and fixed, failure rate, and confirmation test results).</li><li>Test coverage of requirements, user stories, acceptance criteria, risks, or code</li><li>Task completion, resource allocation and usage, and effort</li><li>Cost of testing, including the cost compared to the benefit of finding the next defect or the cost compared to the benefit of running the next test.</li></ul><h4>5.3.2 Purposes, Contents, and Audiences for Test Reports</h4><p>The purpose of test reporting is to summarize and communicate test activity information, both during and at the end of a test activity (e.g., a test level). The test report prepared during a test activity may be referred to as a test progress report, while a test report prepared at the end of a test activity may be referred to as a test summary report.</p><p>During test monitoring and control, the test manager regularly issues test progress reports for stakeholders. In addition to content common to test progress reports and test summary reports, typical test progress reports may also include:</p><ul><li>The status of the test activities and progress against the test plan.</li><li>Factors impeding progress.</li><li>Testing planned for the next reporting period.</li><li>The quality of the test object.</li></ul><p>When exit criteria are reached, the test manager issues the test summary report. This report provides a summary of the testing performed, based on the latest test progress report and any other relevant information.</p><p>Typical test progress reports and test summary reports may include:</p><ul><li>Summary of testing performed.</li><li>Information on what occurred during a test period.</li><li>Deviations from plan, including deviations in schedule, duration, or effort of test activities.</li><li>Status of testing and product quality with respect to the exit criteria or definition of done.</li><li>Factors that have blocked or continue to block progress.</li><li>Metrics of defects, test cases, test coverage, activity progress, and resource consumption. (e.g., as described in 5.3.1, Metrics Used in Testing).</li><li>Residual risks (see section 5.5, Risks and Testing).</li><li>Reusable test work products produced.</li></ul><p>The contents of a test report will vary depending on the project, the organizational requirements, and the software development lifecycle. For example, a complex project with many stakeholders or a regulated project may require more detailed and rigorous reporting than a quick software update. As another example, in Agile development, test progress reporting may be incorporated into task boards, defect summaries, and burndown charts, which may be discussed during a daily stand-up meeting (see ISTQBAT Foundation Level Agile Tester Extension Syllabus).</p><p>In addition to tailoring test reports based on the context of the project, test reports should be tailored based on the report’s audience. The type and amount of information that should be included for a technical audience or a test team may be different from what would be included in an executive summary report. In the first case, detailed information on defect types and trends may be important. In the latter case, a high-level report (e.g., a status summary of defects by priority, budget, schedule, and test conditions passed/failed/not tested) may be more appropriate.</p><p>ISO standard (ISO/IEC/IEEE 29119–3) refers to two types of test reports, test progress reports and test completion reports (called test summary reports in this syllabus), and contains structures and examples for each type.</p><h3>5.4 Configuration Management</h3><p>The purpose of configuration management is to establish and maintain the integrity of the component or system, the testware, and their relationships to one another through the project and product lifecycle.</p><p>To properly support testing, configuration management may involve ensuring the following:</p><ul><li>All test items are uniquely identified, version controlled, tracked for changes, and related to each other.</li><li>All items of testware are uniquely identified, version controlled, tracked for changes, related to each other and related to versions of the test item(s) so that traceability can be maintained throughout the test process.</li><li>All identified documents and software items are referenced unambiguously in test documentation.</li></ul><p>During test planning, configuration management procedures and infrastructure (tools) should be identified and implemented.</p><h3>5.5 Risks and Testing</h3><h4>5.5.1 Definition of Risk</h4><p>Risk involves the possibility of an event in the future which has negative consequences. The level of risk is determined by the likelihood of the event and the impact (the harm) from that event.</p><h4>5.5.2 Product and Project Risks</h4><p>Product risk involves the possibility that a work product (e.g., a specification, component, system, or test) may fail to satisfy the legitimate needs of its users and/or stakeholders. When the product risks are associated with specific quality characteristics of a product (e.g., functional suitability, reliability, performance efficiency, usability, security, compatibility, maintainability, and portability), product risks are also called quality risks.</p><p>Examples of product risks include:</p><ul><li>Software might not perform its intended functions according to the specification.</li><li>Software might not perform its intended functions according to user, customer, and/or stakeholder needs.</li><li>A system architecture may not adequately support some non-functional requirement(s).</li><li>A particular computation may be performed incorrectly in some circumstances.</li><li>A loop control structure may be coded incorrectly.</li><li>Response-times may be inadequate for a high-performance transaction processing system.</li><li>User experience (UX) feedback might not meet product expectations.</li></ul><p>Project risk involves situations that, should they occur, may have a negative effect on a project’s ability to achieve its objectives. Examples of project risks include:</p><p><strong>Project issues.</strong></p><ul><li>Delays may occur in delivery, task completion, or satisfaction of exit criteria or definition of done.</li><li>Inaccurate estimates, reallocation of funds to higher priority projects, or general costcutting across the organization may result in inadequate funding.</li><li>Late changes may result in substantial re-work.</li></ul><p><strong>Organizational issues.</strong></p><ul><li>Skills, training, and staff may not be sufficient.</li><li>Personnel issues may cause conflict and problems.</li><li>Users, business staff, or subject matter experts may not be available due to conflicting business priorities.</li></ul><p><strong>Political issues.</strong></p><ul><li>Testers may not communicate their needs and/or the test results adequately.</li><li>Developers and/or testers may fail to follow up on information found in testing and reviews (e.g., not improving development and testing practices).</li><li>There may be an improper attitude toward, or expectations of, testing (e.g., not appreciating the value of finding defects during testing).</li></ul><p><strong>Technical issues.</strong></p><ul><li>Requirements may not be defined well enough.</li><li>The requirements may not be met, given existing constraints.</li><li>The test environment may not be ready on time.</li><li>Data conversion, migration planning, and their tool support may be late.</li><li>Weaknesses in the development process may impact the consistency or quality of project work products such as design, code, configuration, test data, and test cases.</li><li>Poor defect management and similar problems may result in accumulated defects and other technical debt.</li></ul><p><strong>Supplier issues.</strong></p><ul><li>A third party may fail to deliver a necessary product or service, or go bankrupt.</li><li>Contractual issues may cause problems to the project.</li></ul><p>Project risks may affect both development activities and test activities. In some cases, project managers are responsible for handling all project risks, but it is not unusual for test managers to have responsibility for test-related project risks.</p><h4>5.5.3 Risk-based Testing and Product Quality</h4><p>Risk is used to focus the effort required during testing. It is used to decide where and when to start testing and to identify areas that need more attention. Testing is used to reduce the probability of an adverse event occurring, or to reduce the impact of an adverse event. Testing is used as a risk mitigation activity, to provide feedback about identified risks, as well as providing feedback on residual (unresolved) risks.</p><p>A risk-based approach to testing provides proactive opportunities to reduce the levels of product risk. It involves product risk analysis, which includes the identification of product risks and the assessment of each risk’s likelihood and impact. The resulting product risk information is used to guide test planning, the specification, preparation and execution of test cases, and test monitoring and control. Analyzing product risks early contributes to the success of a project.</p><p>In a risk-based approach, the results of product risk analysis are used to:</p><ul><li>Determine the test techniques to be employed.</li><li>Determine the particular levels and types of testing to be performed (e.g., security testing, accessibility testing).</li><li>Determine the extent of testing to be carried out.</li><li>Prioritize testing in an attempt to find the critical defects as early as possible.</li><li>Determine whether any activities in addition to testing could be employed to reduce risk (e.g., providing training to inexperienced designers).</li></ul><p>Risk-based testing draws on the collective knowledge and insight of the project stakeholders to carry out product risk analysis. To ensure that the likelihood of a product failure is minimized, risk management activities provide a disciplined approach to:</p><ul><li>Analyze (and re-evaluate on a regular basis) what can go wrong (risks).</li><li>Determine which risks are important to deal with.</li><li>Implement actions to mitigate those risks.</li><li>Make contingency plans to deal with the risks should they become actual events.</li></ul><p>In addition, testing may identify new risks, help to determine what risks should be mitigated, and lower uncertainty about risks.</p><h3>5.6 Defect Management</h3><p>Since one of the objectives of testing is to find defects, defects found during testing should be logged.</p><p>The way in which defects are logged may vary, depending on the context of the component or system being tested, the test level, and the software development lifecycle model. Any defects identified should be investigated and should be tracked from discovery and classification to their resolution (e.g., correction of the defects and successful confirmation testing of the solution, deferral to a subsequent release, acceptance as a permanent product limitation, etc.). In order to manage all defects to resolution, an organization should establish a defect management process which includes a workflow and rules for classification. This process must be agreed with all those participating in defect management, including designers, developers, testers, and product owners. In some organizations, defect logging and tracking may be very informal.</p><p>During the defect management process, some of the reports may turn out to describe false positives, not actual failures due to defects. For example, a test may fail when a network connection is broken or times out. This behavior does not result from a defect in the test object, but is an anomaly that needs to be investigated. Testers should attempt to minimize the number of false positives reported as defects.</p><p>Defects may be reported during coding, static analysis, reviews, dynamic testing, or use of a software product. Defects may be reported for issues in code or working systems, or in any type of documentation including requirements, user stories and acceptance criteria, development documents, test documents, user manuals, or installation guides. In order to have an effective and efficient defect management process, organizations may define standards for the attributes, classification, and workflow of defects.</p><p>Typical defect reports have the following objectives:</p><ul><li>Provide developers and other parties with information about any adverse event that occurred, to enable them to identify specific effects, to isolate the problem with a minimal reproducing test, and to correct the potential defect(s), as needed or to otherwise resolve the problem.</li><li>Provide test managers a means of tracking the quality of the work product and the impact on the testing (e.g., if a lot of defects are reported, the testers will have spent a lot of time reporting them instead of running tests, and there will be more confirmation testing needed).</li><li>Provide ideas for development and test process improvement.</li></ul><p>A defect report filed during dynamic testing typically includes:</p><ul><li>An identifier.</li><li>A title and a short summary of the defect being reported.</li><li>Date of the defect report, issuing organization, and author.</li><li>Identification of the test item (configuration item being tested) and environment.</li><li>The development lifecycle phase(s) in which the defect was observed.</li><li>A description of the defect to enable reproduction and resolution, including logs, database dumps, screenshots, or recordings (if found during test execution).</li><li>Expected and actual results.</li><li>Scope or degree of impact (severity) of the defect on the interests of stakeholder(s).</li><li>Urgency/priority to fix.</li><li>State of the defect report (e.g., open, deferred, duplicate, waiting to be fixed, awaiting confirmation testing, re-opened, closed).</li><li>Conclusions, recommendations and approvals.</li><li>Global issues, such as other areas that may be affected by a change resulting from the defect.</li><li>Change history, such as the sequence of actions taken by project team members with respect to the defect to isolate, repair, and confirm it as fixed.</li><li>References, including the test case that revealed the problem.</li></ul><p>Some of these details may be automatically included and/or managed when using defect management tools, e.g., automatic assignment of an identifier, assignment and update of the defect report state during the workflow, etc. Defects found during static testing, particularly reviews, will normally be documented in a different way, e.g., in review meeting notes.</p><p>An example of the contents of a defect report can be found in ISO standard (ISO/IEC/IEEE 29119–3) (which refers to defect reports as incident reports).</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a6b594135f09" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ISTQB Foundation Level Syllabus, Chapter 3 of 6: Static Testing]]></title>
            <link>https://medium.com/@HugoSaxTavares/istqb-foundation-level-syllabus-chapter-3-of-6-static-testing-813868d2460c?source=rss-4bf118ee381a------2</link>
            <guid isPermaLink="false">https://medium.com/p/813868d2460c</guid>
            <category><![CDATA[quality-software]]></category>
            <category><![CDATA[itsqb]]></category>
            <category><![CDATA[static-testing]]></category>
            <category><![CDATA[itsqb-certification]]></category>
            <category><![CDATA[software-testing]]></category>
            <dc:creator><![CDATA[Hugo Bandeira Tavares]]></dc:creator>
            <pubDate>Tue, 03 Dec 2019 00:41:33 GMT</pubDate>
            <atom:updated>2019-12-03T00:41:33.119Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Disclaimer: this article is a copy from the original document available <a href="https://www.istqb.org/downloads/send/2-foundation-level-documents/281-istqb-ctfl-syllabus-2018-v3-1.html">here</a>.<br>All rights belong to International Software Testing Qualifications Board (hereinafter called ISTQB®). ISTQB is a registered trademark of the International Software Testing Qualifications Board.</blockquote><blockquote>This is only here for study purposes of the author.</blockquote><h3>Keywords</h3><p>ad hoc reviewing, checklist-based reviewing, dynamic testing, formal review, informal review, inspection, perspective-based reading, review, role-based reviewing, scenario-based reviewing, static analysis, static testing, technical review, walkthrough</p><h3>3.1 Static Testing Basics</h3><p>In contrast to dynamic testing, which requires the execution of the software being tested, static testing relies on the manual examination of work products (i.e., reviews) or tool-driven evaluation of the code or other work products (i.e., static analysis). Both types of static testing assess the code or other work product being tested without actually executing the code or work product being tested.</p><p>Static analysis is important for safety-critical computer systems (e.g., aviation, medical, or nuclear software), but static analysis has also become important and common in other settings. For example, static analysis is an important part of security testing. Static analysis is also often incorporated into automated build and delivery systems, for example in Agile development, continuous delivery, and continuous deployment.</p><h3>3.1.1 Work Products that Can Be Examined by Static Testing</h3><p>Almost any work product can be examined using static testing (reviews and/or static analysis), for example:</p><ul><li>Specifications, including business requirements, functional requirements, and security requirements.</li><li>Epics, user stories, and acceptance criteria.</li><li>Architecture and design specifications.</li><li>Code.</li><li>Testware, including test plans, test cases, test procedures, and automated test scripts.</li><li>User guides.</li><li>Web pages.</li><li>Contracts, project plans, schedules, and budgets.</li><li>Models, such as activity diagrams, which may be used for Model-Based testing (see ISTQB-MBT Foundation Level Model-Based Tester Extension Syllabus and Kramer 2016).</li></ul><p>Reviews can be applied to any work product that the participants know how to read and understand. Static analysis can be applied efficiently to any work product with a formal structure (typically code or models) for which an appropriate static analysis tool exists. Static analysis can even be applied with tools that evaluate work products written in natural language such as requirements (e.g., checking for spelling, grammar, and readability).</p><h3>3.1.2 Benefits of Static Testing</h3><p>Static testing techniques provide a variety of benefits. When applied early in the software development lifecycle, static testing enables the early detection of defects before dynamic testing is performed (e.g., in requirements or design specifications reviews, product backlog refinement, etc.). Defects found early are often much cheaper to remove than defects found later in the lifecycle, especially compared to defects found after the software is deployed and in active use. Using static testing techniques to find defects and then fixing those defects promptly is almost always much cheaper for the organization than using dynamic testing to find defects in the test object and then fixing them, especially when considering the additional costs associated with updating other work products and performing confirmation and regression testing.</p><p>Additional benefits of static testing may include:</p><ul><li>Detecting and correcting defects more efficiently, and prior to dynamic test execution.</li><li>Identifying defects which are not easily found by dynamic testing.</li><li>Preventing defects in design or coding by uncovering inconsistencies, ambiguities, contradictions, omissions, inaccuracies, and redundancies in requirements.</li><li>Increasing development productivity (e.g., due to improved design, more maintainable code).</li><li>Reducing development cost and time.</li><li>Reducing testing cost and time.</li><li>Reducing total cost of quality over the software’s lifetime, due to fewer failures later in the lifecycle or after delivery into operation.</li><li>Improving communication between team members in the course of participating in reviews.</li></ul><h3>3.1.3 Differences between Static and Dynamic Testing</h3><p>Static testing and dynamic testing can have the same objectives (see section 1.1.1, Typical Objectives of Testing), such as providing an assessment of the quality of the work products and identifying defects as early as possible. Static and dynamic testing complement each other by finding different types of defects.</p><p>One main distinction is that static testing finds defects in work products directly rather than identifying failures caused by defects when the software is run. A defect can reside in a work product for a very long time without causing a failure. The path where the defect lies may be rarely exercised or hard to reach, so it will not be easy to construct and execute a dynamic test that encounters it. Static testing may be able to find the defect with much less effort.</p><p>Another distinction is that static testing can be used to improve the consistency and internal quality of work products, while dynamic testing typically focuses on externally visible behaviors.</p><p>Compared with dynamic testing, typical defects that are easier and cheaper to find and fix through static testing include:</p><ul><li>Requirement defects (e.g., inconsistencies, ambiguities, contradictions, omissions, inaccuracies, and redundancies)</li><li>Design defects (e.g., inefficient algorithms or database structures, high coupling, low cohesion)</li><li>Coding defects (e.g., variables with undefined values, variables that are declared but never used, unreachable code, duplicate code)</li><li>Deviations from standards (e.g., lack of adherence to coding standards)</li><li>Incorrect interface specifications (e.g., different units of measurement used by the calling system than by the called system)</li><li>Security vulnerabilities (e.g., susceptibility to buffer overflows)</li><li>Gaps or inaccuracies in test basis traceability or coverage (e.g., missing tests for an acceptance criterion)</li></ul><p>Moreover, most types of maintainability defects can only be found by static testing (e.g., improper modularization, poor reusability of components, code that is difficult to analyze and modify without introducing new defects).</p><h3>3.2 Review Process</h3><p>Reviews vary from informal to formal. Informal reviews are characterized by not following a defined process and not having formal documented output. Formal reviews are characterized by team participation, documented results of the review, and documented procedures for conducting the review.</p><p>The formality of a review process is related to factors such as the software development lifecycle model, the maturity of the development process, the complexity of the work product to be reviewed, any legal or regulatory requirements, and/or the need for an audit trail.</p><p>The focus of a review depends on the agreed objectives of the review (e.g., finding defects, gaining understanding, educating participants such as testers and new team members, or discussing and deciding by consensus).</p><p>ISO standard (ISO/IEC 20246) contains more in-depth descriptions of the review process for work products, including roles and review techniques.</p><h3>3.2.1 Work Product Review Process</h3><p>The review process comprises the following main activities:</p><p><strong>Planning.</strong></p><ul><li>Defining the scope, which includes the purpose of the review, what documents or parts of documents to review, and the quality characteristics to be evaluated.</li><li>Estimating effort and timeframe.</li><li>Identifying review characteristics such as the review type with roles, activities, and checklists.</li><li>Selecting the people to participate in the review and allocating roles.</li><li>Defining the entry and exit criteria for more formal review types (e.g., inspections).</li><li>Checking that entry criteria are met (for more formal review types).</li></ul><p><strong>Initiate review.</strong></p><ul><li>Distributing the work product (physically or by electronic means) and other material, such as issue log forms, checklists, and related work products.</li><li>Explaining the scope, objectives, process, roles, and work products to the participants.</li><li>Answering any questions that participants may have about the review.</li></ul><p><strong>Individual review (i.e., individual preparation).</strong></p><ul><li>Reviewing all or part of the work product.</li><li>Noting potential defects, recommendations, and questions.</li></ul><p><strong>Issue communication and analysis.</strong></p><ul><li>Communicating identified potential defects (e.g., in a review meeting).</li><li>Analyzing potential defects, assigning ownership and status to them.</li><li>Evaluating and documenting quality characteristics.</li><li>Evaluating the review findings against the exit criteria to make a review decision (reject; major changes needed; accept, possibly with minor changes).</li></ul><p><strong>Fixing and reporting.</strong></p><ul><li>Creating defect reports for those findings that require changes.</li><li>Fixing defects found (typically done by the author) in the work product reviewed.</li><li>Communicating defects to the appropriate person or team (when found in a work product related to the work product reviewed).</li><li>Recording updated status of defects (in formal reviews), potentially including the agreement of the comment originator.</li><li>Gathering metrics (for more formal review types).</li><li>Checking that exit criteria are met (for more formal review types).</li><li>Accepting the work product when the exit criteria are reached.</li></ul><p>The results of a work product review vary, depending on the review type and formality, as described in section 3.2.3, Review Types.</p><h3>3.2.2 Roles and responsibilities in a formal review</h3><p>A typical formal review will include the roles below:</p><p><strong>Author.</strong></p><ul><li>Creates the work product under review.</li><li>Fixes defects in the work product under review (if necessary).</li></ul><p><strong>Management.</strong></p><ul><li>Is responsible for review planning.</li><li>Decides on the execution of reviews.</li><li>Assigns staff, budget, and time.</li><li>Monitors ongoing cost-effectiveness.</li><li>Executes control decisions in the event of inadequate outcomes.</li></ul><p><strong>Facilitator (often called moderator).</strong></p><ul><li>Ensures effective running of review meetings (when held).</li><li>Mediates, if necessary, between the various points of view.</li><li>Is often the person upon whom the success of the review depends.</li></ul><p><strong>Review leader.</strong></p><ul><li>Takes overall responsibility for the review.</li><li>Decides who will be involved and organizes when and where it will take place.</li></ul><p><strong>Reviewers.</strong></p><ul><li>May be subject matter experts, persons working on the project, stakeholders with an interest in the work product, and/or individuals with specific technical or business backgrounds.</li><li>Identify potential defects in the work product under review.</li><li>May represent different perspectives (e.g., tester, programmer, user, operator, business analyst, usability expert, etc.).</li></ul><p><strong>Scribe (or recorder).</strong></p><ul><li>Collates potential defects found during the individual review activity.</li><li>Records new potential defects, open points, and decisions from the review meeting (when held).</li></ul><p>In some review types, one person may play more than one role, and the actions associated with each role may also vary based on review type. In addition, with the advent of tools to support the review process, especially the logging of defects, open points, and decisions, there is often no need for a scribe.</p><p>Further, more detailed roles are possible, as described in ISO standard (ISO/IEC 20246).</p><h3>3.2.3 Review Types</h3><p>Although reviews can be used for various purposes, one of the main objectives is to uncover defects. All review types can aid in defect detection, and the selected review type should be based on the needs of the project, available resources, product type and risks, business domain, and company culture, among other selection criteria.</p><p>Reviews can be classified according to various attributes. The following lists the four most common types of reviews and their associated attributes.</p><p><strong>Informal review (e.g., buddy check, pairing, pair review).</strong></p><ul><li>Main purpose: detecting potential defects.</li><li>Possible additional purposes: generating new ideas or solutions, quickly solving minor problems.</li><li>Not based on a formal (documented) process.</li><li>May not involve a review meeting.</li><li>May be performed by a colleague of the author (buddy check) or by more people.</li><li>Results may be documented.</li><li>Varies in usefulness depending on the reviewers.</li><li>Use of checklists is optional.</li><li>Very commonly used in Agile development.</li></ul><p><strong>Walkthrough.</strong></p><ul><li>Main purposes: find defects, improve the software product, consider alternative implementations, evaluate conformance to standards and specifications.</li><li>Possible additional purposes: exchanging ideas about techniques or style variations, training of participants, achieving consensus.</li><li>Individual preparation before the review meeting is optional.</li><li>Review meeting is typically led by the author of the work product.</li><li>Scribe is mandatory.</li><li>Use of checklists is optional.</li><li>May take the form of scenarios, dry runs, or simulations.</li><li>Potential defect logs and review reports may be produced.</li><li>May vary in practice from quite informal to very formal.</li></ul><p><strong>Technical review.</strong></p><ul><li>Main purposes: gaining consensus, detecting potential defects.</li><li>Possible further purposes: evaluating quality and building confidence in the work product, generating new ideas, motivating and enabling authors to improve future work products, considering alternative implementations.</li><li>Reviewers should be technical peers of the author, and technical experts in the same or other disciplines.</li><li>Individual preparation before the review meeting is required.</li><li>Review meeting is optional, ideally led by a trained facilitator (typically not the author).</li><li>Scribe is mandatory, ideally not the author.</li><li>Use of checklists is optional.</li><li>Potential defect logs and review reports are typically produced.</li></ul><p><strong>Inspection.</strong></p><ul><li>Main purposes: detecting potential defects, evaluating quality and building confidence in the work product, preventing future similar defects through author learning and root cause analysis.</li><li>Possible further purposes: motivating and enabling authors to improve future work products and the software development process, achieving consensus.</li><li>Follows a defined process with formal documented outputs, based on rules and checklists.</li><li>Uses clearly defined roles, such as those specified in section 3.2.2, Roles and responsibilities in a formal review, which are mandatory, and may include a dedicated reader (who reads the work product aloud during the review meeting).</li><li>Individual preparation before the review meeting is required.</li><li>Reviewers are either peers of the author or experts in other disciplines that are relevant to the work product.</li><li>Specified entry and exit criteria are used.</li><li>Scribe is mandatory.</li><li>Review meeting is led by a trained facilitator (not the author).</li><li>Author cannot act as the review leader, reader, or scribe.</li><li>Potential defect logs and review report are produced.</li><li>Metrics are collected and used to improve the entire software development process, including the inspection process.</li></ul><p>A single work product may be the subject of more than one type of review. If more than one type of review is used, the order may vary. For example, an informal review may be carried out before a technical review, to ensure the work product is ready for a technical review.</p><p>The types of reviews described above can be done as peer reviews, i.e., done by colleagues at a similar approximate organizational level.</p><p>The types of defects found in a review vary, depending especially on the work product being reviewed. See section 3.1.3, Differences between Static and Dynamic Testing, for examples of defects that can be found by reviews in different work products, and see Gilb 1993 for information on formal inspections.</p><h3>3.2.4 Applying Review Techniques</h3><p>There are a number of review techniques that can be applied during the individual review (i.e., individual preparation) activity to uncover defects. These techniques can be used across the review types described above. The effectiveness of the techniques may differ depending on the type of review used. Examples of different individual review techniques for various review types are listed below.</p><p><strong>Ad hoc.</strong></p><p>In an ad hoc review, reviewers are provided with little or no guidance on how this task should be performed. Reviewers often read the work product sequentially, identifying and documenting issues as they encounter them. Ad hoc reviewing is a commonly used technique needing little preparation. This technique is highly dependent on reviewer skills and may lead to many duplicate issues being reported by different reviewers.</p><p><strong>Checklist-based.</strong></p><p>A checklist-based review is a systematic technique, whereby the reviewers detect issues based on checklists that are distributed at review initiation (e.g., by the facilitator). A review checklist consists of a set of questions based on potential defects, which may be derived from experience. Checklists should be specific to the type of work product under review and should be maintained regularly to cover issue types missed in previous reviews. The main advantage of the checklist-based technique is a systematic coverage of typical defect types. Care should be taken not to simply follow the checklist in individual reviewing, but also to look for defects outside the checklist.</p><p><strong>Scenarios and dry runs.</strong></p><p>In a scenario-based review, reviewers are provided with structured guidelines on how to read through the work product. A scenario-based approach supports reviewers in performing “dry runs” on the work product based on expected usage of the work product (if the work product is documented in a suitable format such as use cases). These scenarios provide reviewers with better guidelines on how to identify specific defect types than simple checklist entries. As with checklist-based reviews, in order not to miss other defect types (e.g., missing features), reviewers should not be constrained to the documented scenarios.</p><p><strong>Role-based.</strong></p><p>A role-based review is a technique in which the reviewers evaluate the work product from the perspective of individual stakeholder roles. Typical roles include specific end user types (experienced, inexperienced, senior, child, etc.), and specific roles in the organization (user administrator, system administrator, performance tester, etc.).</p><p><strong>Perspective-based.</strong></p><p>In perspective-based reading, similar to a role-based review, reviewers take on different stakeholder viewpoints in individual reviewing. Typical stakeholder viewpoints include end user, marketing, designer, tester, or operations. Using different stakeholder viewpoints leads to more depth in individual reviewing with less duplication of issues across reviewers.</p><p>In addition, perspective-based reading also requires the reviewers to attempt to use the work product under review to generate the product they would derive from it. For example, a tester would attempt to generate draft acceptance tests if performing a perspective-based reading on a requirements specification to see if all the necessary information was included. Further, in perspective-based reading, checklists are expected to be used.</p><p>Empirical studies have shown perspective-based reading to be the most effective general technique for reviewing requirements and technical work products. A key success factor is including and weighing different stakeholder viewpoints appropriately, based on risks. See Shul 2000 for details on perspectivebased reading, and Sauer 2000 for the effectiveness of different review types.</p><h3>3.2.5 Success Factors for Reviews</h3><p>In order to have a successful review, the appropriate type of review and the techniques used must be considered. In addition, there are a number of other factors that will affect the outcome of the review.</p><p>Organizational success factors for reviews include:</p><ul><li>Each review has clear objectives, defined during review planning, and used as measurable exit criteria.</li><li>Review types are applied which are suitable to achieve the objectives and are appropriate to the type and level of software work products and participants.</li><li>Any review techniques used, such as checklist-based or role-based reviewing, are suitable for effective defect identification in the work product to be reviewed.</li><li>Any checklists used address the main risks and are up to date.</li><li>Large documents are written and reviewed in small chunks, so that quality control is exercised by providing authors early and frequent feedback on defects.</li><li>Participants have adequate time to prepare.</li><li>Reviews are scheduled with adequate notice.</li><li>Management supports the review process (e.g., by incorporating adequate time for review activities in project schedules).</li></ul><p>People-related success factors for reviews include:</p><ul><li>The right people are involved to meet the review objectives, for example, people with different skill sets or perspectives, who may use the document as a work input.</li><li>Testers are seen as valued reviewers who contribute to the review and learn about the work product, which enables them to prepare more effective tests, and to prepare those tests earlier.</li><li>Participants dedicate adequate time and attention to detail.</li><li>Reviews are conducted on small chunks, so that reviewers do not lose concentration during individual review and/or the review meeting (when held).</li><li>Defects found are acknowledged, appreciated, and handled objectively.</li><li>The meeting is well-managed, so that participants consider it a valuable use of their time.</li><li>The review is conducted in an atmosphere of trust; the outcome will not be used for the evaluation of the participants.</li><li>Participants avoid body language and behaviors that might indicate boredom, exasperation, or hostility to other participants.</li><li>Adequate training is provided, especially for more formal review types such as inspections.</li><li>A culture of learning and process improvement is promoted.</li></ul><p>See Gilb 1993, Wiegers 2002, and van Veenendaal 2004 for more on successful reviews.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=813868d2460c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ISTQB Foundation Level Syllabus, Chapter 2 of 6: Testing Throughout the Software Development…]]></title>
            <link>https://medium.com/@HugoSaxTavares/istqb-foundation-level-syllabus-chapter-2-of-6-testing-throughout-the-software-development-583abb1b8314?source=rss-4bf118ee381a------2</link>
            <guid isPermaLink="false">https://medium.com/p/583abb1b8314</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[istqb-certification]]></category>
            <category><![CDATA[istqb]]></category>
            <category><![CDATA[quality-software]]></category>
            <dc:creator><![CDATA[Hugo Bandeira Tavares]]></dc:creator>
            <pubDate>Tue, 03 Dec 2019 00:40:30 GMT</pubDate>
            <atom:updated>2019-12-03T00:40:30.364Z</atom:updated>
            <content:encoded><![CDATA[<h3>ISTQB Foundation Level Syllabus, Chapter 2 of 6: Testing Throughout the Software Development Lifecycle</h3><blockquote>Disclaimer: this article is a copy from the original document available <a href="https://www.istqb.org/downloads/send/2-foundation-level-documents/281-istqb-ctfl-syllabus-2018-v3-1.html">here</a>.<br>All rights belong to International Software Testing Qualifications Board (hereinafter called ISTQB®). ISTQB is a registered trademark of the International Software Testing Qualifications Board.</blockquote><blockquote>This is only here for study purposes of the author</blockquote><h3>Keywords</h3><p>acceptance testing, alpha testing, beta testing, commercial off-the-shelf (COTS), component integration testing, component testing, confirmation testing, contractual acceptance testing, functional testing, impact analysis, integration testing, maintenance testing, non-functional testing, operational acceptance testing, regression testing, regulatory acceptance testing, sequential development model, system integration testing, system testing, test basis, test case, test environment, test level, test object, test objective, test type, user acceptance testing, white-box testing</p><h3>2.1 Software Development Lifecycle Models</h3><p>A software development lifecycle model describes the types of activity performed at each stage in a software development project, and how the activities relate to one another logically and chronologically.</p><p>There are a number of different software development lifecycle models, each of which requires different approaches to testing.</p><h3>2.1.1 Software Development and Software Testing</h3><p>It is an important part of a tester’s role to be familiar with the common software development lifecycle models so that appropriate test activities can take place.</p><p>In any software development lifecycle model, there are several characteristics of good testing:</p><ul><li>For every development activity, there is a corresponding test activity.</li><li>Each test level has test objectives specific to that level.</li><li>Test analysis and design for a given test level begin during the corresponding development activity.</li><li>Testers participate in discussions to define and refine requirements and design, and are involved in reviewing work products (e.g., requirements, design, user stories, etc.) as soon as drafts are available.</li></ul><p>No matter which software development lifecycle model is chosen, test activities should start in the early stages of the lifecycle, adhering to the testing principle of early testing.</p><p>This syllabus categorizes common software development lifecycle models as follows:</p><ul><li>Sequential development models.</li><li>Iterative and incremental development models.</li></ul><p>A sequential development model describes the software development process as a linear, sequential flow of activities. This means that any phase in the development process should begin when the previous phase is complete. In theory, there is no overlap of phases, but in practice, it is beneficial to have early feedback from the following phase.</p><p>In the Waterfall model, the development activities (e.g., requirements analysis, design, coding, testing) are completed one after another. In this model, test activities only occur after all other development activities have been completed.</p><p>Unlike the Waterfall model, the V-model integrates the test process throughout the development process, implementing the principle of early testing. Further, the V-model includes test levels associated with each corresponding development phase, which further supports early testing (see section 2.2, Test Levels, for a discussion of test levels). In this model, the execution of tests associated with each test level proceeds sequentially, but in some cases overlapping occurs.</p><p>Sequential development models deliver software that contains the complete set of features, but typically require months or years for delivery to stakeholders and users.</p><p>Incremental development involves establishing requirements, designing, building, and testing a system in pieces, which means that the software’s features grow incrementally. The size of these feature increments vary, with some methods having larger pieces and some smaller pieces. The feature increments can be as small as a single change to a user interface screen or new query option.</p><p>Iterative development occurs when groups of features are specified, designed, built, and tested together in a series of cycles, often of a fixed duration. Iterations may involve changes to features developed in earlier iterations, along with changes in project scope. Each iteration delivers working software which is a growing subset of the overall set of features until the final software is delivered or development is stopped.</p><p>Examples include:</p><ul><li>Rational Unified Process: Each iteration tends to be relatively long (e.g., two to three months), and the feature increments are correspondingly large, such as two or three groups of related features.</li><li>Scrum: Each iteration tends to be relatively short (e.g., hours, days, or a few weeks), and the feature increments are correspondingly small, such as a few enhancements and/or two or three new features.</li><li>Kanban: Implemented with or without fixed-length iterations, which can deliver either a single enhancement or feature upon completion, or can group features together to release at once.</li><li>Spiral (or prototyping): Involves creating experimental increments, some of which may be heavily re-worked or even abandoned in subsequent development work.</li></ul><p>Components or systems developed using these methods often involve overlapping and iterating test levels throughout development. Ideally, each feature is tested at several test levels as it moves towards delivery. In some cases, teams use continuous delivery or continuous deployment, both of which involve significant automation of multiple test levels as part of their delivery pipelines. Many development efforts using these methods also include the concept of self-organizing teams, which can change the way testing work is organized as well as the relationship between testers and developers.</p><p>These methods form a growing system, which may be released to end-users on a feature-by-feature basis, on an iteration-by-iteration basis, or in a more traditional major-release fashion. Regardless of whether the software increments are released to end-users, regression testing is increasingly important as the system grows.</p><p>In contrast to sequential models, iterative and incremental models may deliver usable software in weeks or even days, but may only deliver the complete set of requirements product over a period of months or even years.</p><p>For more information on software testing in the context of Agile development, see ISTQB-AT Foundation Level Agile Tester Extension Syllabus, Black 2017, Crispin 2008, and Gregory 2015.</p><h3>2.1.2 Software Development Lifecycle Models in Context</h3><p>Software development lifecycle models must be selected and adapted to the context of project and product characteristics. An appropriate software development lifecycle model should be selected and adapted based on the project goal, the type of product being developed, business priorities (e.g., time-tomarket), and identified product and project risks. For example, the development and testing of a minor internal administrative system should differ from the development and testing of a safety-critical system such as an automobile’s brake control system. As another example, in some cases organizational and cultural issues may inhibit communication between team members, which can impede iterative development.</p><p>Depending on the context of the project, it may be necessary to combine or reorganize test levels and/or test activities. For example, for the integration of a commercial off-the-shelf (COTS) software product into a larger system, the purchaser may perform interoperability testing at the system integration test level (e.g., integration to the infrastructure and other systems) and at the acceptance test level (functional and non-functional, along with user acceptance testing and operational acceptance testing). See section 2.2, Test Levels, for a discussion of test levels and section 2.3, Test Types, for a discussion of test types.</p><p>In addition, software development lifecycle models themselves may be combined. For example, a V-model may be used for the development and testing of the backend systems and their integrations, while an Agile development model may be used to develop and test the front-end user interface (UI) and functionality. Prototyping may be used early in a project, with an incremental development model adopted once the experimental phase is complete.</p><p>Internet of Things (IoT) systems, which consist of many different objects, such as devices, products, and services, typically apply separate software development lifecycle models for each object. This presents a particular challenge for the development of Internet of Things system versions. Additionally the software development lifecycle of such objects places stronger emphasis on the later phases of the software development lifecycle after they have been introduced to operational use (e.g., operate, update, and decommission phases).</p><h3>2.2 Test Levels</h3><p>Test levels are groups of test activities that are organized and managed together. Each test level is an instance of the test process, consisting of the activities described in section 1.4, Test Process, performed in relation to software at a given level of development, from individual units or components to complete systems or, where applicable, systems of systems. Test levels are related to other activities within the software development lifecycle. The test levels used in this syllabus are:</p><ul><li>Component testing;</li><li>Integration testing;</li><li>System testing;</li><li>Acceptance testing.</li></ul><p>Test levels are characterized by the following attributes:</p><ul><li>Specific objectives;</li><li>Test basis, referenced to derive test cases;</li><li>Test object (i.e., what is being tested);</li><li>Typical defects and failures;</li><li>Specific approaches and responsibilities.</li></ul><p>For every test level, a suitable test environment is required. In acceptance testing, for example, a production-like test environment is ideal, while in component testing the developers typically use their own development environment.</p><h3>2.2.1 Component Testing</h3><p><strong>Objectives of component testing.</strong></p><p>Component testing (also known as unit or module testing) focuses on components that are separately testable. Objectives of component testing include:</p><ul><li>Reducing risk.</li><li>Verifying whether the functional and non-functional behaviors of the component are as designed and specified.</li><li>Building confidence in the component’s quality.</li><li>Finding defects in the component.</li><li>Preventing defects from escaping to higher test levels.</li></ul><p>In some cases, especially in incremental and iterative development models (e.g., Agile) where code changes are ongoing, automated component regression tests play a key role in building confidence that changes have not broken existing components.</p><p>Component testing is often done in isolation from the rest of the system, depending on the software development lifecycle model and the system, which may require mock objects, service virtualization, harnesses, stubs, and drivers. Component testing may cover functionality (e.g., correctness of calculations), non-functional characteristics (e.g., searching for memory leaks), and structural properties (e.g., decision testing).</p><p><strong>Test basis.</strong></p><p>Examples of work products that can be used as a test basis for component testing include:</p><ul><li>Detailed design;</li><li>Code;</li><li>Data model;</li><li>Component specifications.</li></ul><p><strong>Test objects.</strong></p><p>Typical test objects for component testing include:</p><ul><li>Components, units or modules;</li><li>Code and data structures;</li><li>Classes;</li><li>Database modules.</li></ul><p><strong>Typical defects and failures.</strong></p><p>Examples of typical defects and failures for component testing include:</p><ul><li>Incorrect functionality (e.g., not as described in design specifications);</li><li>Data flow problems;</li><li>Incorrect code and logic.</li></ul><p>Defects are typically fixed as soon as they are found, often with no formal defect management. However, when developers do report defects, this provides important information for root cause analysis and process improvement.</p><p><strong>Specific approaches and responsibilities.</strong></p><p>Component testing is usually performed by the developer who wrote the code, but it at least requires access to the code being tested. Developers may alternate component development with finding and fixing defects. Developers will often write and execute tests after having written the code for a component.</p><p>However, in Agile development especially, writing automated component test cases may precede writing application code.</p><p>For example, consider test driven development (TDD). Test driven development is highly iterative and is based on cycles of developing automated test cases, then building and integrating small pieces of code, then executing the component tests, correcting any issues, and re-factoring the code. This process continues until the component has been completely built and all component tests are passing. Test driven development is an example of a test-first approach. While test driven development originated in eXtreme Programming (XP), it has spread to other forms of Agile and also to sequential lifecycles (see ISTQB-AT Foundation Level Agile Tester Extension Syllabus).</p><h3>2.2.2 Integration Testing</h3><p><strong>Objectives of integration testing.</strong></p><p>Integration testing focuses on interactions between components or systems. Objectives of integration testing include:</p><ul><li>Reducing risk.</li><li>Verifying whether the functional and non-functional behaviors of the interfaces are as designed and specified.</li><li>Building confidence in the quality of the interfaces.</li><li>Finding defects (which may be in the interfaces themselves or within the components or systems).</li><li>Preventing defects from escaping to higher test levels.</li></ul><p>As with component testing, in some cases automated integration regression tests provide confidence that changes have not broken existing interfaces, components, or systems.</p><p>There are two different levels of integration testing described in this syllabus, which may be carried out on test objects of varying size as follows:</p><ul><li><strong>Component integration</strong> <strong>testing</strong> focuses on the <strong>interactions and interfaces between integrated components</strong>. Component integration <strong>testing is performed after component testing</strong>, and is generally <strong>automated</strong>. In iterative and incremental development, component integration tests are usually part of the <strong>continuous integration process</strong>.</li><li><strong>System integration</strong> <strong>testing</strong> focuses on the interactions and interfaces between systems, packages, and microservices. System integration testing can also cover interactions with, and interfaces provided by, external organizations (e.g., web services). In this case, the developing organization does not control the external interfaces, which can create various challenges for testing (e.g., ensuring that test-blocking defects in the external organization’s code are resolved, arranging for test environments, etc.). System integration testing may be done after system testing or in parallel with ongoing system test activities (in both sequential development and iterative and incremental development).</li></ul><p><strong>Test basis.</strong></p><p>Examples of work products that can be used as a test basis for integration testing include:</p><ul><li>Software and system design</li><li>Sequence diagrams</li><li>Interface and communication protocol specifications</li><li>Use cases</li><li>Architecture at component or system level</li><li>Workflows</li><li>External interface definitions</li></ul><p><strong>Test objects.</strong></p><p>Typical test objects for integration testing include:</p><ul><li>Subsystems</li><li>Databases</li><li>Infrastructure</li><li>Interfaces</li><li>APIs</li><li>Microservices</li></ul><p><strong>Typical defects and failures.</strong></p><p>Examples of typical defects and failures for component integration testing include:</p><ul><li>Incorrect data, missing data, or incorrect data encoding.</li><li>Incorrect sequencing or timing of interface calls.</li><li>Interface mismatch.</li><li>Failures in communication between components.</li><li>Unhandled or improperly handled communication failures between components.</li><li>Incorrect assumptions about the meaning, units, or boundaries of the data being passed between components.</li></ul><p>Examples of typical defects and failures for system integration testing include:</p><ul><li>Inconsistent message structures between systems.</li><li>Incorrect data, missing data, or incorrect data encoding.</li><li>Interface mismatch.</li><li>Failures in communication between systems.</li><li>Unhandled or improperly handled communication failures between systems.</li><li>Incorrect assumptions about the meaning, units, or boundaries of the data being passed between systems.</li><li>Failure to comply with mandatory security regulations</li></ul><p><strong>Specific approaches and responsibilities.</strong></p><p>Component integration tests and system integration tests should concentrate on the integration itself. For example, if integrating module A with module B, tests should focus on the communication between the modules, not the functionality of the individual modules, as that should have been covered during component testing. If integrating system X with system Y, tests should focus on the communication between the systems, not the functionality of the individual systems, as that should have been covered during system testing. Functional, non-functional, and structural test types are applicable.</p><p>Component integration testing is often the responsibility of developers. System integration testing is generally the responsibility of testers. Ideally, testers performing system integration testing should understand the system architecture, and should have influenced integration planning.</p><p>If integration tests and the integration strategy are planned before components or systems are built, those components or systems can be built in the order required for most efficient testing. Systematic integration strategies may be based on the system architecture (e.g., top-down and bottom-up), functional tasks, transaction processing sequences, or some other aspect of the system or components. In order to simplify defect isolation and detect defects early, integration should normally be incremental (i.e., a small number of additional components or systems at a time) rather than “big bang” (i.e., integrating all components or systems in one single step). A risk analysis of the most complex interfaces can help to focus the integration testing.</p><p>The greater the scope of integration, the more difficult it becomes to isolate defects to a specific component or system, which may lead to increased risk and additional time for troubleshooting. This is one reason that continuous integration, where software is integrated on a component-by-component basis (i.e., functional integration), has become common practice. Such continuous integration often includes automated regression testing, ideally at multiple test levels.</p><h3>2.2.3 System Testing</h3><p><strong>Objectives of system testing.</strong></p><p>System testing focuses on the behavior and capabilities of a whole system or product, often considering the end-to-end tasks the system can perform and the non-functional behaviors it exhibits while performing those tasks. Objectives of system testing include:</p><ul><li>Reducing risk.</li><li>Verifying whether the functional and non-functional behaviors of the system are as designed and specified.</li><li>Validating that the system is complete and will work as expected.</li><li>Building confidence in the quality of the system as a whole.</li><li>Finding defects.</li><li>Preventing defects from escaping to higher test levels or production.</li></ul><p>For certain systems, verifying data quality may be an objective. As with component testing and integration testing, in some cases automated system regression tests provide confidence that changes have not broken existing features or end-to-end capabilities. System testing often produces information that is used by stakeholders to make release decisions. System testing may also satisfy legal or regulatory requirements or standards.</p><p>The test environment should ideally correspond to the final target or production environment.</p><p><strong>Test basis.</strong></p><p>Examples of work products that can be used as a test basis for system testing include:</p><ul><li>System and software requirement specifications (functional and non-functional);</li><li>Risk analysis reports;</li><li>Use cases;</li><li>Epics and user stories;</li><li>Models of system behavior;</li><li>State diagrams;</li><li>System and user manuals.</li></ul><p><strong>Test objects.</strong></p><p>Typical test objects for system testing include:</p><ul><li>Applications;</li><li>Hardware/software systems;</li><li>Operating systems;</li><li>System under test (SUT);</li><li>System configuration and configuration data.</li></ul><p><strong>Typical defects and failures.</strong></p><p>Examples of typical defects and failures for system testing include:</p><ul><li>Incorrect calculations;</li><li>Incorrect or unexpected system functional or non-functional behavior;</li><li>Incorrect control and/or data flows within the system;</li><li>Failure to properly and completely carry out end-to-end functional tasks;</li><li>Failure of the system to work properly in the production environment(s);</li><li>Failure of the system to work as described in system and user manuals.</li></ul><p><strong>Specific approaches and responsibilities.</strong></p><p>System testing should focus on the overall, end-to-end behavior of the system as a whole, both functional and non-functional. System testing should use the most appropriate techniques (see chapter 4, Test Techniques) for the aspect(s) of the system to be tested. For example, a decision table may be created to verify whether functional behavior is as described in business rules.</p><p>Independent testers typically carry out system testing. Defects in specifications (e.g., missing user stories, incorrectly stated business requirements, etc.) can lead to a lack of understanding of, or disagreements about, expected system behavior. Such situations can cause false positives and false negatives, which waste time and reduce defect detection effectiveness, respectively. Early involvement of testers in user story refinement or static testing activities, such as reviews, helps to reduce the incidence of such situations.</p><h3>2.2.4 Acceptance Testing</h3><p><strong>Objectives of acceptance testing.</strong></p><p>Acceptance testing, like system testing, typically focuses on the behavior and capabilities of a whole system or product. Objectives of acceptance testing include:</p><ul><li>Establishing confidence in the quality of the system as a whole.</li><li>Validating that the system is complete and will work as expected.</li><li>Verifying that functional and non-functional behaviors of the system are as specified.</li></ul><p>Acceptance testing may produce information to assess the system’s readiness for deployment and use by the customer (end-user). Defects may be found during acceptance testing, but finding defects is often not an objective, and finding a significant number of defects during acceptance testing may in some cases be considered a major project risk. Acceptance testing may also satisfy legal or regulatory requirements or standards.</p><p>Common forms of acceptance testing include the following:</p><ul><li>User acceptance testing.</li><li>Operational acceptance testing.</li><li>Contractual and regulatory acceptance testing.</li><li>Alpha and beta testing.</li></ul><p>Each is described in the following four subsections.</p><p><strong>User acceptance testing (UAT).</strong></p><p>The acceptance testing of the system by users is typically focused on validating the fitness for use of the system by intended users in a real or simulated operational environment. The main objective is building confidence that the users can use the system to meet their needs, fulfill requirements, and perform business processes with minimum difficulty, cost, and risk.</p><p><strong>Operational acceptance testing (OAT).</strong></p><p>The acceptance testing of the system by operations or systems administration staff is usually performed in a (simulated) production environment. The tests focus on operational aspects, and may include:</p><ul><li>Testing of backup and restore;</li><li>Installing, uninstalling and upgrading;</li><li>Disaster recovery;</li><li>User management;</li><li>Maintenance tasks;</li><li>Data load and migration tasks;</li><li>Checks for security vulnerabilities;</li><li>Performance testing.</li></ul><p>The main objective of operational acceptance testing is building confidence that the operators or system administrators can keep the system working properly for the users in the operational environment, even under exceptional or difficult conditions.</p><p><strong>Contractual and regulatory acceptance testing.</strong></p><p>Contractual acceptance testing is performed against a contract’s acceptance criteria for producing custom-developed software. Acceptance criteria should be defined when the parties agree to the contract. Contractual acceptance testing is often performed by users or by independent testers.</p><p>Regulatory acceptance testing is performed against any regulations that must be adhered to, such as government, legal, or safety regulations. Regulatory acceptance testing is often performed by users or by independent testers, sometimes with the results being witnessed or audited by regulatory agencies.</p><p>The main objective of contractual and regulatory acceptance testing is building confidence that contractual or regulatory compliance has been achieved.</p><p><strong>Alpha and beta testing.</strong></p><p>Alpha and beta testing are typically used by developers of commercial off-the-shelf (COTS) software who want to get feedback from potential or existing users, customers, and/or operators before the software product is put on the market. Alpha testing is performed at the developing organization’s site, not by the development team, but by potential or existing customers, and/or operators or an independent test team.</p><p>Beta testing is performed by potential or existing customers, and/or operators at their own locations. Beta testing may come after alpha testing, or may occur without any preceding alpha testing having occurred.</p><p>One objective of alpha and beta testing is building confidence among potential or existing customers, and/or operators that they can use the system under normal, everyday conditions, and in the operational environment(s) to achieve their objectives with minimum difficulty, cost, and risk. Another objective may be the detection of defects related to the conditions and environment(s) in which the system will be used, especially when those conditions and environment(s) are difficult to replicate by the development team.</p><p><strong>Test basis.</strong></p><p>Examples of work products that can be used as a test basis for any form of acceptance testing include:</p><ul><li>Business processes;</li><li>User or business requirements;</li><li>Regulations, legal contracts and standards;</li><li>Use cases;</li><li>System requirements;</li><li>System or user documentation;</li><li>Installation procedures;</li><li>Risk analysis reports.</li></ul><p>In addition, as a test basis for deriving test cases for operational acceptance testing, one or more of the following work products can be used:</p><ul><li>Backup and restore procedures;</li><li>Disaster recovery procedures;</li><li>Non-functional requirements;</li><li>Operations documentation;</li><li>Deployment and installation instructions;</li><li>Performance targets;</li><li>Database packages;</li><li>Security standards or regulations.</li></ul><p><strong>Typical test objects.</strong></p><p>Typical test objects for any form of acceptance testing include:</p><ul><li>System under test;</li><li>System configuration and configuration data;</li><li>Business processes for a fully integrated system;</li><li>Recovery systems and hot sites (for business continuity and disaster recovery testing);</li><li>Operational and maintenance processes;</li><li>Forms;</li><li>Reports;</li><li>Existing and converted production data.</li></ul><p><strong>Typical defects and failures.</strong></p><p>Examples of typical defects for any form of acceptance testing include:</p><ul><li>System workflows do not meet business or user requirements;</li><li>Business rules are not implemented correctly;</li><li>System does not satisfy contractual or regulatory requirements;</li><li>Non-functional failures such as security vulnerabilities, inadequate performance efficiency under high loads, or improper operation on a supported platform.</li></ul><p><strong>Specific approaches and responsibilities.</strong></p><p>Acceptance testing is often the responsibility of the customers, business users, product owners, or operators of a system, and other stakeholders may be involved as well.</p><p>Acceptance testing is often thought of as the last test level in a sequential development lifecycle, but it may also occur at other times, for example:</p><ul><li>Acceptance testing of a COTS software product may occur when it is installed or integrated.</li><li>Acceptance testing of a new functional enhancement may occur before system testing.</li></ul><p>In iterative development, project teams can employ various forms of acceptance testing during and at the end of each iteration, such as those focused on verifying a new feature against its acceptance criteria and those focused on validating that a new feature satisfies the users’ needs. In addition, alpha tests and beta tests may occur, either at the end of each iteration, after the completion of each iteration, or after a series of iterations. User acceptance tests, operational acceptance tests, regulatory acceptance tests, and contractual acceptance tests also may occur, either at the close of each iteration, after the completion of each iteration, or after a series of iterations.</p><h3>2.3 Test Types</h3><p>A test type is a group of test activities aimed at testing specific characteristics of a software system, or a part of a system, based on specific test objectives. Such objectives may include:</p><ul><li>Evaluating functional quality characteristics, such as completeness, correctness, and appropriateness.</li><li>Evaluating non-functional quality characteristics, such as reliability, performance efficiency, security, compatibility, and usability.</li><li>Evaluating whether the structure or architecture of the component or system is correct, complete, and as specified.</li><li>Evaluating the effects of changes, such as confirming that defects have been fixed (confirmation testing) and looking for unintended changes in behavior resulting from software or environment changes (regression testing).</li></ul><h3>2.3.1 Functional Testing</h3><p>Functional testing of a system involves tests that evaluate functions that the system should perform.</p><p>Functional requirements may be described in work products such as business requirements specifications, epics, user stories, use cases, or functional specifications, or they may be undocumented.</p><p>The functions are “what” the system should do.</p><p>Functional tests should be performed at all test levels (e.g., tests for components may be based on a component specification), though the focus is different at each level (see section 2.2, Test Levels).</p><p>Functional testing considers the behavior of the software, so black-box techniques may be used to derive test conditions and test cases for the functionality of the component or system (see section 4.2, Black-box Test Techniques).</p><p>The thoroughness of functional testing can be measured through functional coverage. Functional coverage is the extent to which some type of functional element has been exercised by tests, and is expressed as a percentage of the type(s) of element being covered. For example, using traceability between tests and functional requirements, the percentage of these requirements which are addressed by testing can be calculated, potentially identifying coverage gaps.</p><p>Functional test design and execution may involve special skills or knowledge, such as knowledge of the particular business problem the software solves (e.g., geological modelling software for the oil and gas industries) or the particular role the software serves (e.g., computer gaming software that provides interactive entertainment).</p><h3>2.3.2 Non-functional Testing</h3><p>Non-functional testing of a system evaluates characteristics of systems and software such as usability, performance efficiency or security. Refer to ISO standard (ISO/IEC 25010) for a classification of software product quality characteristics. Non-functional testing is the testing of “how well” the system behaves.</p><p>Contrary to common misperceptions, non-functional testing can and often should be performed at all test levels, and done as early as possible. The late discovery of non-functional defects can be extremely dangerous to the success of a project.</p><p>Black-box techniques (see section 4.2, Black-box Test Techniques) may be used to derive test conditions and test cases for nonfunctional testing. For example, boundary value analysis can be used to define the stress conditions for performance tests.</p><p>The thoroughness of non-functional testing can be measured through non-functional coverage. Nonfunctional coverage is the extent to which some type of non-functional element has been exercised by tests, and is expressed as a percentage of the type(s) of element being covered. For example, using traceability between tests and supported devices for a mobile application, the percentage of devices which are addressed by compatibility testing can be calculated, potentially identifying coverage gaps.</p><p>Non-functional test design and execution may involve special skills or knowledge, such as knowledge of the inherent weaknesses of a design or technology (e.g., security vulnerabilities associated with particular programming languages) or the particular user base (e.g., the personas of users of healthcare facility management systems).</p><p>Refer to ISTQB-ATA Advanced Level Test Analyst Syllabus, ISTQB-ATTA Advanced Level Technical Test Analyst Syllabus, ISTQB-SEC Advanced Level Security Tester Syllabus, and other ISTQB specialist modules for more details regarding the testing of non-functional quality characteristics.</p><h3>2.3.3 White-box Testing</h3><p>White-box testing derives tests based on the system’s internal structure or implementation. Internal structure may include code, architecture, work flows, and/or data flows within the system (see section 4.3, White-box Test Techniques).</p><p>The thoroughness of white-box testing can be measured through structural coverage. Structural coverage is the extent to which some type of structural element has been exercised by tests, and is expressed as a percentage of the type of element being covered.</p><p>At the component testing level, code coverage is based on the percentage of component code that has been tested, and may be measured in terms of different aspects of code (coverage items) such as the percentage of executable statements tested in the component, or the percentage of decision outcomes tested. These types of coverage are collectively called code coverage. At the component integration testing level, white-box testing may be based on the architecture of the system, such as interfaces between components, and structural coverage may be measured in terms of the percentage of interfaces exercised by tests.</p><p>White-box test design and execution may involve special skills or knowledge, such as the way the code is built (e.g., to use code coverage tools), how data is stored (e.g., to evaluate possible database queries), and how to use coverage tools and to correctly interpret their results.</p><h3>2.3.4 Change-related Testing</h3><p>When changes are made to a system, either to correct a defect or because of new or changing functionality, testing should be done to confirm that the changes have corrected the defect or implemented the functionality correctly, and have not caused any unforeseen adverse consequences.</p><ul><li><strong>Confirmation testing</strong>: <strong>After a defect is fixed</strong>, the software may be tested with all test cases that failed due to the defect, which should be re-executed on the new software version. <strong>The software may also be tested with new tests if</strong>, for instance, <strong>the defect was missing functionality</strong>. At the very least, the steps to reproduce the failure(s) caused by the defect must be re-executed on the new software version. The purpose of a confirmation test is to confirm whether the original defect has been successfully fixed.</li><li><strong>Regression testing</strong>: It is possible that a change made in one part of the code, whether a fix or another type of change, may accidentally affect the behavior of other parts of the code, whether within the same component, in other components of the same system, or even in other systems. Changes may include changes to the environment, such as a new version of an operating system or database management system. Such unintended side-effects are called regressions. Regression testing involves running tests to detect such unintended side-effects.</li></ul><p>Confirmation testing and regression testing are performed at all test levels.</p><p>Especially in iterative and incremental development lifecycles (e.g., Agile), new features, changes to existing features, and code refactoring result in frequent changes to the code, which also requires change-related testing. Due to the evolving nature of the system, confirmation and regression testing are very important. This is particularly relevant for Internet of Things systems where individual objects (e.g., devices) are frequently updated or replaced.</p><p>Regression test suites are run many times and generally evolve slowly, so regression testing is a strong candidate for automation. Automation of these tests should start early in the project (see chapter 6, Tool Support for Testing).</p><h3>2.3.5 Test Types and Test Levels</h3><p>It is possible to perform any of the test types mentioned above at any test level. To illustrate, examples of functional, non-functional, white-box, and change-related tests will be given across all test levels, for a banking application, starting with functional tests:</p><ul><li>For component testing, tests are designed based on how a component should calculate compound interest.</li><li>For component integration testing, tests are designed based on how account information captured at the user interface is passed to the business logic.</li><li>For system testing, tests are designed based on how account holders can apply for a line of credit on their checking accounts.</li><li>For system integration testing, tests are designed based on how the system uses an external microservice to check an account holder’s credit score.</li><li>For acceptance testing, tests are designed based on how the banker handles approving or declining a credit application.</li></ul><p>The following are examples of non-functional tests:</p><ul><li>For component testing, performance tests are designed to evaluate the number of CPU cycles required to perform a complex total interest calculation.</li><li>For component integration testing, security tests are designed for buffer overflow vulnerabilities due to data passed from the user interface to the business logic.</li><li>For system testing, portability tests are designed to check whether the presentation layer works on all supported browsers and mobile devices.</li><li>For system integration testing, reliability tests are designed to evaluate system robustness if the credit score microservice fails to respond.</li><li>For acceptance testing, usability tests are designed to evaluate the accessibility of the banker’s credit processing interface for people with disabilities.</li></ul><p>The following are examples of white-box tests:</p><ul><li>For component testing, tests are designed to achieve complete statement and decision coverage (see section 4.3, White-box Test Techniques) for all components that perform financial calculations.</li><li>For component integration testing, tests are designed to exercise how each screen in the browser interface passes data to the next screen and to the business logic.</li><li>For system testing, tests are designed to cover sequences of web pages that can occur during a credit line application.</li><li>For system integration testing, tests are designed to exercise all possible inquiry types sent to the credit score microservice.</li><li>For acceptance testing, tests are designed to cover all supported financial data file structures and value ranges for bank-to-bank transfers.</li></ul><p>Finally, the following are examples for change-related tests:</p><ul><li>For component testing, automated regression tests are built for each component and included within the continuous integration framework.</li><li>For component integration testing, tests are designed to confirm fixes to interface-related defects as the fixes are checked into the code repository.</li><li>For system testing, all tests for a given workflow are re-executed if any screen on that workflow changes.</li><li>For system integration testing, tests of the application interacting with the credit scoring microservice are re-executed daily as part of continuous deployment of that microservice.</li><li>For acceptance testing, all previously-failed tests are re-executed after a defect found in acceptance testing is fixed.</li></ul><p>While this section provides examples of every test type across every level, it is not necessary, for all software, to have every test type represented across every level. However, it is important to run applicable test types at each level, especially the earliest level where the test type occurs.</p><h3>2.4 Maintenance Testing</h3><p>Once deployed to production environments, software and systems need to be maintained. Changes of various sorts are almost inevitable in delivered software and systems, either to fix defects discovered in operational use, to add new functionality, or to delete or alter already-delivered functionality. Maintenance is also needed to preserve or improve non-functional quality characteristics of the component or system over its lifetime, especially performance efficiency, compatibility, reliability, security, compatibility, and portability.</p><p>When any changes are made as part of maintenance, maintenance testing should be performed, both to evaluate the success with which the changes were made and to check for possible side-effects (e.g., regressions) in parts of the system that remain unchanged (which is usually most of the system).</p><p>Maintenance testing focuses on testing the changes to the system, as well as testing unchanged parts that might have been affected by the changes. Maintenance can involve planned releases and unplanned releases (hot fixes).</p><p>A maintenance release may require maintenance testing at multiple test levels, using various test types, based on its scope. The scope of maintenance testing depends on:</p><ul><li>The degree of risk of the change, for example, the degree to which the changed area of software communicates with other components or systems.</li><li>The size of the existing system.</li><li>The size of the change.</li></ul><h3>2.4.1 Triggers for Maintenance</h3><p>There are several reasons why software maintenance, and thus maintenance testing, takes place, both for planned and unplanned changes.</p><p>We can classify the triggers for maintenance as follows:</p><ul><li>Modification, such as planned enhancements (e.g., release-based), corrective and emergency changes, changes of the operational environment (such as planned operating system or database upgrades), upgrades of COTS software, and patches for defects and vulnerabilities</li><li>Migration, such as from one platform to another, which can require operational tests of the new environment as well as of the changed software, or tests of data conversion when data from another application will be migrated into the system being maintained</li><li>Retirement, such as when an application reaches the end of its life</li></ul><p>When an application or system is retired, this can require testing of data migration or archiving if long data-retention periods are required. Testing restore/retrieve procedures after archiving for long retention periods may also be needed. In addition regression testing may be needed to ensure that any functionality that remains in service still works.</p><p>For Internet of Things systems, maintenance testing may be triggered by the introduction of completely new or modified things, such as hardware devices and software services, into the overall system. The maintenance testing for such systems places particular emphasis on integration testing at different levels (e.g., network level, application level) and on security aspects, in particular those relating to personal data.</p><h3>2.4.2 Impact Analysis for Maintenance</h3><p>Impact analysis evaluates the changes that were made for a maintenance release to identify the intended consequences as well as expected and possible side effects of a change, and to identify the areas in the system that will be affected by the change. Impact analysis can also help to identify the impact of a change on existing tests. The side effects and affected areas in the system need to be tested for regressions, possibly after updating any existing tests affected by the change.</p><p>Impact analysis may be done before a change is made, to help decide if the change should be made, based on the potential consequences in other areas of the system.</p><p>Impact analysis can be difficult if:</p><ul><li>Specifications (e.g., business requirements, user stories, architecture) are out of date or missing.</li><li>Test cases are not documented or are out of date.</li><li>Bi-directional traceability between tests and the test basis has not been maintained.</li><li>Tool support is weak or non-existent.</li><li>The people involved do not have domain and/or system knowledge.</li><li>Insufficient attention has been paid to the software’s maintainability during development.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=583abb1b8314" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ISTQB Foundation Level Syllabus — Part 3 of 6]]></title>
            <link>https://medium.com/@HugoSaxTavares/istqb-foundation-level-syllabus-part-3-of-6-989e013e70f2?source=rss-4bf118ee381a------2</link>
            <guid isPermaLink="false">https://medium.com/p/989e013e70f2</guid>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Hugo Bandeira Tavares]]></dc:creator>
            <pubDate>Thu, 28 Nov 2019 01:01:29 GMT</pubDate>
            <atom:updated>2019-11-28T15:32:42.950Z</atom:updated>
            <content:encoded><![CDATA[<h3>ISTQB Foundation Level Syllabus, Chapter 3 of 6: Static Testing</h3><blockquote>Disclaimer: this article is a copy from the original document available <a href="https://www.istqb.org/downloads/send/2-foundation-level-documents/281-istqb-ctfl-syllabus-2018-v3-1.html">here</a>.<br>All rights belong to International Software Testing Qualifications Board (hereinafter called ISTQB®). ISTQB is a registered trademark of the International Software Testing Qualifications Board.</blockquote><blockquote>This is only here for study purposes of the author.</blockquote><h3>Keywords</h3><p>ad hoc reviewing, checklist-based reviewing, dynamic testing, formal review, informal review, inspection, perspective-based reading, review, role-based reviewing, scenario-based reviewing, static analysis, static testing, technical review, walkthrough</p><h3>3.1 Static Testing Basics</h3><p>In contrast to dynamic testing, which requires the execution of the software being tested, static testing relies on the manual examination of work products (i.e., reviews) or tool-driven evaluation of the code or other work products (i.e., static analysis). Both types of static testing assess the code or other work product being tested without actually executing the code or work product being tested.</p><p>Static analysis is important for safety-critical computer systems (e.g., aviation, medical, or nuclear software), but static analysis has also become important and common in other settings. For example, static analysis is an important part of security testing. Static analysis is also often incorporated into automated build and delivery systems, for example in Agile development, continuous delivery, and continuous deployment.</p><h4><strong>3.1.1 Work Products that Can Be Examined by Static Testing</strong></h4><p>Almost any work product can be examined using static testing (reviews and/or static analysis), for example:</p><ul><li>Specifications, including business requirements, functional requirements, and security requirements.</li><li>Epics, user stories, and acceptance criteria.</li><li>Architecture and design specifications.</li><li>Code.</li><li>Testware, including test plans, test cases, test procedures, and automated test scripts.</li><li>User guides.</li><li>Web pages.</li><li>Contracts, project plans, schedules, and budgets.</li><li>Models, such as activity diagrams, which may be used for Model-Based testing (see ISTQB-MBT Foundation Level Model-Based Tester Extension Syllabus and Kramer 2016).</li></ul><p>Reviews can be applied to any work product that the participants know how to read and understand. Static analysis can be applied efficiently to any work product with a formal structure (typically code or models) for which an appropriate static analysis tool exists. Static analysis can even be applied with tools that evaluate work products written in natural language such as requirements (e.g., checking for spelling, grammar, and readability).</p><h4><strong>3.1.2 Benefits of Static Testing</strong></h4><p>Static testing techniques provide a variety of benefits. When applied early in the software development lifecycle, static testing enables the early detection of defects before dynamic testing is performed (e.g., in requirements or design specifications reviews, product backlog refinement, etc.). Defects found early are often much cheaper to remove than defects found later in the lifecycle, especially compared to defects found after the software is deployed and in active use. Using static testing techniques to find defects and then fixing those defects promptly is almost always much cheaper for the organization than using dynamic testing to find defects in the test object and then fixing them, especially when considering the additional costs associated with updating other work products and performing confirmation and regression testing.</p><p>Additional benefits of static testing may include:</p><ul><li>Detecting and correcting defects more efficiently, and prior to dynamic test execution.</li><li>Identifying defects which are not easily found by dynamic testing.</li><li>Preventing defects in design or coding by uncovering inconsistencies, ambiguities, contradictions, omissions, inaccuracies, and redundancies in requirements.</li><li>Increasing development productivity (e.g., due to improved design, more maintainable code).</li><li>Reducing development cost and time.</li><li>Reducing testing cost and time.</li><li>Reducing total cost of quality over the software’s lifetime, due to fewer failures later in the lifecycle or after delivery into operation.</li><li>Improving communication between team members in the course of participating in reviews.</li></ul><h4><strong>3.1.3 Differences between Static and Dynamic Testing</strong></h4><p>Static testing and dynamic testing can have the same objectives (see section 1.1.1, Typical Objectives of Testing), such as providing an assessment of the quality of the work products and identifying defects as early as possible. Static and dynamic testing complement each other by finding different types of defects.</p><p>One main distinction is that static testing finds defects in work products directly rather than identifying failures caused by defects when the software is run. A defect can reside in a work product for a very long time without causing a failure. The path where the defect lies may be rarely exercised or hard to reach, so it will not be easy to construct and execute a dynamic test that encounters it. Static testing may be able to find the defect with much less effort.</p><p>Another distinction is that static testing can be used to improve the consistency and internal quality of work products, while dynamic testing typically focuses on externally visible behaviors.</p><p>Compared with dynamic testing, typical defects that are easier and cheaper to find and fix through static testing include:</p><ul><li>Requirement defects (e.g., inconsistencies, ambiguities, contradictions, omissions, inaccuracies, and redundancies)</li><li>Design defects (e.g., inefficient algorithms or database structures, high coupling, low cohesion)</li><li>Coding defects (e.g., variables with undefined values, variables that are declared but never used, unreachable code, duplicate code)</li><li>Deviations from standards (e.g., lack of adherence to coding standards)</li><li>Incorrect interface specifications (e.g., different units of measurement used by the calling system than by the called system)</li><li>Security vulnerabilities (e.g., susceptibility to buffer overflows)</li><li>Gaps or inaccuracies in test basis traceability or coverage (e.g., missing tests for an acceptance criterion)</li></ul><p>Moreover, most types of maintainability defects can only be found by static testing (e.g., improper modularization, poor reusability of components, code that is difficult to analyze and modify without introducing new defects).</p><h3>3.2 Review Process</h3><p>Reviews vary from informal to formal. Informal reviews are characterized by not following a defined process and not having formal documented output. Formal reviews are characterized by team participation, documented results of the review, and documented procedures for conducting the review.</p><p>The formality of a review process is related to factors such as the software development lifecycle model, the maturity of the development process, the complexity of the work product to be reviewed, any legal or regulatory requirements, and/or the need for an audit trail.</p><p>The focus of a review depends on the agreed objectives of the review (e.g., finding defects, gaining understanding, educating participants such as testers and new team members, or discussing and deciding by consensus).</p><p>ISO standard (ISO/IEC 20246) contains more in-depth descriptions of the review process for work products, including roles and review techniques.</p><h4><strong>3.2.1 Work Product Review Process</strong></h4><p>The review process comprises the following main activities:</p><p><strong>Planning.</strong></p><ul><li>Defining the scope, which includes the purpose of the review, what documents or parts of documents to review, and the quality characteristics to be evaluated.</li><li>Estimating effort and timeframe.</li><li>Identifying review characteristics such as the review type with roles, activities, and checklists.</li><li>Selecting the people to participate in the review and allocating roles.</li><li>Defining the entry and exit criteria for more formal review types (e.g., inspections).</li><li>Checking that entry criteria are met (for more formal review types).</li></ul><p><strong>Initiate review.</strong></p><ul><li>Distributing the work product (physically or by electronic means) and other material, such as issue log forms, checklists, and related work products.</li><li>Explaining the scope, objectives, process, roles, and work products to the participants.</li><li>Answering any questions that participants may have about the review.</li></ul><p><strong>Individual review (i.e., individual preparation).</strong></p><ul><li>Reviewing all or part of the work product.</li><li>Noting potential defects, recommendations, and questions.</li></ul><p><strong>Issue communication and analysis.</strong></p><ul><li>Communicating identified potential defects (e.g., in a review meeting).</li><li>Analyzing potential defects, assigning ownership and status to them.</li><li>Evaluating and documenting quality characteristics.</li><li>Evaluating the review findings against the exit criteria to make a review decision (reject; major changes needed; accept, possibly with minor changes).</li></ul><p><strong>Fixing and reporting.</strong></p><ul><li>Creating defect reports for those findings that require changes.</li><li>Fixing defects found (typically done by the author) in the work product reviewed.</li><li>Communicating defects to the appropriate person or team (when found in a work product related to the work product reviewed).</li><li>Recording updated status of defects (in formal reviews), potentially including the agreement of the comment originator.</li><li>Gathering metrics (for more formal review types).</li><li>Checking that exit criteria are met (for more formal review types).</li><li>Accepting the work product when the exit criteria are reached.</li></ul><p>The results of a work product review vary, depending on the review type and formality, as described in section 3.2.3, Review Types.</p><h4><strong>3.2.2 Roles and responsibilities in a formal review</strong></h4><p>A typical formal review will include the roles below:</p><p><strong>Author.</strong></p><ul><li>Creates the work product under review.</li><li>Fixes defects in the work product under review (if necessary).</li></ul><p><strong>Management.</strong></p><ul><li>Is responsible for review planning.</li><li>Decides on the execution of reviews.</li><li>Assigns staff, budget, and time.</li><li>Monitors ongoing cost-effectiveness.</li><li>Executes control decisions in the event of inadequate outcomes.</li></ul><p><strong>Facilitator (often called moderator).</strong></p><ul><li>Ensures effective running of review meetings (when held).</li><li>Mediates, if necessary, between the various points of view.</li><li>Is often the person upon whom the success of the review depends.</li></ul><p><strong>Review leader.</strong></p><ul><li>Takes overall responsibility for the review.</li><li>Decides who will be involved and organizes when and where it will take place.</li></ul><p><strong>Reviewers.</strong></p><ul><li>May be subject matter experts, persons working on the project, stakeholders with an interest in the work product, and/or individuals with specific technical or business backgrounds.</li><li>Identify potential defects in the work product under review.</li><li>May represent different perspectives (e.g., tester, programmer, user, operator, business analyst, usability expert, etc.).</li></ul><p><strong>Scribe (or recorder).</strong></p><ul><li>Collates potential defects found during the individual review activity.</li><li>Records new potential defects, open points, and decisions from the review meeting (when held).</li></ul><p>In some review types, one person may play more than one role, and the actions associated with each role may also vary based on review type. In addition, with the advent of tools to support the review process, especially the logging of defects, open points, and decisions, there is often no need for a scribe.</p><p>Further, more detailed roles are possible, as described in ISO standard (ISO/IEC 20246).</p><h4><strong>3.2.3 Review Types</strong></h4><p>Although reviews can be used for various purposes, one of the main objectives is to uncover defects. All review types can aid in defect detection, and the selected review type should be based on the needs of the project, available resources, product type and risks, business domain, and company culture, among other selection criteria.</p><p>Reviews can be classified according to various attributes. The following lists the four most common types of reviews and their associated attributes.</p><p><strong>Informal review (e.g., buddy check, pairing, pair review).</strong></p><ul><li>Main purpose: detecting potential defects.</li><li>Possible additional purposes: generating new ideas or solutions, quickly solving minor problems.</li><li>Not based on a formal (documented) process.</li><li>May not involve a review meeting.</li><li>May be performed by a colleague of the author (buddy check) or by more people.</li><li>Results may be documented.</li><li>Varies in usefulness depending on the reviewers.</li><li>Use of checklists is optional.</li><li>Very commonly used in Agile development.</li></ul><p><strong>Walkthrough.</strong></p><ul><li>Main purposes: find defects, improve the software product, consider alternative implementations, evaluate conformance to standards and specifications.</li><li>Possible additional purposes: exchanging ideas about techniques or style variations, training of participants, achieving consensus.</li><li>Individual preparation before the review meeting is optional.</li><li>Review meeting is typically led by the author of the work product.</li><li>Scribe is mandatory.</li><li>Use of checklists is optional.</li><li>May take the form of scenarios, dry runs, or simulations.</li><li>Potential defect logs and review reports may be produced.</li><li>May vary in practice from quite informal to very formal.</li></ul><p><strong>Technical review.</strong></p><ul><li>Main purposes: gaining consensus, detecting potential defects.</li><li>Possible further purposes: evaluating quality and building confidence in the work product, generating new ideas, motivating and enabling authors to improve future work products, considering alternative implementations.</li><li>Reviewers should be technical peers of the author, and technical experts in the same or other disciplines.</li><li>Individual preparation before the review meeting is required.</li><li>Review meeting is optional, ideally led by a trained facilitator (typically not the author).</li><li>Scribe is mandatory, ideally not the author.</li><li>Use of checklists is optional.</li><li>Potential defect logs and review reports are typically produced.</li></ul><p><strong>Inspection.</strong></p><ul><li>Main purposes: detecting potential defects, evaluating quality and building confidence in the work product, preventing future similar defects through author learning and root cause analysis.</li><li>Possible further purposes: motivating and enabling authors to improve future work products and the software development process, achieving consensus.</li><li>Follows a defined process with formal documented outputs, based on rules and checklists.</li><li>Uses clearly defined roles, such as those specified in section 3.2.2, Roles and responsibilities in a formal review, which are mandatory, and may include a dedicated reader (who reads the work product aloud during the review meeting).</li><li>Individual preparation before the review meeting is required.</li><li>Reviewers are either peers of the author or experts in other disciplines that are relevant to the work product.</li><li>Specified entry and exit criteria are used.</li><li>Scribe is mandatory.</li><li>Review meeting is led by a trained facilitator (not the author).</li><li>Author cannot act as the review leader, reader, or scribe.</li><li>Potential defect logs and review report are produced.</li><li>Metrics are collected and used to improve the entire software development process, including the inspection process.</li></ul><p>A single work product may be the subject of more than one type of review. If more than one type of review is used, the order may vary. For example, an informal review may be carried out before a technical review, to ensure the work product is ready for a technical review.</p><p>The types of reviews described above can be done as peer reviews, i.e., done by colleagues at a similar approximate organizational level.</p><p>The types of defects found in a review vary, depending especially on the work product being reviewed. See section 3.1.3, Differences between Static and Dynamic Testing, for examples of defects that can be found by reviews in different work products, and see Gilb 1993 for information on formal inspections.</p><h4><strong>3.2.4 Applying Review Techniques</strong></h4><p>There are a number of review techniques that can be applied during the individual review (i.e., individual preparation) activity to uncover defects. These techniques can be used across the review types described above. The effectiveness of the techniques may differ depending on the type of review used. Examples of different individual review techniques for various review types are listed below.</p><p><strong>Ad hoc.</strong></p><p>In an ad hoc review, reviewers are provided with little or no guidance on how this task should be performed. Reviewers often read the work product sequentially, identifying and documenting issues as they encounter them. Ad hoc reviewing is a commonly used technique needing little preparation. This technique is highly dependent on reviewer skills and may lead to many duplicate issues being reported by different reviewers.</p><p><strong>Checklist-based.</strong></p><p>A checklist-based review is a systematic technique, whereby the reviewers detect issues based on checklists that are distributed at review initiation (e.g., by the facilitator). A review checklist consists of a set of questions based on potential defects, which may be derived from experience. Checklists should be specific to the type of work product under review and should be maintained regularly to cover issue types missed in previous reviews. The main advantage of the checklist-based technique is a systematic coverage of typical defect types. Care should be taken not to simply follow the checklist in individual reviewing, but also to look for defects outside the checklist.</p><p><strong>Scenarios and dry runs.</strong></p><p>In a scenario-based review, reviewers are provided with structured guidelines on how to read through the work product. A scenario-based approach supports reviewers in performing “dry runs” on the work product based on expected usage of the work product (if the work product is documented in a suitable format such as use cases). These scenarios provide reviewers with better guidelines on how to identify specific defect types than simple checklist entries. As with checklist-based reviews, in order not to miss other defect types (e.g., missing features), reviewers should not be constrained to the documented scenarios.</p><p><strong>Role-based.</strong></p><p>A role-based review is a technique in which the reviewers evaluate the work product from the perspective of individual stakeholder roles. Typical roles include specific end user types (experienced, inexperienced, senior, child, etc.), and specific roles in the organization (user administrator, system administrator, performance tester, etc.).</p><p><strong>Perspective-based.</strong></p><p>In perspective-based reading, similar to a role-based review, reviewers take on different stakeholder viewpoints in individual reviewing. Typical stakeholder viewpoints include end user, marketing, designer, tester, or operations. Using different stakeholder viewpoints leads to more depth in individual reviewing with less duplication of issues across reviewers.</p><p>In addition, perspective-based reading also requires the reviewers to attempt to use the work product under review to generate the product they would derive from it. For example, a tester would attempt to generate draft acceptance tests if performing a perspective-based reading on a requirements specification to see if all the necessary information was included. Further, in perspective-based reading, checklists are expected to be used.</p><p>Empirical studies have shown perspective-based reading to be the most effective general technique for reviewing requirements and technical work products. A key success factor is including and weighing different stakeholder viewpoints appropriately, based on risks. See Shul 2000 for details on perspectivebased reading, and Sauer 2000 for the effectiveness of different review types.</p><h4><strong>3.2.5 Success Factors for Reviews</strong></h4><p>In order to have a successful review, the appropriate type of review and the techniques used must be considered. In addition, there are a number of other factors that will affect the outcome of the review.</p><p>Organizational success factors for reviews include:</p><ul><li>Each review has clear objectives, defined during review planning, and used as measurable exit criteria.</li><li>Review types are applied which are suitable to achieve the objectives and are appropriate to the type and level of software work products and participants.</li><li>Any review techniques used, such as checklist-based or role-based reviewing, are suitable for effective defect identification in the work product to be reviewed.</li><li>Any checklists used address the main risks and are up to date.</li><li>Large documents are written and reviewed in small chunks, so that quality control is exercised by providing authors early and frequent feedback on defects.</li><li>Participants have adequate time to prepare.</li><li>Reviews are scheduled with adequate notice.</li><li>Management supports the review process (e.g., by incorporating adequate time for review activities in project schedules).</li></ul><p>People-related success factors for reviews include:</p><ul><li>The right people are involved to meet the review objectives, for example, people with different skill sets or perspectives, who may use the document as a work input.</li><li>Testers are seen as valued reviewers who contribute to the review and learn about the work product, which enables them to prepare more effective tests, and to prepare those tests earlier.</li><li>Participants dedicate adequate time and attention to detail.</li><li>Reviews are conducted on small chunks, so that reviewers do not lose concentration during individual review and/or the review meeting (when held).</li><li>Defects found are acknowledged, appreciated, and handled objectively.</li><li>The meeting is well-managed, so that participants consider it a valuable use of their time.</li><li>The review is conducted in an atmosphere of trust; the outcome will not be used for the evaluation of the participants.</li><li>Participants avoid body language and behaviors that might indicate boredom, exasperation, or hostility to other participants.</li><li>Adequate training is provided, especially for more formal review types such as inspections.</li><li>A culture of learning and process improvement is promoted.</li></ul><p>See Gilb 1993, Wiegers 2002, and van Veenendaal 2004 for more on successful reviews.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=989e013e70f2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ISTQB Foundation Level Syllabus — Part 2 of 6]]></title>
            <link>https://medium.com/@HugoSaxTavares/istqb-foundation-level-syllabus-part-2-of-6-e85155a27ccf?source=rss-4bf118ee381a------2</link>
            <guid isPermaLink="false">https://medium.com/p/e85155a27ccf</guid>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Hugo Bandeira Tavares]]></dc:creator>
            <pubDate>Thu, 28 Nov 2019 00:22:31 GMT</pubDate>
            <atom:updated>2019-11-28T15:34:59.689Z</atom:updated>
            <content:encoded><![CDATA[<h3>ISTQB Foundation Level Syllabus, Chapter 2 of 6: Testing Throughout the Software Development Lifecycle</h3><blockquote>Disclaimer: this article is a copy from the original document available <a href="https://www.istqb.org/downloads/send/2-foundation-level-documents/281-istqb-ctfl-syllabus-2018-v3-1.html">here</a>.<br>All rights belong to International Software Testing Qualifications Board (hereinafter called ISTQB®). ISTQB is a registered trademark of the International Software Testing Qualifications Board.</blockquote><blockquote>This is only here for study purposes of the author.</blockquote><h3>Keywords</h3><p>acceptance testing, alpha testing, beta testing, commercial off-the-shelf (COTS), component integration testing, component testing, confirmation testing, contractual acceptance testing, functional testing, impact analysis, integration testing, maintenance testing, non-functional testing, operational acceptance testing, regression testing, regulatory acceptance testing, sequential development model, system integration testing, system testing, test basis, test case, test environment, test level, test object, test objective, test type, user acceptance testing, white-box testing</p><h3>2.1 Software Development Lifecycle Models</h3><p>A software development lifecycle model describes the types of activity performed at each stage in a software development project, and how the activities relate to one another logically and chronologically.</p><p>There are a number of different software development lifecycle models, each of which requires different approaches to testing.</p><h4><strong>2.1.1 Software Development and Software Testing</strong></h4><p>It is an important part of a tester’s role to be familiar with the common software development lifecycle models so that appropriate test activities can take place.</p><p>In any software development lifecycle model, there are several characteristics of good testing:</p><ul><li>For every development activity, there is a corresponding test activity.</li><li>Each test level has test objectives specific to that level.</li><li>Test analysis and design for a given test level begin during the corresponding development activity.</li><li>Testers participate in discussions to define and refine requirements and design, and are involved in reviewing work products (e.g., requirements, design, user stories, etc.) as soon as drafts are available.</li></ul><p>No matter which software development lifecycle model is chosen, test activities should start in the early stages of the lifecycle, adhering to the testing principle of early testing.</p><p>This syllabus categorizes common software development lifecycle models as follows:</p><ul><li>Sequential development models.</li><li>Iterative and incremental development models.</li></ul><p>A sequential development model describes the software development process as a linear, sequential flow of activities. This means that any phase in the development process should begin when the previous phase is complete. In theory, there is no overlap of phases, but in practice, it is beneficial to have early feedback from the following phase.</p><p>In the Waterfall model, the development activities (e.g., requirements analysis, design, coding, testing) are completed one after another. In this model, test activities only occur after all other development activities have been completed.</p><p>Unlike the Waterfall model, the V-model integrates the test process throughout the development process, implementing the principle of early testing. Further, the V-model includes test levels associated with each corresponding development phase, which further supports early testing (see section 2.2, Test Levels, for a discussion of test levels). In this model, the execution of tests associated with each test level proceeds sequentially, but in some cases overlapping occurs.</p><p>Sequential development models deliver software that contains the complete set of features, but typically require months or years for delivery to stakeholders and users.</p><p>Incremental development involves establishing requirements, designing, building, and testing a system in pieces, which means that the software’s features grow incrementally. The size of these feature increments vary, with some methods having larger pieces and some smaller pieces. The feature increments can be as small as a single change to a user interface screen or new query option.</p><p>Iterative development occurs when groups of features are specified, designed, built, and tested together in a series of cycles, often of a fixed duration. Iterations may involve changes to features developed in earlier iterations, along with changes in project scope. Each iteration delivers working software which is a growing subset of the overall set of features until the final software is delivered or development is stopped.</p><p>Examples include:</p><ul><li>Rational Unified Process: Each iteration tends to be relatively long (e.g., two to three months), and the feature increments are correspondingly large, such as two or three groups of related features.</li><li>Scrum: Each iteration tends to be relatively short (e.g., hours, days, or a few weeks), and the feature increments are correspondingly small, such as a few enhancements and/or two or three new features.</li><li>Kanban: Implemented with or without fixed-length iterations, which can deliver either a single enhancement or feature upon completion, or can group features together to release at once.</li><li>Spiral (or prototyping): Involves creating experimental increments, some of which may be heavily re-worked or even abandoned in subsequent development work.</li></ul><p>Components or systems developed using these methods often involve overlapping and iterating test levels throughout development. Ideally, each feature is tested at several test levels as it moves towards delivery. In some cases, teams use continuous delivery or continuous deployment, both of which involve significant automation of multiple test levels as part of their delivery pipelines. Many development efforts using these methods also include the concept of self-organizing teams, which can change the way testing work is organized as well as the relationship between testers and developers.</p><p>These methods form a growing system, which may be released to end-users on a feature-by-feature basis, on an iteration-by-iteration basis, or in a more traditional major-release fashion. Regardless of whether the software increments are released to end-users, regression testing is increasingly important as the system grows.</p><p>In contrast to sequential models, iterative and incremental models may deliver usable software in weeks or even days, but may only deliver the complete set of requirements product over a period of months or even years.</p><p>For more information on software testing in the context of Agile development, see ISTQB-AT Foundation Level Agile Tester Extension Syllabus, Black 2017, Crispin 2008, and Gregory 2015.</p><h4><strong>2.1.2 Software Development Lifecycle Models in Context</strong></h4><p>Software development lifecycle models must be selected and adapted to the context of project and product characteristics. An appropriate software development lifecycle model should be selected and adapted based on the project goal, the type of product being developed, business priorities (e.g., time-tomarket), and identified product and project risks. For example, the development and testing of a minor internal administrative system should differ from the development and testing of a safety-critical system such as an automobile’s brake control system. As another example, in some cases organizational and cultural issues may inhibit communication between team members, which can impede iterative development.</p><p>Depending on the context of the project, it may be necessary to combine or reorganize test levels and/or test activities. For example, for the integration of a commercial off-the-shelf (COTS) software product into a larger system, the purchaser may perform interoperability testing at the system integration test level (e.g., integration to the infrastructure and other systems) and at the acceptance test level (functional and non-functional, along with user acceptance testing and operational acceptance testing). See section 2.2, Test Levels, for a discussion of test levels and section 2.3, Test Types, for a discussion of test types.</p><p>In addition, software development lifecycle models themselves may be combined. For example, a V-model may be used for the development and testing of the backend systems and their integrations, while an Agile development model may be used to develop and test the front-end user interface (UI) and functionality. Prototyping may be used early in a project, with an incremental development model adopted once the experimental phase is complete.</p><p>Internet of Things (IoT) systems, which consist of many different objects, such as devices, products, and services, typically apply separate software development lifecycle models for each object. This presents a particular challenge for the development of Internet of Things system versions. Additionally the software development lifecycle of such objects places stronger emphasis on the later phases of the software development lifecycle after they have been introduced to operational use (e.g., operate, update, and decommission phases).</p><h3>2.2 Test Levels</h3><p>Test levels are groups of test activities that are organized and managed together. Each test level is an instance of the test process, consisting of the activities described in section 1.4, Test Process, performed in relation to software at a given level of development, from individual units or components to complete systems or, where applicable, systems of systems. Test levels are related to other activities within the software development lifecycle. The test levels used in this syllabus are:</p><ul><li>Component testing;</li><li>Integration testing;</li><li>System testing;</li><li>Acceptance testing.</li></ul><p>Test levels are characterized by the following attributes:</p><ul><li>Specific objectives;</li><li>Test basis, referenced to derive test cases;</li><li>Test object (i.e., what is being tested);</li><li>Typical defects and failures;</li><li>Specific approaches and responsibilities.</li></ul><p>For every test level, a suitable test environment is required. In acceptance testing, for example, a production-like test environment is ideal, while in component testing the developers typically use their own development environment.</p><h4><strong>2.2.1 Component Testing</strong></h4><p><strong>Objectives of component testing.</strong></p><p>Component testing (also known as unit or module testing) focuses on components that are separately testable. Objectives of component testing include:</p><ul><li>Reducing risk.</li><li>Verifying whether the functional and non-functional behaviors of the component are as designed and specified.</li><li>Building confidence in the component’s quality.</li><li>Finding defects in the component.</li><li>Preventing defects from escaping to higher test levels.</li></ul><p>In some cases, especially in incremental and iterative development models (e.g., Agile) where code changes are ongoing, automated component regression tests play a key role in building confidence that changes have not broken existing components.</p><p>Component testing is often done in isolation from the rest of the system, depending on the software development lifecycle model and the system, which may require mock objects, service virtualization, harnesses, stubs, and drivers. Component testing may cover functionality (e.g., correctness of calculations), non-functional characteristics (e.g., searching for memory leaks), and structural properties (e.g., decision testing).</p><p><strong>Test basis.</strong></p><p>Examples of work products that can be used as a test basis for component testing include:</p><ul><li>Detailed design;</li><li>Code;</li><li>Data model;</li><li>Component specifications.</li></ul><p><strong>Test objects.</strong></p><p>Typical test objects for component testing include:</p><ul><li>Components, units or modules;</li><li>Code and data structures;</li><li>Classes;</li><li>Database modules.</li></ul><p><strong>Typical defects and failures.</strong></p><p>Examples of typical defects and failures for component testing include:</p><ul><li>Incorrect functionality (e.g., not as described in design specifications);</li><li>Data flow problems;</li><li>Incorrect code and logic.</li></ul><p>Defects are typically fixed as soon as they are found, often with no formal defect management. However, when developers do report defects, this provides important information for root cause analysis and process improvement.</p><p><strong>Specific approaches and responsibilities.</strong></p><p>Component testing is usually performed by the developer who wrote the code, but it at least requires access to the code being tested. Developers may alternate component development with finding and fixing defects. Developers will often write and execute tests after having written the code for a component.</p><p>However, in Agile development especially, writing automated component test cases may precede writing application code.</p><p>For example, consider test driven development (TDD). Test driven development is highly iterative and is based on cycles of developing automated test cases, then building and integrating small pieces of code, then executing the component tests, correcting any issues, and re-factoring the code. This process continues until the component has been completely built and all component tests are passing. Test driven development is an example of a test-first approach. While test driven development originated in eXtreme Programming (XP), it has spread to other forms of Agile and also to sequential lifecycles (see ISTQB-AT Foundation Level Agile Tester Extension Syllabus).</p><h4><strong>2.2.2 Integration Testing</strong></h4><p><strong>Objectives of integration testing.</strong></p><p>Integration testing focuses on interactions between components or systems. Objectives of integration testing include:</p><ul><li>Reducing risk.</li><li>Verifying whether the functional and non-functional behaviors of the interfaces are as designed and specified.</li><li>Building confidence in the quality of the interfaces.</li><li>Finding defects (which may be in the interfaces themselves or within the components or systems).</li><li>Preventing defects from escaping to higher test levels.</li></ul><p>As with component testing, in some cases automated integration regression tests provide confidence that changes have not broken existing interfaces, components, or systems.</p><p>There are two different levels of integration testing described in this syllabus, which may be carried out on test objects of varying size as follows:</p><ul><li>Component integration testing focuses on the interactions and interfaces between integrated components. Component integration testing is performed after component testing, and is generally automated. In iterative and incremental development, component integration tests are usually part of the continuous integration process.</li><li>System integration testing focuses on the interactions and interfaces between systems, packages, and microservices. System integration testing can also cover interactions with, and interfaces provided by, external organizations (e.g., web services). In this case, the developing organization does not control the external interfaces, which can create various challenges for testing (e.g., ensuring that test-blocking defects in the external organization’s code are resolved, arranging for test environments, etc.). System integration testing may be done after system testing or in parallel with ongoing system test activities (in both sequential development and iterative and incremental development).</li></ul><p><strong>Test basis.</strong></p><p>Examples of work products that can be used as a test basis for integration testing include:</p><ul><li>Software and system design</li><li>Sequence diagrams</li><li>Interface and communication protocol specifications</li><li>Use cases</li><li>Architecture at component or system level</li><li>Workflows</li><li>External interface definitions</li></ul><p><strong>Test objects.</strong></p><p>Typical test objects for integration testing include:</p><ul><li>Subsystems</li><li>Databases</li><li>Infrastructure</li><li>Interfaces</li><li>APIs</li><li>Microservices</li></ul><p><strong>Typical defects and failures.</strong></p><p>Examples of typical defects and failures for component integration testing include:</p><ul><li>Incorrect data, missing data, or incorrect data encoding.</li><li>Incorrect sequencing or timing of interface calls.</li><li>Interface mismatch.</li><li>Failures in communication between components.</li><li>Unhandled or improperly handled communication failures between components.</li><li>Incorrect assumptions about the meaning, units, or boundaries of the data being passed between components.</li></ul><p>Examples of typical defects and failures for system integration testing include:</p><ul><li>Inconsistent message structures between systems.</li><li>Incorrect data, missing data, or incorrect data encoding.</li><li>Interface mismatch.</li><li>Failures in communication between systems.</li><li>Unhandled or improperly handled communication failures between systems.</li><li>Incorrect assumptions about the meaning, units, or boundaries of the data being passed between systems.</li><li>Failure to comply with mandatory security regulations</li></ul><p><strong>Specific approaches and responsibilities.</strong></p><p>Component integration tests and system integration tests should concentrate on the integration itself. For example, if integrating module A with module B, tests should focus on the communication between the modules, not the functionality of the individual modules, as that should have been covered during component testing. If integrating system X with system Y, tests should focus on the communication between the systems, not the functionality of the individual systems, as that should have been covered during system testing. Functional, non-functional, and structural test types are applicable.</p><p>Component integration testing is often the responsibility of developers. System integration testing is generally the responsibility of testers. Ideally, testers performing system integration testing should understand the system architecture, and should have influenced integration planning.</p><p>If integration tests and the integration strategy are planned before components or systems are built, those components or systems can be built in the order required for most efficient testing. Systematic integration strategies may be based on the system architecture (e.g., top-down and bottom-up), functional tasks, transaction processing sequences, or some other aspect of the system or components. In order to simplify defect isolation and detect defects early, integration should normally be incremental (i.e., a small number of additional components or systems at a time) rather than “big bang” (i.e., integrating all components or systems in one single step). A risk analysis of the most complex interfaces can help to focus the integration testing.</p><p>The greater the scope of integration, the more difficult it becomes to isolate defects to a specific component or system, which may lead to increased risk and additional time for troubleshooting. This is one reason that continuous integration, where software is integrated on a component-by-component basis (i.e., functional integration), has become common practice. Such continuous integration often includes automated regression testing, ideally at multiple test levels.</p><h4><strong>2.2.3 System Testing</strong></h4><p><strong>Objectives of system testing.</strong></p><p>System testing focuses on the behavior and capabilities of a whole system or product, often considering the end-to-end tasks the system can perform and the non-functional behaviors it exhibits while performing those tasks. Objectives of system testing include:</p><ul><li>Reducing risk.</li><li>Verifying whether the functional and non-functional behaviors of the system are as designed and specified.</li><li>Validating that the system is complete and will work as expected.</li><li>Building confidence in the quality of the system as a whole.</li><li>Finding defects.</li><li>Preventing defects from escaping to higher test levels or production.</li></ul><p>For certain systems, verifying data quality may be an objective. As with component testing and integration testing, in some cases automated system regression tests provide confidence that changes have not broken existing features or end-to-end capabilities. System testing often produces information that is used by stakeholders to make release decisions. System testing may also satisfy legal or regulatory requirements or standards.</p><p>The test environment should ideally correspond to the final target or production environment.</p><p><strong>Test basis.</strong></p><p>Examples of work products that can be used as a test basis for system testing include:</p><ul><li>System and software requirement specifications (functional and non-functional);</li><li>Risk analysis reports;</li><li>Use cases;</li><li>Epics and user stories;</li><li>Models of system behavior;</li><li>State diagrams;</li><li>System and user manuals.</li></ul><p><strong>Test objects.</strong></p><p>Typical test objects for system testing include:</p><ul><li>Applications;</li><li>Hardware/software systems;</li><li>Operating systems;</li><li>System under test (SUT);</li><li>System configuration and configuration data.</li></ul><p><strong>Typical defects and failures.</strong></p><p>Examples of typical defects and failures for system testing include:</p><ul><li>Incorrect calculations;</li><li>Incorrect or unexpected system functional or non-functional behavior;</li><li>Incorrect control and/or data flows within the system;</li><li>Failure to properly and completely carry out end-to-end functional tasks;</li><li>Failure of the system to work properly in the production environment(s);</li><li>Failure of the system to work as described in system and user manuals.</li></ul><p><strong>Specific approaches and responsibilities.</strong></p><p>System testing should focus on the overall, end-to-end behavior of the system as a whole, both functional and non-functional. System testing should use the most appropriate techniques (see chapter 4, Test Techniques) for the aspect(s) of the system to be tested. For example, a decision table may be created to verify whether functional behavior is as described in business rules.</p><p>Independent testers typically carry out system testing. Defects in specifications (e.g., missing user stories, incorrectly stated business requirements, etc.) can lead to a lack of understanding of, or disagreements about, expected system behavior. Such situations can cause false positives and false negatives, which waste time and reduce defect detection effectiveness, respectively. Early involvement of testers in user story refinement or static testing activities, such as reviews, helps to reduce the incidence of such situations.</p><h4><strong>2.2.4 Acceptance Testing</strong></h4><p><strong>Objectives of acceptance testing.</strong></p><p>Acceptance testing, like system testing, typically focuses on the behavior and capabilities of a whole system or product. Objectives of acceptance testing include:</p><ul><li>Establishing confidence in the quality of the system as a whole.</li><li>Validating that the system is complete and will work as expected.</li><li>Verifying that functional and non-functional behaviors of the system are as specified.</li></ul><p>Acceptance testing may produce information to assess the system’s readiness for deployment and use by the customer (end-user). Defects may be found during acceptance testing, but finding defects is often not an objective, and finding a significant number of defects during acceptance testing may in some cases be considered a major project risk. Acceptance testing may also satisfy legal or regulatory requirements or standards.</p><p>Common forms of acceptance testing include the following:</p><ul><li>User acceptance testing.</li><li>Operational acceptance testing.</li><li>Contractual and regulatory acceptance testing.</li><li>Alpha and beta testing.</li></ul><p>Each is described in the following four subsections.</p><p><strong>User acceptance testing (UAT).</strong></p><p>The acceptance testing of the system by users is typically focused on validating the fitness for use of the system by intended users in a real or simulated operational environment. The main objective is building confidence that the users can use the system to meet their needs, fulfill requirements, and perform business processes with minimum difficulty, cost, and risk.</p><p><strong>Operational acceptance testing (OAT).</strong></p><p>The acceptance testing of the system by operations or systems administration staff is usually performed in a (simulated) production environment. The tests focus on operational aspects, and may include:</p><ul><li>Testing of backup and restore;</li><li>Installing, uninstalling and upgrading;</li><li>Disaster recovery;</li><li>User management;</li><li>Maintenance tasks;</li><li>Data load and migration tasks;</li><li>Checks for security vulnerabilities;</li><li>Performance testing.</li></ul><p>The main objective of operational acceptance testing is building confidence that the operators or system administrators can keep the system working properly for the users in the operational environment, even under exceptional or difficult conditions.</p><p><strong>Contractual and regulatory acceptance testing.</strong></p><p>Contractual acceptance testing is performed against a contract’s acceptance criteria for producing custom-developed software. Acceptance criteria should be defined when the parties agree to the contract. Contractual acceptance testing is often performed by users or by independent testers.</p><p>Regulatory acceptance testing is performed against any regulations that must be adhered to, such as government, legal, or safety regulations. Regulatory acceptance testing is often performed by users or by independent testers, sometimes with the results being witnessed or audited by regulatory agencies.</p><p>The main objective of contractual and regulatory acceptance testing is building confidence that contractual or regulatory compliance has been achieved.</p><p><strong>Alpha and beta testing.</strong></p><p>Alpha and beta testing are typically used by developers of commercial off-the-shelf (COTS) software who want to get feedback from potential or existing users, customers, and/or operators before the software product is put on the market. Alpha testing is performed at the developing organization’s site, not by the development team, but by potential or existing customers, and/or operators or an independent test team.</p><p>Beta testing is performed by potential or existing customers, and/or operators at their own locations. Beta testing may come after alpha testing, or may occur without any preceding alpha testing having occurred.</p><p>One objective of alpha and beta testing is building confidence among potential or existing customers, and/or operators that they can use the system under normal, everyday conditions, and in the operational environment(s) to achieve their objectives with minimum difficulty, cost, and risk. Another objective may be the detection of defects related to the conditions and environment(s) in which the system will be used, especially when those conditions and environment(s) are difficult to replicate by the development team.</p><p><strong>Test basis.</strong></p><p>Examples of work products that can be used as a test basis for any form of acceptance testing include:</p><ul><li>Business processes;</li><li>User or business requirements;</li><li>Regulations, legal contracts and standards;</li><li>Use cases;</li><li>System requirements;</li><li>System or user documentation;</li><li>Installation procedures;</li><li>Risk analysis reports.</li></ul><p>In addition, as a test basis for deriving test cases for operational acceptance testing, one or more of the following work products can be used:</p><ul><li>Backup and restore procedures;</li><li>Disaster recovery procedures;</li><li>Non-functional requirements;</li><li>Operations documentation;</li><li>Deployment and installation instructions;</li><li>Performance targets;</li><li>Database packages;</li><li>Security standards or regulations.</li></ul><p><strong>Typical test objects.</strong></p><p>Typical test objects for any form of acceptance testing include:</p><ul><li>System under test;</li><li>System configuration and configuration data;</li><li>Business processes for a fully integrated system;</li><li>Recovery systems and hot sites (for business continuity and disaster recovery testing);</li><li>Operational and maintenance processes;</li><li>Forms;</li><li>Reports;</li><li>Existing and converted production data.</li></ul><p><strong>Typical defects and failures.</strong></p><p>Examples of typical defects for any form of acceptance testing include:</p><ul><li>System workflows do not meet business or user requirements;</li><li>Business rules are not implemented correctly;</li><li>System does not satisfy contractual or regulatory requirements;</li><li>Non-functional failures such as security vulnerabilities, inadequate performance efficiency under high loads, or improper operation on a supported platform.</li></ul><p><strong>Specific approaches and responsibilities.</strong></p><p>Acceptance testing is often the responsibility of the customers, business users, product owners, or operators of a system, and other stakeholders may be involved as well.</p><p>Acceptance testing is often thought of as the last test level in a sequential development lifecycle, but it may also occur at other times, for example:</p><ul><li>Acceptance testing of a COTS software product may occur when it is installed or integrated.</li><li>Acceptance testing of a new functional enhancement may occur before system testing.</li></ul><p>In iterative development, project teams can employ various forms of acceptance testing during and at the end of each iteration, such as those focused on verifying a new feature against its acceptance criteria and those focused on validating that a new feature satisfies the users’ needs. In addition, alpha tests and beta tests may occur, either at the end of each iteration, after the completion of each iteration, or after a series of iterations. User acceptance tests, operational acceptance tests, regulatory acceptance tests, and contractual acceptance tests also may occur, either at the close of each iteration, after the completion of each iteration, or after a series of iterations.</p><h3>2.3 Test Types</h3><p>A test type is a group of test activities aimed at testing specific characteristics of a software system, or a part of a system, based on specific test objectives. Such objectives may include:</p><ul><li>Evaluating functional quality characteristics, such as completeness, correctness, and appropriateness.</li><li>Evaluating non-functional quality characteristics, such as reliability, performance efficiency, security, compatibility, and usability.</li><li>Evaluating whether the structure or architecture of the component or system is correct, complete, and as specified.</li><li>Evaluating the effects of changes, such as confirming that defects have been fixed (confirmation testing) and looking for unintended changes in behavior resulting from software or environment changes (regression testing).</li></ul><h4><strong>2.3.1 Functional Testing</strong></h4><p>Functional testing of a system involves tests that evaluate functions that the system should perform.</p><p>Functional requirements may be described in work products such as business requirements specifications, epics, user stories, use cases, or functional specifications, or they may be undocumented.</p><p>The functions are “what” the system should do.</p><p>Functional tests should be performed at all test levels (e.g., tests for components may be based on a component specification), though the focus is different at each level (see section 2.2, Test Levels).</p><p>Functional testing considers the behavior of the software, so black-box techniques may be used to derive test conditions and test cases for the functionality of the component or system (see section 4.2, Black-box Test Techniques).</p><p>The thoroughness of functional testing can be measured through functional coverage. Functional coverage is the extent to which some type of functional element has been exercised by tests, and is expressed as a percentage of the type(s) of element being covered. For example, using traceability between tests and functional requirements, the percentage of these requirements which are addressed by testing can be calculated, potentially identifying coverage gaps.</p><p>Functional test design and execution may involve special skills or knowledge, such as knowledge of the particular business problem the software solves (e.g., geological modelling software for the oil and gas industries) or the particular role the software serves (e.g., computer gaming software that provides interactive entertainment).</p><h4><strong>2.3.2 Non-functional Testing</strong></h4><p>Non-functional testing of a system evaluates characteristics of systems and software such as usability, performance efficiency or security. Refer to ISO standard (ISO/IEC 25010) for a classification of software product quality characteristics. Non-functional testing is the testing of “how well” the system behaves.</p><p>Contrary to common misperceptions, non-functional testing can and often should be performed at all test levels, and done as early as possible. The late discovery of non-functional defects can be extremely dangerous to the success of a project.</p><p>Black-box techniques (see section 4.2) may be used to derive test conditions and test cases for nonfunctional testing. For example, boundary value analysis can be used to define the stress conditions for performance tests.</p><p>The thoroughness of non-functional testing can be measured through non-functional coverage. Nonfunctional coverage is the extent to which some type of non-functional element has been exercised by tests, and is expressed as a percentage of the type(s) of element being covered. For example, using traceability between tests and supported devices for a mobile application, the percentage of devices which are addressed by compatibility testing can be calculated, potentially identifying coverage gaps.</p><p>Non-functional test design and execution may involve special skills or knowledge, such as knowledge of the inherent weaknesses of a design or technology (e.g., security vulnerabilities associated with particular programming languages) or the particular user base (e.g., the personas of users of healthcare facility management systems).</p><p>Refer to ISTQB-ATA Advanced Level Test Analyst Syllabus, ISTQB-ATTA Advanced Level Technical Test Analyst Syllabus, ISTQB-SEC Advanced Level Security Tester Syllabus, and other ISTQB specialist modules for more details regarding the testing of non-functional quality characteristics.</p><h4><strong>2.3.3 White-box Testing</strong></h4><p>White-box testing derives tests based on the system’s internal structure or implementation. Internal structure may include code, architecture, work flows, and/or data flows within the system (see section 4.3, White-box Test Techniques).</p><p>The thoroughness of white-box testing can be measured through structural coverage. Structural coverage is the extent to which some type of structural element has been exercised by tests, and is expressed as a percentage of the type of element being covered.</p><p>At the component testing level, code coverage is based on the percentage of component code that has been tested, and may be measured in terms of different aspects of code (coverage items) such as the percentage of executable statements tested in the component, or the percentage of decision outcomes tested. These types of coverage are collectively called code coverage. At the component integration testing level, white-box testing may be based on the architecture of the system, such as interfaces between components, and structural coverage may be measured in terms of the percentage of interfaces exercised by tests.</p><p>White-box test design and execution may involve special skills or knowledge, such as the way the code is built (e.g., to use code coverage tools), how data is stored (e.g., to evaluate possible database queries), and how to use coverage tools and to correctly interpret their results.</p><h4><strong>2.3.4 Change-related Testing</strong></h4><p>When changes are made to a system, either to correct a defect or because of new or changing functionality, testing should be done to confirm that the changes have corrected the defect or implemented the functionality correctly, and have not caused any unforeseen adverse consequences.</p><ul><li><strong>Confirmation testing</strong>: After a defect is fixed, the software may be tested with all test cases that failed due to the defect, which should be re-executed on the new software version. The software may also be tested with new tests if, for instance, the defect was missing functionality. At the very least, the steps to reproduce the failure(s) caused by the defect must be re-executed on the new software version. The purpose of a confirmation test is to confirm whether the original defect has been successfully fixed.</li><li><strong>Regression testing</strong>: It is possible that a change made in one part of the code, whether a fix or another type of change, may accidentally affect the behavior of other parts of the code, whether within the same component, in other components of the same system, or even in other systems. Changes may include changes to the environment, such as a new version of an operating system or database management system. Such unintended side-effects are called regressions. Regression testing involves running tests to detect such unintended side-effects.</li></ul><p>Confirmation testing and regression testing are performed at all test levels.</p><p>Especially in iterative and incremental development lifecycles (e.g., Agile), new features, changes to existing features, and code refactoring result in frequent changes to the code, which also requires change-related testing. Due to the evolving nature of the system, confirmation and regression testing are very important. This is particularly relevant for Internet of Things systems where individual objects (e.g., devices) are frequently updated or replaced.</p><p>Regression test suites are run many times and generally evolve slowly, so regression testing is a strong candidate for automation. Automation of these tests should start early in the project (see chapter 6, Tool Support for Testing).</p><h4><strong>2.3.5 Test Types and Test Levels</strong></h4><p>It is possible to perform any of the test types mentioned above at any test level. To illustrate, examples of functional, non-functional, white-box, and change-related tests will be given across all test levels, for a banking application, starting with functional tests:</p><ul><li>For component testing, tests are designed based on how a component should calculate compound interest.</li><li>For component integration testing, tests are designed based on how account information captured at the user interface is passed to the business logic.</li><li>For system testing, tests are designed based on how account holders can apply for a line of credit on their checking accounts.</li><li>For system integration testing, tests are designed based on how the system uses an external microservice to check an account holder’s credit score.</li><li>For acceptance testing, tests are designed based on how the banker handles approving or declining a credit application.</li></ul><p>The following are examples of non-functional tests:</p><ul><li>For component testing, performance tests are designed to evaluate the number of CPU cycles required to perform a complex total interest calculation.</li><li>For component integration testing, security tests are designed for buffer overflow vulnerabilities due to data passed from the user interface to the business logic.</li><li>For system testing, portability tests are designed to check whether the presentation layer works on all supported browsers and mobile devices.</li><li>For system integration testing, reliability tests are designed to evaluate system robustness if the credit score microservice fails to respond.</li><li>For acceptance testing, usability tests are designed to evaluate the accessibility of the banker’s credit processing interface for people with disabilities.</li></ul><p>The following are examples of white-box tests:</p><ul><li>For component testing, tests are designed to achieve complete statement and decision coverage (see section 4.3, White-box Test Techniques) for all components that perform financial calculations.</li><li>For component integration testing, tests are designed to exercise how each screen in the browser interface passes data to the next screen and to the business logic.</li><li>For system testing, tests are designed to cover sequences of web pages that can occur during a credit line application.</li><li>For system integration testing, tests are designed to exercise all possible inquiry types sent to the credit score microservice.</li><li>For acceptance testing, tests are designed to cover all supported financial data file structures and value ranges for bank-to-bank transfers.</li></ul><p>Finally, the following are examples for change-related tests:</p><ul><li>For component testing, automated regression tests are built for each component and included within the continuous integration framework.</li><li>For component integration testing, tests are designed to confirm fixes to interface-related defects as the fixes are checked into the code repository.</li><li>For system testing, all tests for a given workflow are re-executed if any screen on that workflow changes.</li><li>For system integration testing, tests of the application interacting with the credit scoring microservice are re-executed daily as part of continuous deployment of that microservice.</li><li>For acceptance testing, all previously-failed tests are re-executed after a defect found in acceptance testing is fixed.</li></ul><p>While this section provides examples of every test type across every level, it is not necessary, for all software, to have every test type represented across every level. However, it is important to run applicable test types at each level, especially the earliest level where the test type occurs.</p><h3>2.4 Maintenance Testing</h3><p>Once deployed to production environments, software and systems need to be maintained. Changes of various sorts are almost inevitable in delivered software and systems, either to fix defects discovered in operational use, to add new functionality, or to delete or alter already-delivered functionality. Maintenance is also needed to preserve or improve non-functional quality characteristics of the component or system over its lifetime, especially performance efficiency, compatibility, reliability, security, compatibility, and portability.</p><p>When any changes are made as part of maintenance, maintenance testing should be performed, both to evaluate the success with which the changes were made and to check for possible side-effects (e.g., regressions) in parts of the system that remain unchanged (which is usually most of the system).</p><p>Maintenance testing focuses on testing the changes to the system, as well as testing unchanged parts that might have been affected by the changes. Maintenance can involve planned releases and unplanned releases (hot fixes).</p><p>A maintenance release may require maintenance testing at multiple test levels, using various test types, based on its scope. The scope of maintenance testing depends on:</p><ul><li>The degree of risk of the change, for example, the degree to which the changed area of software communicates with other components or systems.</li><li>The size of the existing system.</li><li>The size of the change.</li></ul><h4><strong>2.4.1 Triggers for Maintenance</strong></h4><p>There are several reasons why software maintenance, and thus maintenance testing, takes place, both for planned and unplanned changes.</p><p>We can classify the triggers for maintenance as follows:</p><ul><li>Modification, such as planned enhancements (e.g., release-based), corrective and emergency changes, changes of the operational environment (such as planned operating system or database upgrades), upgrades of COTS software, and patches for defects and vulnerabilities</li><li>Migration, such as from one platform to another, which can require operational tests of the new environment as well as of the changed software, or tests of data conversion when data from another application will be migrated into the system being maintained</li><li>Retirement, such as when an application reaches the end of its life</li></ul><p>When an application or system is retired, this can require testing of data migration or archiving if long data-retention periods are required. Testing restore/retrieve procedures after archiving for long retention periods may also be needed. In addition regression testing may be needed to ensure that any functionality that remains in service still works.</p><p>For Internet of Things systems, maintenance testing may be triggered by the introduction of completely new or modified things, such as hardware devices and software services, into the overall system. The maintenance testing for such systems places particular emphasis on integration testing at different levels (e.g., network level, application level) and on security aspects, in particular those relating to personal data.</p><h4><strong>2.4.2 Impact Analysis for Maintenance</strong></h4><p>Impact analysis evaluates the changes that were made for a maintenance release to identify the intended consequences as well as expected and possible side effects of a change, and to identify the areas in the system that will be affected by the change. Impact analysis can also help to identify the impact of a change on existing tests. The side effects and affected areas in the system need to be tested for regressions, possibly after updating any existing tests affected by the change.</p><p>Impact analysis may be done before a change is made, to help decide if the change should be made, based on the potential consequences in other areas of the system.</p><p>Impact analysis can be difficult if:</p><ul><li>Specifications (e.g., business requirements, user stories, architecture) are out of date or missing.</li><li>Test cases are not documented or are out of date.</li><li>Bi-directional traceability between tests and the test basis has not been maintained.</li><li>Tool support is weak or non-existent.</li><li>The people involved do not have domain and/or system knowledge.</li><li>Insufficient attention has been paid to the software’s maintainability during development.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e85155a27ccf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ISTQB Foundation Level Syllabus]]></title>
            <link>https://medium.com/@HugoSaxTavares/istqb-foundation-level-syllabus-526e7cc7db4c?source=rss-4bf118ee381a------2</link>
            <guid isPermaLink="false">https://medium.com/p/526e7cc7db4c</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[istqb-certification]]></category>
            <dc:creator><![CDATA[Hugo Bandeira Tavares]]></dc:creator>
            <pubDate>Wed, 27 Nov 2019 22:31:27 GMT</pubDate>
            <atom:updated>2019-11-28T15:31:43.087Z</atom:updated>
            <content:encoded><![CDATA[<h3>ISTQB Foundation Level Syllabus, Chapter 1 of 6: Fundamentals of Testing</h3><blockquote>Disclaimer: this article is a copy from the original document available <a href="https://www.istqb.org/downloads/send/2-foundation-level-documents/281-istqb-ctfl-syllabus-2018-v3-1.html">here</a>.<br>All rights belong to International Software Testing Qualifications Board (hereinafter called ISTQB®). ISTQB is a registered trademark of the International Software Testing Qualifications Board.</blockquote><blockquote>This is only here for study purposes of the author.</blockquote><h3>Keywords</h3><p>coverage, debugging, defect, error, failure, quality, quality assurance, root cause, test analysis, test basis, test case, test completion, test condition, test control, test data, test design, test execution, test execution schedule, test implementation, test monitoring, test object, test objective, test oracle, test planning, test procedure, test suite, testing, testware, traceability, validation, verification</p><h3>1.1 What is Testing?</h3><p>Software systems are an integral part of life, from business applications (e.g., banking) to consumer products (e.g., cars). Most people have had an experience with software that did not work as expected.</p><p>Software that does not work correctly can lead to many problems, including loss of money, time, or business reputation, and even injury or death. Software testing is a way to assess the quality of the software and to reduce the risk of software failure in operation.</p><p>A common misperception of testing is that it only consists of running tests, i.e., executing the software and checking the results. As described in section 1.4, Test Process, software testing is a process which includes many different activities; test execution (including checking of results) is only one of these activities. The test process also includes activities such as test planning, analyzing, designing, and implementing tests, reporting test progress and results, and evaluating the quality of a test object.</p><p>Some testing does involve the execution of the component or system being tested; such testing is called dynamic testing. Other testing does not involve the execution of the component or system being tested; such testing is called static testing. So, testing also includes reviewing work products such as requirements, user stories, and source code.</p><p>Another common misperception of testing is that it focuses entirely on verification of requirements, user stories, or other specifications. While testing does involve checking whether the system meets specified requirements, it also involves validation, which is checking whether the system will meet user and other stakeholder needs in its operational environment(s).</p><p>Test activities are organized and carried out differently in different lifecycles (see section 2.1 Software Development Lifecycle Models).</p><h4>1.1.1 Typical Objectives of Testing</h4><p>For any given project, the objectives of testing may include:</p><ul><li>To evaluate work products such as requirements, user stories, design, and code.</li><li>To verify whether all specified requirements have been fulfilled.</li><li>To validate whether the test object is complete and works as the users and other stakeholders expect.</li><li>To build confidence in the level of quality of the test object.</li><li>To prevent defects.</li><li>To find failures and defects.</li><li>To provide sufficient information to stakeholders to allow them to make informed decisions, especially regarding the level of quality of the test object.</li><li>To reduce the level of risk of inadequate software quality (e.g., previously undetected failures occurring in operation).</li><li>To comply with contractual, legal, or regulatory requirements or standards, and/or to verify the test object’s compliance with such requirements or standards.</li></ul><p>The objectives of testing can vary, depending upon the context of the component or system being tested, the test level, and the software development lifecycle model. These differences may include, for example:</p><ul><li>During component testing, one objective may be to find as many failures as possible so that the underlying defects are identified and fixed early. Another objective may be to increase code coverage of the component tests.</li><li>During acceptance testing, one objective may be to confirm that the system works as expected and satisfies requirements. Another objective of this testing may be to give information to stakeholders about the risk of releasing the system at a given time.</li></ul><h4>1.1.2 Testing and Debugging</h4><p>Testing and debugging are different. Executing tests can show failures that are caused by defects in the software. Debugging is the development activity that finds, analyzes, and fixes such defects. Subsequent confirmation testing checks whether the fixes resolved the defects. In some cases, testers are responsible for the initial test and the final confirmation test, while developers do the debugging and associated component testing. However, in Agile development and in some other lifecycles, testers may be involved in debugging and component testing.</p><p>ISO standard (ISO/IEC/IEEE 29119–1) has further information about software testing concepts.</p><h3>1.2 Why is Testing Necessary?</h3><p>Rigorous testing of components and systems, and their associated documentation, can help reduce the risk of failures occurring during operation. When defects are detected, and subsequently fixed, this contributes to the quality of the components or systems. In addition, software testing may also be required to meet contractual or legal requirements or industry-specific standards.</p><h4>1.2.1 Testing’s Contributions to Success</h4><p>Throughout the history of computing, it is quite common for software and systems to be delivered into operation and, due to the presence of defects, to subsequently cause failures or otherwise not meet the stakeholders’ needs. However, using appropriate test techniques can reduce the frequency of such problematic deliveries, when those techniques are applied with the appropriate level of test expertise, in the appropriate test levels, and at the appropriate points in the software development lifecycle.</p><p>Examples include:</p><ul><li>Having testers involved in requirements reviews or user story refinement could detect defects in these work products. The identification and removal of requirements defects reduces the risk of incorrect or untestable functionality being developed.</li><li>Having testers work closely with system designers while the system is being designed can increase each party’s understanding of the design and how to test it. This increased understanding can reduce the risk of fundamental design defects and enable tests to be identified at an early stage.</li><li>Having testers work closely with developers while the code is under development can increase each party’s understanding of the code and how to test it. This increased understanding can reduce the risk of defects within the code and the tests.</li><li>Having testers verify and validate the software prior to release can detect failures that might otherwise have been missed, and support the process of removing the defects that caused the failures (i.e., debugging). This increases the likelihood that the software meets stakeholder needs and satisfies requirements.</li></ul><p>In addition to these examples, the achievement of defined test objectives (see section 1.1.1, Typical Objectives of Testing) contributes to overall software development and maintenance success.</p><h4>1.2.2 Quality Assurance and Testing</h4><p>While people often use the phrase <strong>quality assurance</strong> (or just QA) to refer to testing, <strong>quality assurance and testing are not the same</strong>, but they are related. A larger concept, <strong>quality management</strong>, <strong>ties them together</strong>.</p><p><strong>Quality management includes all activities that direct and control an organization with regard to quality.</strong></p><p>Among other activities, <strong>quality management includes both quality assurance and quality control</strong>. Quality assurance is typically focused on adherence to proper processes, in order to provide confidence that the appropriate levels of quality will be achieved. When processes are carried out properly, the work products created by those processes are generally of higher quality, which contributes to defect prevention. In addition, the use of root cause analysis to detect and remove the causes of defects, along with the proper application of the findings of retrospective meetings to improve processes, are important for effective quality assurance.</p><p>Quality control involves various activities, including test activities, that support the achievement of appropriate levels of quality. Test activities are part of the overall software development or maintenance process. Since quality assurance is concerned with the proper execution of the entire process, quality assurance supports proper testing. As described in sections 1.1.1, Typical Objectives of Testing, and 1.2.1, Testing’s Contributions to Success, testing contributes to the achievement of quality in a variety of ways.</p><h4>1.2.3 Errors, Defects, and Failures</h4><p>A person can make an error (mistake), which can lead to the introduction of a defect (fault or bug) in the software code or in some other related work product. An error that leads to the introduction of a defect in one work product can trigger an error that leads to the introduction of a defect in a related work product.</p><p>For example, a requirements elicitation error can lead to a requirements defect, which then results in a programming error that leads to a defect in the code.</p><p>If a defect in the code is executed, this may cause a failure, but not necessarily in all circumstances. For example, some defects require very specific inputs or preconditions to trigger a failure, which may occur rarely or never.</p><p>Errors may occur for many reasons, such as:</p><ul><li>Time pressure;</li><li>Human fallibility;</li><li>Inexperienced or insufficiently skilled project participants;</li><li>Miscommunication between project participants, including miscommunication about requirements and design;</li><li>Complexity of the code, design, architecture, the underlying problem to be solved, and/or the technologies used;</li><li>Misunderstandings about intra-system and inter-system interfaces, especially when such intra-system and inter-system interactions are large in number;</li><li>New, unfamiliar technologies.</li></ul><p>In addition to failures caused due to defects in the code, failures can also be caused by environmental conditions. For example, radiation, electromagnetic fields, and pollution can cause defects in firmware or influence the execution of software by changing hardware conditions.</p><p>Not all unexpected test results are failures. False positives may occur due to errors in the way tests were executed, or due to defects in the test data, the test environment, or other testware, or for other reasons. The inverse situation can also occur, where similar errors or defects lead to false negatives. False negatives are tests that do not detect defects that they should have detected; false positives are reported as defects, but aren’t actually defects.</p><h4>1.2.4 Defects, Root Causes and Effects</h4><p>The root causes of defects are the earliest actions or conditions that contributed to creating the defects. Defects can be analyzed to identify their root causes, so as to reduce the occurrence of similar defects in the future. By focusing on the most significant root causes, root cause analysis can lead to process improvements that prevent a significant number of future defects from being introduced.</p><p>For example, suppose incorrect interest payments, due to a single line of incorrect code, result in customer complaints. The defective code was written for a user story which was ambiguous, due to the product owner’s misunderstanding of how to calculate interest. If a large percentage of defects exist in interest calculations, and these defects have their root cause in similar misunderstandings, the product owners could be trained in the topic of interest calculations to reduce such defects in the future.</p><p>In this example, the customer complaints are effects. The incorrect interest payments are failures. The improper calculation in the code is a defect, and it resulted from the original defect, the ambiguity in the user story. The root cause of the original defect was a lack of knowledge on the part of the product owner, which resulted in the product owner making a mistake while writing the user story.</p><p>The process of root cause analysis is discussed in ISTQB-ETM Expert Level Test Management Syllabus and ISTQB-EITP Expert Level Improving the Test Process Syllabus.</p><h3>1.3 Seven Testing Principles</h3><p>A number of testing principles have been suggested over the past 50 years and offer general guidelines common for all testing.</p><h4>Principle 1: Testing shows the presence of defects, not their absence</h4><p>Testing can show that defects are present, but cannot prove that there are no defects. Testing reduces the probability of undiscovered defects remaining in the software but, even if no defects are found, testing is not a proof of correctness.</p><h4>Principle 2: Exhaustive testing is impossible</h4><p>Testing everything (all combinations of inputs and preconditions) is not feasible except for trivial cases.</p><p>Rather than attempting to test exhaustively, risk analysis, test techniques, and priorities should be used to focus test efforts.</p><h4>Principle 3: Early testing saves time and money</h4><p>To find defects early, both static and dynamic test activities should be started as early as possible in the software development lifecycle. Early testing is sometimes referred to as shift left. Testing early in the software development lifecycle helps reduce or eliminate costly changes (see section 3.1 Static Testing Basics).</p><h4>Principle 4: Defects cluster together</h4><p>A small number of modules usually contains most of the defects discovered during pre-release testing, or is responsible for most of the operational failures. Predicted defect clusters, and the actual observed defect clusters in test or operation, are an important input into a risk analysis used to focus the test effort (as mentioned in principle 2: Exhaustive testing is impossible).</p><h4>Principle 5: Beware of the pesticide paradox</h4><p>If the same tests are repeated over and over again, eventually these tests no longer find any new defects.</p><p>To detect new defects, existing tests and test data may need changing, and new tests may need to be written. (Tests are no longer effective at finding defects, just as pesticides are no longer effective at killing insects after a while.) In some cases, such as automated regression testing, the pesticide paradox has a beneficial outcome, which is the relatively low number of regression defects.</p><h4>Principle 6: Testing is context dependent</h4><p>Testing is done differently in different contexts. For example, safety-critical industrial control software is tested differently from an e-commerce mobile app. As another example, testing in an Agile project is done differently than testing in a sequential lifecycle project (see section 2.1, Software Development Lifecycle Models).</p><h4>Principle 7: Absence-of-errors is a fallacy</h4><p>Some organizations expect that testers can run all possible tests and find all possible defects, but principles 2 and 1, respectively, tell us that this is impossible. Further, it is a fallacy (i.e., a mistaken belief) to expect that just finding and fixing a large number of defects will ensure the success of a system. For example, thoroughly testing all specified requirements and fixing all defects found could still produce a system that is difficult to use, that does not fulfill the users’ needs and expectations, or that is inferior compared to other competing systems.</p><h3>1.4 Test Process</h3><p>There is no one universal software test process, but there are common sets of test activities without which testing will be less likely to achieve its established objectives. These sets of test activities are a test process. The proper, specific software test process in any given situation depends on many factors.</p><p>Which test activities are involved in this test process, how these activities are implemented, and when these activities occur may be discussed in an organization’s test strategy.</p><h4>1.4.1 Test Process in Context</h4><p>Contextual factors that influence the test process for an organization, include, but are not limited to:</p><ul><li>Software development lifecycle model and project methodologies being used;</li><li>Test levels and test types being considered;</li><li>Product and project risks;</li><li>Business domain;</li><li>Operational constraints, including but not limited to: (i) budgets and resources, (ii) timescales, (iii) complexity, (iv) contractual and regulatory requirements;</li><li>Organizational policies and practices;</li><li>Required internal and external standards.</li></ul><p>The following sections describe general aspects of organizational test processes in terms of the following:</p><ul><li>Test activities and tasks;</li><li>Test work products;</li><li>Traceability between the test basis and test work products.</li></ul><p>It is very useful if the test basis (for any level or type of testing that is being considered) has measurable coverage criteria defined. The coverage criteria can act effectively as key performance indicators (KPIs) to drive the activities that demonstrate achievement of software test objectives (see section 1.1.1, Typical Objectives of Testing).</p><p>For example, for a mobile application, the test basis may include a list of requirements and a list of supported mobile devices. Each requirement is an element of the test basis. Each supported device is also an element of the test basis. The coverage criteria may require at least one test case for each element of the test basis. Once executed, the results of these tests tell stakeholders whether specified requirements are fulfilled and whether failures were observed on supported devices.</p><p>ISO standard (ISO/IEC/IEEE 29119–2) has further information about test processes.</p><h4>1.4.2 Test Activities and Tasks</h4><p>A test process consists of the following main groups of activities:</p><ul><li>Test planning;</li><li>Test monitoring and control;</li><li>Test analysis;</li><li>Test design;</li><li>Test implementation;</li><li>Test execution;</li><li>Test completion.</li></ul><p>Each group of activities is composed of constituent activities, which will be described in the subsections below. Each activity within each group of activities in turn may consist of multiple individual tasks, which would vary from one project or release to another.</p><p>Further, although many of these activity groups may appear logically sequential, they are often implemented iteratively. For example, Agile development involves small iterations of software design, build, and test that happen on a continuous basis, supported by on-going planning. So test activities are also happening on an iterative, continuous basis within this development approach. Even in sequential development, the stepped logical sequence of activities will involve overlap, combination, concurrency, or omission, so tailoring these main activities within the context of the system and the project is usually required.</p><p><strong>Test planning.</strong></p><p>Test planning involves activities that define the objectives of testing and the approach for meeting test objectives within constraints imposed by the context (e.g., specifying suitable test techniques and tasks, and formulating a test schedule for meeting a deadline). Test plans may be revisited based on feedback from monitoring and control activities. Test planning is further explained in section 5.2, Test Planning and Estimation.</p><p><strong>Test monitoring and control.</strong></p><p>Test monitoring involves the on-going comparison of actual progress against the test plan using any test monitoring metrics defined in the test plan. Test control involves taking actions necessary to meet the objectives of the test plan (which may be updated over time). Test monitoring and control are supported by the evaluation of exit criteria, which are referred to as the definition of done in some lifecycles (see ISTQB-AT Foundation Level Agile Tester Extension Syllabus). For example, the evaluation of exit criteria for test execution as part of a given test level may include:</p><ul><li>Checking test results and logs against specified coverage criteria.</li><li>Assessing the level of component or system quality based on test results and logs.</li><li>Determining if more tests are needed (e.g., if tests originally intended to achieve a certain level of product risk coverage failed to do so, requiring additional tests to be written and executed).</li></ul><p>Test progress against the plan is communicated to stakeholders in test progress reports, including deviations from the plan and information to support any decision to stop testing.</p><p>Test monitoring and control are further explained in section 5.3 Test Monitoring and Control.</p><p><strong>Test analysis.</strong></p><p>During test analysis, the test basis is analyzed to identify testable features and define associated test conditions. In other words, test analysis determines “what to test” in terms of measurable coverage criteria. Test analysis includes the following major activities:</p><ul><li>Analyzing the test basis appropriate to the test level being considered, for example:</li></ul><ol><li>Requirement specifications, such as business requirements, functional requirements, system requirements, user stories, epics, use cases, or similar work products that specify desired functional and non-functional component or system behavior.</li><li>Design and implementation information, such as system or software architecture diagrams or documents, design specifications, call flows, modelling diagrams (e.g., UML or entity-relationship diagrams), interface specifications, or similar work products that specify component or system structure.</li><li>The implementation of the component or system itself, including code, database metadata and queries, and interfaces.</li><li>Risk analysis reports, which may consider functional, non-functional, and structural aspects of the component or system.</li></ol><ul><li>Evaluating the test basis and test items to identify defects of various types, such as:</li></ul><ol><li>Ambiguities;</li><li>Omissions;</li><li>Inconsistencies;</li><li>Inaccuracies;</li><li>Contradictions;</li><li>Superfluous statements.</li></ol><ul><li>Identifying features and sets of features to be tested.</li><li>Defining and prioritizing test conditions for each feature based on analysis of the test basis, and considering functional, non-functional, and structural characteristics, other business and technical factors, and levels of risks.</li><li>Capturing bi-directional traceability between each element of the test basis and the associated test conditions (see sections 1.4.3, Test Work Products, and 1.4.4, Traceability between the Test Basis and Test Work Products).</li></ul><p><strong>The application of black-box, white-box, and experience-based test techniques can be useful in the process of test analysis</strong> (see chapter 4, Test Techniques) to reduce the likelihood of omitting important test conditions and to define more precise and accurate test conditions.</p><p>In some cases, <strong>test analysis produces test conditions which are to be used as test objectives in test charters</strong>. Test charters are typical work products in some types of experience-based testing (see section 4.4.2, Exploratory Testing). When these test objectives are traceable to the test basis, coverage achieved during such experience-based testing can be measured.</p><p>The identification of defects during test analysis is an important potential benefit, especially where no other review process is being used and/or the test process is closely connected with the review process.</p><p>Such test analysis activities not only verify whether the requirements are consistent, properly expressed, and complete, but also validate whether the requirements properly capture customer, user, and other stakeholder needs. For example, techniques such as <strong>behavior driven development</strong> (BDD) and <strong>acceptance test driven development</strong> (ATDD), which involve generating test conditions and test cases from user stories and acceptance criteria prior to coding, also verify, validate, and detect defects in the user stories and acceptance criteria (see ISTQB Foundation Level Agile Tester Extension syllabus).</p><p><strong>Test design.</strong></p><p>During test design, the test conditions are elaborated into high-level test cases, sets of high-level test cases, and other testware. So, test analysis answers the question “what to test?” while test design answers the question “how to test?”.</p><p>Test design includes the following major activities:</p><ul><li>Designing and prioritizing test cases and sets of test cases.</li><li>Identifying necessary test data to support test conditions and test cases.</li><li>Designing the test environment and identifying any required infrastructure and tools.</li><li>Capturing bi-directional traceability between the test basis, test conditions, test cases, and test procedures (see section 1.4.4, Traceability between the Test Basis and Test Work Products).</li></ul><p>The elaboration of test conditions into test cases and sets of test cases during test design often involves using test techniques (see chapter, 4 Test Techniques).</p><p>As with test analysis, test design may also result in the identification of similar types of defects in the test basis. Also as with test analysis, the identification of defects during test design is an important potential benefit.</p><p><strong>Test implementation.</strong></p><p>During test implementation, the testware necessary for test execution is created and/or completed, including sequencing the test cases into test procedures. So, test design answers the question “how to test?” while test implementation answers the question “do we now have everything in place to run the tests?”.</p><p>Test implementation includes the following major activities:</p><ul><li>Developing and prioritizing test procedures, and, potentially, creating automated test scripts;</li><li>Creating test suites from the test procedures and (if any) automated test scripts;</li><li>Arranging the test suites within a test execution schedule in a way that results in efficient test execution (see section 5.2.4, Test Execution Schedule).</li><li>Building the test environment (including, potentially, test harnesses, service virtualization, simulators, and other infrastructure items) and verifying that everything needed has been set up correctly.</li><li>Preparing test data and ensuring it is properly loaded in the test environment.</li><li>Verifying and updating bi-directional traceability between the test basis, test conditions, test cases, test procedures, and test suites (see section 1.4.4, Traceability between the Test Basis and Test Work Products).</li></ul><p>Test design and test implementation tasks are often combined.</p><p>In exploratory testing and other types of experience-based testing, test design and implementation may occur, and may be documented, as part of test execution. Exploratory testing may be based on test charters (produced as part of test analysis), and exploratory tests are executed immediately as they are designed and implemented (see section 4.4.2, Exploratory Testing).</p><p><strong>Test execution.</strong></p><p>During test execution, test suites are run in accordance with the test execution schedule.</p><p>Test execution includes the following major activities:</p><ul><li>Recording the IDs and versions of the test item(s) or test object, test tool(s), and testware.</li><li>Executing tests either manually or by using test execution tools.</li><li>Comparing actual results with expected results.</li><li>Analyzing anomalies to establish their likely causes (e.g., failures may occur due to defects in the code, but false positives also may occur [see section 1.2.3, Errors, Defects, and Failures]).</li><li>Reporting defects based on the failures observed (see section 5.6, Defect Management)</li><li>Logging the outcome of test execution (e.g., pass, fail, blocked)</li><li>Repeating test activities either as a result of action taken for an anomaly, or as part of the planned testing (e.g., execution of a corrected test, confirmation testing, and/or regression testing).</li><li>Verifying and updating bi-directional traceability between the test basis, test conditions, test ases, test procedures, and test results.</li></ul><p><strong>Test completion.</strong></p><p>Test completion activities collect data from completed test activities to consolidate experience, testware, and any other relevant information. Test completion activities occur at project milestones such as when a software system is released, a test project is completed (or cancelled), an Agile project iteration is finished (e.g., as part of a retrospective meeting), a test level is completed, or a maintenance release has been completed.</p><p>Test completion includes the following major activities:</p><ul><li>Checking whether all defect reports are closed, entering change requests or product backlog items for any defects that remain unresolved at the end of test execution.</li><li>Creating a test summary report to be communicated to stakeholders.</li><li>Finalizing and archiving the test environment, the test data, the test infrastructure, and other testware for later reuse.</li><li>Handing over the testware to the maintenance teams, other project teams, and/or other stakeholders who could benefit from its use.</li><li>Analyzing lessons learned from the completed test activities to determine changes needed for future iterations, releases, and projects.</li><li>Using the information gathered to improve test process maturity.</li></ul><h4>1.4.3 Test Work Products</h4><p>Test work products are created as part of the test process. Just as there is significant variation in the way that organizations implement the test process, there is also significant variation in the types of work products created during that process, in the ways those work products are organized and managed, and in the names used for those work products. This syllabus adheres to the test process outlined above, and the work products described in this syllabus and in the ISTQB Glossary. ISO standard (ISO/IEC/IEEE 29119–3) may also serve as a guideline for test work products.</p><p>Many of the test work products described in this section can be captured and managed using test management tools and defect management tools (see chapter 6 Tool Support for Testing).</p><p><strong>Test planning work products.</strong></p><p>Test planning work products typically include one or more test plans. The test plan includes information about the test basis, to which the other test work products will be related via traceability information (see below and section 1.4.4, Traceability between the Test Basis and Test Work Products), as well as exit criteria (or definition of done) which will be used during test monitoring and control. Test plans are described in section 5.2, Test Planning and Estimation.</p><p><strong>Test monitoring and control work products.</strong></p><p>Test monitoring and control work products typically include various types of test reports, including test progress reports (produced on an ongoing and/or a regular basis) and test summary reports (produced at various completion milestones). All test reports should provide audience-relevant details about the test progress as of the date of the report, including summarizing the test execution results once those become available.</p><p>Test monitoring and control work products should also address project management concerns, such as task completion, resource allocation and usage, and effort.</p><p>Test monitoring and control, and the work products created during these activities, are further explained in section 5.3, Test Monitoring and Control, of this syllabus.</p><p><strong>Test analysis work products.</strong></p><p>Test analysis work products include defined and prioritized test conditions, each of which is ideally bidirectionally traceable to the specific element(s) of the test basis it covers. For exploratory testing, test analysis may involve the creation of test charters. Test analysis may also result in the discovery and reporting of defects in the test basis.</p><p><strong>Test design work products.</strong></p><p>Test design results in test cases and sets of test cases to exercise the test conditions defined in test analysis. It is often a good practice to design high-level test cases, without concrete values for input data and expected results. Such high-level test cases are reusable across multiple test cycles with different concrete data, while still adequately documenting the scope of the test case. Ideally, each test case is bidirectionally traceable to the test condition(s) it covers.</p><p>Test design also results in the design and/or identification of the necessary test data, the design of the test environment, and the identification of infrastructure and tools, though the extent to which these results are documented varies significantly.</p><p>Test conditions defined in test analysis may be further refined in test design.</p><p><strong>Test implementation work products.</strong></p><p>Test implementation work products include:</p><ul><li>Test procedures and the sequencing of those test procedures;</li><li>Test suites;</li><li>A test execution schedule.</li></ul><p>Ideally, once test implementation is complete, achievement of coverage criteria established in the test plan can be demonstrated via bi-directional traceability between test procedures and specific elements of the test basis, through the test cases and test conditions.</p><p>In some cases, test implementation involves creating work products using or used by tools, such as service virtualization and automated test scripts. Test implementation also may result in the creation and verification of test data and the test environment.</p><p>The completeness of the documentation of the data and/or environment verification results may vary significantly.</p><p>The test data serve to assign concrete values to the inputs and expected results of test cases. Such concrete values, together with explicit directions about the use of the concrete values, turn high-level test cases into executable low-level test cases. The same high-level test case may use different test data when executed on different releases of the test object. The concrete expected results which are associated with concrete test data are identified by using a test oracle.</p><p>In exploratory testing, some test design and implementation work products may be created during test execution, though the extent to which exploratory tests (and their traceability to specific elements of the test basis) are documented may vary significantly.</p><p>Test conditions defined in test analysis may be further refined in test implementation.</p><p><strong>Test execution work products.</strong></p><p>Test execution work products include:</p><ul><li>Documentation of the status of individual test cases or test procedures (e.g., ready to run, pass, fail, blocked, deliberately skipped, etc.).</li><li>Defect reports (see section 5.6, Defect Management).</li><li>Documentation about which test item (or items), test object (or objects), test tools, and testware were involved in the testing.</li></ul><p>Ideally, once test execution is complete, the status of each element of the test basis can be determined and reported via bi-directional traceability with the associated the test procedure (or procedures). For example, we can say which requirements have passed all planned tests, which requirements have failed tests and/or have defects associated with them, and which requirements have planned tests still waiting to be run. This enables verification that the coverage criteria have been met, and enables the reporting of test results in terms that are understandable to stakeholders.</p><p><strong>Test completion work products.</strong></p><p>Test completion work products include test summary reports, action items for improvement of subsequent projects or iterations (e.g., following a project Agile retrospective), change requests or product backlog items, and finalized testware.</p><h4>1.4.4 Traceability between the Test Basis and Test Work Products</h4><p>As mentioned in section 1.4.3, Test Work Products, test work products and the names of those work products vary significantly. Regardless of these variations, in order to implement effective test monitoring and control, it is important to establish and maintain traceability throughout the test process between each element of the test basis and the various test work products associated with that element, as described above. In addition to the evaluation of test coverage, good traceability supports:</p><ul><li>Analyzing the impact of changes.</li><li>Making testing auditable.</li><li>Meeting IT governance criteria.</li><li>Improving the understandability of test progress reports and test summary reports to include the status of elements of the test basis (e.g., requirements that passed their tests, requirements that failed their tests, and requirements that have pending tests).</li><li>Relating the technical aspects of testing to stakeholders in terms that they can understand.</li><li>Providing information to assess product quality, process capability, and project progress against business goals.</li></ul><p>Some test management tools provide test work product models that match part or all of the test work products outlined in this section. Some organizations build their own management systems to organize the work products and provide the information traceability they require.</p><h3>1.5 The Psychology of Testing</h3><p>Software development, including software testing, involves human beings. Therefore, human psychology has important effects on software testing.</p><h4>1.5.1 Human Psychology and Testing</h4><p>Identifying defects during a static test such as a requirements review or user story refinement session, or identifying failures during dynamic test execution, may be perceived as criticism of the product and of its author. An element of human psychology called confirmation bias can make it difficult to accept information that disagrees with currently held beliefs. For example, since developers expect their code to be correct, they have a confirmation bias that makes it difficult to accept that the code is incorrect. In addition to confirmation bias, other cognitive biases may make it difficult for people to understand or accept information produced by testing. Further, it is a common human trait to blame the bearer of bad news, and information produced by testing often contains bad news.</p><p>As a result of these psychological factors, some people may perceive testing as a destructive activity, even though it contributes greatly to project progress and product quality (see sections 1.1, What is Testing?,and 1.2, Why is Testing Necessary?). To try to reduce these perceptions, information about defects and failures should be communicated in a constructive way. This way, tensions between the testers and the analysts, product owners, designers, and developers can be reduced. This applies during both static and dynamic testing.</p><p>Testers and test managers need to have good interpersonal skills to be able to communicate effectively about defects, failures, test results, test progress, and risks, and to build positive relationships with colleagues.</p><p>Ways to communicate well include the following examples:</p><ul><li>Start with collaboration rather than battles. Remind everyone of the common goal of better quality systems.</li><li>Emphasize the benefits of testing. For example, for the authors, defect information can help them improve their work products and their skills. For the organization, defects found and fixed during testing will save time and money and reduce overall risk to product quality.</li><li>Communicate test results and other findings in a neutral, fact-focused way without criticizing the person who created the defective item. Write objective and factual defect reports and review findings.</li><li>Try to understand how the other person feels and the reasons they may react negatively to the information.</li><li>Confirm that the other person has understood what has been said and vice versa.</li></ul><p>Typical test objectives were discussed earlier (see section 1.1, What is Testing). Clearly defining the right set of test objectives has important psychological implications. Most people tend to align their plans and behaviors with the objectives set by the team, management, and other stakeholders. It is also important that testers adhere to these objectives with minimal personal bias.</p><h4>1.5.2 Tester’s and Developer’s Mindsets</h4><p>Developers and testers often think differently. The primary objective of development is to design and build a product. As discussed earlier, the objectives of testing include verifying and validating the product, finding defects prior to release, and so forth. These are different sets of objectives which require different mindsets. Bringing these mindsets together helps to achieve a higher level of product quality.</p><p>A mindset reflects an individual’s assumptions and preferred methods for decision making and problemsolving. A tester’s mindset should include curiosity, professional pessimism, a critical eye, attention to detail, and a motivation for good and positive communications and relationships. A tester’s mindset tends to grow and mature as the tester gains experience.</p><p>A developer’s mindset may include some of the elements of a tester’s mindset, but successful developers are often more interested in designing and building solutions than in contemplating what might be wrong with those solutions. In addition, confirmation bias makes it difficult to find mistakes in their own work.</p><p>With the right mindset, developers are able to test their own code. Different software development lifecycle models often have different ways of organizing the testers and test activities. Having some of the test activities done by independent testers increases defect detection effectiveness, which is particularly important for large, complex, or safety-critical systems. Independent testers bring a perspective which is different than that of the work product authors (i.e., business analysts, product owners, designers, and programmers), since they have different cognitive biases from the authors.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=526e7cc7db4c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[If you can’t take the heat, stay out of the kitchen]]></title>
            <link>https://medium.com/@HugoSaxTavares/if-you-cant-take-the-heat-stay-out-of-the-kitchen-4c117b4c1f6?source=rss-4bf118ee381a------2</link>
            <guid isPermaLink="false">https://medium.com/p/4c117b4c1f6</guid>
            <category><![CDATA[documentary]]></category>
            <category><![CDATA[fia]]></category>
            <category><![CDATA[netflix]]></category>
            <category><![CDATA[formula-1]]></category>
            <category><![CDATA[f1]]></category>
            <dc:creator><![CDATA[Hugo Bandeira Tavares]]></dc:creator>
            <pubDate>Thu, 14 Mar 2019 01:26:31 GMT</pubDate>
            <atom:updated>2019-03-14T02:18:03.419Z</atom:updated>
            <content:encoded><![CDATA[<p>The 4th episode of Netflix’s new docuseries “Formula 1: Drive to Survive” starts with an incisive remark from Christian Horner, team principal of Red Bull Racing. And I could not agree more with this old fox, because Formula 1 is not a sport for the faint hearted, neither for the ones who lack the stamina and commitment.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FwtJPe1ksS6E%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DwtJPe1ksS6E&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FwtJPe1ksS6E%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/fac66bf9215c2787ab7ef9c0bb5363de/href">https://medium.com/media/fac66bf9215c2787ab7ef9c0bb5363de/href</a></iframe><p>With the Formula 1 World Championship about to start in a matter of a week, as a common watcher, with a long lasting passion for Formula 1, and who has keenly interested in the season race after race, when I got home from work today and switched on the TV to relax I was expecting to get hooked to Netflix tonight… but, oh dear, they just released something new and it was about the thing I dread the most every other weekend.</p><p>Of course, the millionaire competition with all that surrounds it is the main dish of the docuseries, with its obviously fundamental and infamous ingredient, the drivers themselves. Yet, as anyone can understand, there is too many things going on that you will have to watch a second time (or a third even). Anyways: it’s the kind of binge watch worthy show Netflix has used the fans, with a lot of spice, drama, tension, humor, joy, and all of what comes with the F1 brand.</p><h3>A tale of competing engines</h3><p>Red Bull Racing versus Renault Sport controversy has been around for the past years. We saw Christian Horner and Cyril Abiteboul exchanging remarks several times, and Cyril replying back in the same coin (and with his contempt-ish smile). Their battles on and off the cameras always have that essence of humor that hate-love relations have, because these are two very high profile, obstinate fearless leaders, who speak irony as their second language and that is a perfect mix to spark some of the most iconic moments of the season.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*p__Nn1Z6p29z7K86xbDy7w.jpeg" /><figcaption>Cyril Abiteboul and Christian Horner — Photo by Grand Prix 247</figcaption></figure><p>Truth be said: Cyril is the man responsible for raising Renault Sport back from the ashes. And that doesn’t leave him a lot of room, especially if that room means selling engines to a competitor on the grid, and a competitor who’s right above Renault in the results.</p><p>On the other hand, I’m personally invested to see what kind of success Honda is helping to Red Bull to forge in 2019 season. The experience we saw with Toro Rosso was quite captivating in the first rounds of 2018 but by the second half of the season, all that magic dust went away, with reliability and performance of the whole block jeopardising the Italian team’s results.</p><p>This year’s winter testing went well for RedBull, as it went for Toro Rosso last year, in regards to engine performance and reliability, with the team complaining of gear box issues. Only time will tell.</p><p>Needless to say, and you all can guess: the aftermath of this RedBull vs. Renault war will be dictated this season.</p><h3>Daniel Ricciardo vs. Max Verstappen dispute</h3><p>At a given time, in episode 4 “The Art of War”, Daniel Ricciardo even comments out loud that he is leaving enough space for Max Verstappen. Don’t get me wrong: Max is definitely the best driver of his generation, but who would be comfortable with a kid with his competitiveness edge and all that ice cold blood in his own team? I wouldn’t be, for sure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6hz7J6vyefZ2_9lJIDbdhg.jpeg" /><figcaption>Max Verstappen and Daniel Ricciardo — Photo by Red Bull</figcaption></figure><p>Ricciardo is the all-charismatic, easy going, huge smile, honey badger who is able to show his teeth and grab a fight whenever needed. Yet what we saw here was a complete lack of support from Red Bull Racing (and I would dare to say from Christian Horner), who swiftly changed their chips for Verstappen right before the middle of the season.</p><p>No wonder why Ricciardo, with a lot of drive, wouldn’t dodge the ball and chase another and more ambitious deal with, surprise, surprise, Renault Sport.</p><p>This chapter is as wide open as it can be, and I’m looking forward for the next episodes. Even more when they — Ricciardo, Hulkenberg, and Renault Sport — adopted a low-key profile during Winter testing. Believe me: I bet this year we will see a lot being written on media, blogs, and newspapers.</p><h3>Like father, like son.</h3><p>Yes, Carlos Sainz Senior is one of the tycoons of world car racing. And yes: his son, Carlos Sainz Junior, may have some times leveraged his driving career thanks to his good dad’s advice and some supervision, I bet. But no, Sainz Jr. wasn’t granted any lamp genie’s wish just because he was soon to this magnificent driver as Sainz Sr.: if something is clear throughout the docuseries, is that they have a pretty normal father-soon relationship, were Sainz Sr. wants to “be invisible” in a few situations — possibly because he is afraid of eclipsing is own soon’s success— and Sainz Jr. going fully on his own.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/830/1*2iQRd6_aeS1QyXwQk9iaSg.jpeg" /><figcaption>Carlos Sainz Sr. and Carlos Sainz Jr. — Photo by MostReliableCars.com</figcaption></figure><p>I got to be honest: at the beginning, I was not expecting much coming from Carlos Sainz Jr., yet the guy makes deliberately makes Formula 1 racing his own business, apart from his father. And he deserves a lot of credit for that: he definitely did not get there for his father’s legacy or his looks, but for the sake of his own sacrifice.</p><h3>The champion is leaving</h3><p>Alonso decided to leave Formula 1. The spaniard may not have left for good, but while he was running, he was <em>allegedly</em> calling the shots in Surrey. Or wherever the team was running.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LblZpHgXCfOB9Lu97qI1Bw.jpeg" /><figcaption>Fernando Alonso — Photo by Fox Sports</figcaption></figure><p>The competitive drive of this man is huge, as it is his ego. No wonders: whilst driving for Renault he won two Formula 1 world championships, bringing the team behind. So, of course, you cannot mess with the man because he is not only the driver: he is a f-ck-ng institution. Eric Boullier may have tried to and he ended up paying the bill.</p><p>Can we expect him back in 2020? Well, for a fact he is not that far away from McLaren, yet the docuseries does not speculate around it, although I believe they should (:devilface:).</p><h3>Williams and Lawrence Stroll convenience marriage</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/725/1*fvos5razxMTTvXfOJ1aiHA.jpeg" /><figcaption>Claire Williams — Photo by ©XPB</figcaption></figure><p>Claire Williams inherited the worst career plan ever: saving the most prolific and awarded team in Formula 1 from a slow and painful death. Truth is — and I say this with great sadness, since Williams was, is and always be in the heart of every Formula 1 knowledgeable fan— that this private team is light-years away from the team they were when Fangio, Hill, Senna, and Schumacher were they top contenders.</p><p>To keep up with the pace, she had to manage a deal with Lawrence Stroll, who in turn brought his son, Lance Stroll. Although a big petrolhead, Stroll — the father — is better used to the management of the clothing business. Let’s see if can do with Sport Pesa Racing. the same he did with Tommy Hilfiger.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/725/1*OGtiqbd2pWqNmrG4fh3wrg.jpeg" /><figcaption>Lawrence Stroll and Lance Stroll — Photo by ©XPB</figcaption></figure><p>One thing we can be assured: Claire Williams is trying her best to keep up with the legacy her dad left.</p><p>And she’s not done with the fight.</p><h3>LeClerc, Gasly, Grosjean, et al: Formula 1 wouldn’t be the same without them</h3><p>Thanks to Drive to Survive, we learn the bounds between Charles LeClerc and Pierre Gasly, the ties between Charles LeClerc and Jules Bianchi, De Haas’s Grosjean despairs and homecoming, etc., etc., etc.,… all of them without whom the Formula 1 championship wouldn’t definitely be what it is right now, they have their time. Yet not as spicy as the fights we’ve saw between constructors (namely RedBull vs. Renault) and the RedBull’s boys controversy, they are all key to the competition (or lack of it, some of the times) and for keeping the duels in the middle field running.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*W8tqfZYgkVGpgTqY7TO2Vg.jpeg" /><figcaption>F1 2018 drivers line up — Photo by Sutton Images</figcaption></figure><p>Anyone can watch Ferrari, Mercedes and Red Bull winning races countless times, but if it was not for these guys who rarely make the podium every single fan of F1 would simple turn off the TV or swap channels for the latest episode of Shark Tank.</p><h3>And the big guys?</h3><p>Out of the picture, and for the time being — in the case of this docuseries it means: until the season renewal — , we missed our favorite iceman Kimi Raikonen — now back to his home squad of Sauber, errrm…, Alfa Romeo, I mean— , the super-tactical Sebastian Vettel, the highly committed Valteri Bottas, and the 5-time-world-champion, Lewis Hamilton… but also the seasoned torpedo man Robert Kubica.</p><p>The last season’s fantastic four from Secuderia Ferrari and Mercerdes AMG F1 are promised for a debut on next season of Drive to Survive (at least there are some rumours about an eventual 2nd season), and we’ll be here waiting for them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*81avTRSkKDsjmKr67VsYPQ.jpeg" /><figcaption>Bottas, Hamilton, Raikkonen, and Vettel — Photo by LAT Images</figcaption></figure><p>And for Kubica, who has a hell of a story in and out Formula 1, particularly for this past 8 years, whilst he longed to come back — but most of all: he longed to feel happy every single morning. For a man who was regarded by Fernando Alonso one of the greatest drivers of his time, there’s is still a lot more to see. And I sincerely hope to see him back to shake things up… a lot!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Bl-hbSjMOHjA7SDzs8GuNA.jpeg" /><figcaption>Robert Kubica — Photo by Radio Renascença</figcaption></figure><p>Enough for tonight.</p><p>F1’s new season is about to start in about 24 hours, and I’m keene on to start watching what teams brought to Albert Park next Friday, a 6AM GMT.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4c117b4c1f6" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>