<?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 Deyvis Ferreira on Medium]]></title>
        <description><![CDATA[Stories by Deyvis Ferreira on Medium]]></description>
        <link>https://medium.com/@deyvisrf?source=rss-eaf4f990334f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*hQEgoLH6CRmKjvjRyv21og.jpeg</url>
            <title>Stories by Deyvis Ferreira on Medium</title>
            <link>https://medium.com/@deyvisrf?source=rss-eaf4f990334f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 14:30:58 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@deyvisrf/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[How to Leverage Bugs to Boost Delivery Quality]]></title>
            <link>https://medium.com/@deyvisrf/how-to-leverage-bugs-to-boost-delivery-quality-5d8bec3c422b?source=rss-eaf4f990334f------2</link>
            <guid isPermaLink="false">https://medium.com/p/5d8bec3c422b</guid>
            <dc:creator><![CDATA[Deyvis Ferreira]]></dc:creator>
            <pubDate>Mon, 17 Feb 2025 15:17:23 GMT</pubDate>
            <atom:updated>2025-02-17T15:20:51.504Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*it5g8v5wbLr0Nls6i1Rnrg.png" /></figure><p>One of the biggest pain points for any squad is dealing with bugs. But what many fail to realize is that bugs are more than just problems — they’re valuable sources of information to improve software quality.<br>Why Measure Delivery Quality?</p><p>Measuring delivery quality is essential to understanding what’s working and what’s not. This goes beyond simply counting the number of bugs; it’s about identifying patterns and learning from them. Teams that focus solely on “delivering fast” often overlook quality, which can lead to issues like:</p><ul><li>Frequent rework to fix errors.</li><li>Bugs reaching production and impacting users.</li><li>Loss of trust between the team and POs/PMs.</li></ul><p>By measuring delivery quality, you can pinpoint bottlenecks and areas for improvement. This enables your team to work more efficiently and deliver a better product.</p><p><strong>Root Cause Focus: Tackling the Real Problem</strong><br>Once you’ve identified bugs (whether in development or production), the next step is to understand their root cause. This is crucial because fixing only the symptoms is like mopping up a wet floor without addressing the leak — the problem will keep coming back.<br>By addressing the root cause, you solve the issue for good, saving time and resources in the long run.</p><p>Here are some common root cause categories that can guide you:</p><ul><li><strong>Code Errors</strong>: Issues directly tied to development, such as incorrect logic, improper use of methods, or mishandling of data.</li><li><em>Example</em>: A function returns unexpected values due to a flaw in the algorithm.</li><li><strong>Missing or Incomplete Specifications</strong>: Bugs arising from poorly defined or incomplete requirements.</li><li><em>Example</em>: A feature behaves differently than expected because the description was unclear.</li><li><strong>Layout Issues</strong>: User interface problems like misaligned elements, inappropriate colors, or device incompatibility.</li><li><em>Example</em>: Buttons not displaying properly on smaller screens.</li><li><strong>Insufficient Unit Testing</strong>: Bugs that could have been caught during testing but slipped through due to inadequate coverage or poorly designed scenarios.</li><li><em>Example</em>: An untested edge case causes a failure in production.</li></ul><p>Categorizing bugs this way helps you identify patterns and prioritize improvements. A simple chart can reveal which categories are most frequent and where to focus your efforts.</p><p><strong>Using Metrics to Empower Your Team</strong><br>Now that you’ve gathered data, it’s time to share it with your team.<br>Here are a few suggestions:</p><ul><li><strong>Regular Feedback</strong>: Present the data during retrospectives with a focus on learning and continuous improvement — not assigning blame.</li><li><strong>Targeted Training</strong>: If many bugs fall into a specific category, like code logic, consider organizing training sessions or pair programming to build the necessary skills.</li><li><strong>Process Adjustments</strong>: Use the insights to refine internal processes. For instance, if requirement-related defects are common, allocate more time to refining user stories.</li><li><strong>Test Automation</strong>: If manual testing misses critical bugs, consider automating key scenarios to improve coverage and reduce errors.</li><li><strong>Celebrate Wins</strong>: When the metrics show improvement, celebrate with the team! Recognizing progress keeps everyone motivated to continue prioritizing quality.</li></ul><p>Measuring delivery quality and categorizing bugs by root cause isn’t about finding fault; it’s about uncovering opportunities for growth. By paying close attention to the data and fostering a collaborative approach, your squad can turn challenges into learning experiences and consistently deliver better software.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d8bec3c422b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Executando testes de UI em paralelo com fastlane e XCUITest]]></title>
            <link>https://medium.com/assertqualityassurance/executando-testes-de-ui-em-paralelo-com-fastlane-e-xctest-b1c1fba196dd?source=rss-eaf4f990334f------2</link>
            <guid isPermaLink="false">https://medium.com/p/b1c1fba196dd</guid>
            <category><![CDATA[test]]></category>
            <category><![CDATA[test-automation]]></category>
            <category><![CDATA[qa]]></category>
            <category><![CDATA[ios]]></category>
            <dc:creator><![CDATA[Deyvis Ferreira]]></dc:creator>
            <pubDate>Tue, 27 Feb 2018 16:53:27 GMT</pubDate>
            <atom:updated>2020-06-17T14:54:36.562Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/871/1*UchIRfbd6orknkV4FZAwTw.png" /></figure><p>Opa!!! blz??</p><p>Uma perguntinha marota:</p><p>Quanto tempo demora a execução dos seus testes de UI?</p><p>Em geral são testes que demoram muuuuuuuuiiiiiiitooooooooooo (dependendo do seu projeto, de quantos cenários você tem, etc). E foi pensando nisso que comecei a pesquisar algumas maneiras de fazer com que meus testes de UI fossem rápidos ou pelo menos que caíssem pela metade do tempo. Então, Eureka!!! Descobri que era possível executa-los em paralelo, ou seja, rodar os testes em vários simuladores ao mesmo tempo!! =)</p><p>Irei dividir esse artigo em duas partes OK?</p><p>Parte 1 — Rodar o mesmo teste em vários simuladores <strong>(importante para validar layout)</strong></p><p>Parte 2 — Dividir os testes e rodar em vários simuladores</p><h3>QA, já ouviu falar do fastlane?</h3><p>“fastlane é uma plataforma de código aberto destinada a simplificar a implantação de Android e iOS. O fastlane permite automatizar todos os aspectos do seu desenvolvimento e liberar o fluxo de trabalho”</p><p>Ele tem inúmeras vantagens e você pode dar uma olhada depois <a href="https://docs.fastlane.tools/">https://docs.fastlane.tools/</a></p><p>Existem algumas outras formas de rodar os testes em paralelo, mas foi essa que (na minha opinião) achei mais organizada, com relatórios e tudo que o QA tem direito.</p><h3>Preparando o ambiente</h3><p>Vou me basear no meu projeto do <strong>GitHub</strong> blz? Dá uma olhada <a href="https://github.com/deyvisrf/app"><strong>AQUI</strong></a> depois. Estou usando um<strong> Mac OS.</strong></p><ul><li>Com a versão do Ruby mais recente, execute no terminal:</li></ul><p><em>sudo gem install fastlane</em></p><ul><li>Navegue até o diretório do seu projeto e execute:</li></ul><p><em>fastlane init</em></p><ul><li>Procure por pelo arquivo <strong><em>fastlane/Fastfile</em></strong> e abra-o com Atom, Sublime Text ou outra IDE de sua preferência</li><li>Vamos usar o <strong>scan</strong> (<a href="https://docs.fastlane.tools/actions/scan/#scan">https://docs.fastlane.tools/actions/scan/#scan</a>) para rodar os testes em múltiplus simuladores</li></ul><p><em>scan(<br> workspace: “Example.xcworkspace”,<br> devices: [“iPhone 6s”, “iPad Air”]<br>)</em></p><p><strong>Ficará assim:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/949/0*_HMnHGcGC2Yowy79.png" /><figcaption>TESTES EM PARALELO COM XCTESTUI E FASTLANE</figcaption></figure><h3>Run tests</h3><p>E finalmente execute os testes nos simuladores iPhone 5s, iPhone 6 e iPhone 7 com:</p><p><em>fastlane ui_test</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*1prledAVv18YvizGdKHd_g.gif" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*NyJ6JzCeFfZoU7xn6U9iKA.gif" /></figure><p>Obs.: Execute esse comando dentro do diretório do seu projeto. No nosso caso em <strong>/app/eats</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b1c1fba196dd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/assertqualityassurance/executando-testes-de-ui-em-paralelo-com-fastlane-e-xctest-b1c1fba196dd">Executando testes de UI em paralelo com fastlane e XCUITest</a> was originally published in <a href="https://medium.com/assertqualityassurance">assert(QA)</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Automação UI com XCUITest]]></title>
            <link>https://medium.com/@deyvisrf/automa%C3%A7%C3%A3o-ui-com-xctest-1c39a8e01a2f?source=rss-eaf4f990334f------2</link>
            <guid isPermaLink="false">https://medium.com/p/1c39a8e01a2f</guid>
            <category><![CDATA[automation-tools]]></category>
            <category><![CDATA[qa]]></category>
            <category><![CDATA[automation-testing]]></category>
            <dc:creator><![CDATA[Deyvis Ferreira]]></dc:creator>
            <pubDate>Mon, 15 Jan 2018 10:15:37 GMT</pubDate>
            <atom:updated>2020-06-17T14:54:22.999Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*4tRkhObDBtmz-c0r.jpg" /></figure><p>Todos sabem a importância de criar testes automatizados ao longo do desenvolvimento, para ajudar nos testes de regressão e evolução do produto.</p><p>Nesse artigo quero contar um pouco da minha experiência com um <em>framework</em> que venho trabalhando. <strong>XCTest!</strong></p><p>Ele está integrado com o XCode e funciona de maneira rápida utilizando Swift. Possui uma opção de Recording, que podemos usar para simular o comportamento do cenário a ser testado e simultaneamente o código é gerado no <strong>XCode</strong>, mapeando textos, id’s etc.</p><p>Claro a gravação ajuda muito, mas para alguns cenários de testes que precisam de uma validação mais complexa, precisamos<strong> codar</strong> mesmo. Penso que a nossa profissão esta mudando, ao ponto de termos QA`s que tambem são Dev`s, pensem no quanto esse profissional poderá agregar na qualidade de um produto, mas esse é um tema para um próximo post =)</p><p><strong>Alguns comandos básicos:</strong></p><p>Define a execução do aplicativo com uma variável fixa chamada <strong>app</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/213/0*7extVpugLJdDeeZD.png" /></figure><p>Pressiona o botão de nome Entrar (o “.tap()” simula o clique)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/210/0*yLOHJl2P1K-_aJRe.png" /></figure><p>Clica no primeiro campo localizado na tela</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*EIuzsMRA-ceHotG_.png" /></figure><p>Insere um texto no campo</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/223/0*4whqD3TuH5iu8tJR.png" /></figure><p>Valida se o texto existe na tela.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/282/0*o-jEWZeB3WL091N5.png" /></figure><p><strong>Vantagens:</strong></p><ul><li>Swift é uma linguagem fácil de aprender</li><li>É uma ferramenta nativa iOS</li><li>Rápida execução dos testes de UI</li><li>Maior interação com os Devs</li><li>Todo o time desenvolvendo na mesma linguagem</li><li>Contato com mesmo código que o time</li><li>Ajuda do time em caso de dúvidas</li><li>Aprendizado com o time</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c39a8e01a2f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>