<?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 Davison Alves da Silva on Medium]]></title>
        <description><![CDATA[Stories by Davison Alves da Silva on Medium]]></description>
        <link>https://medium.com/@davisonalves?source=rss-5650121f6d02------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*FM4eeuYBvHLFuWyCAEXp5w.jpeg</url>
            <title>Stories by Davison Alves da Silva on Medium</title>
            <link>https://medium.com/@davisonalves?source=rss-5650121f6d02------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 06:21:30 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@davisonalves/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[Introduction to Automated Testing with C#]]></title>
            <link>https://medium.com/@davisonalves/introduction-to-automated-testing-with-c-06fa5dbf833e?source=rss-5650121f6d02------2</link>
            <guid isPermaLink="false">https://medium.com/p/06fa5dbf833e</guid>
            <category><![CDATA[dotnet]]></category>
            <category><![CDATA[qa]]></category>
            <category><![CDATA[test-automation]]></category>
            <category><![CDATA[csharp]]></category>
            <dc:creator><![CDATA[Davison Alves da Silva]]></dc:creator>
            <pubDate>Wed, 06 Dec 2023 00:33:34 GMT</pubDate>
            <atom:updated>2023-12-08T14:49:36.210Z</atom:updated>
            <content:encoded><![CDATA[<p>Working on a project that uses C# and looking to automate your tests? If yes, take a look at this article.</p><p>Let’s start with a quick definition of automated tests: they are powerful tools that save us time by providing quick feedback on the state of tested functionalities, reducing the time spent on manual tests.</p><h4>Which levels of tests can we automate?</h4><p>Now that we understand what automated tests are, let’s talk about the test levels. We have component tests (or unit tests), integration tests, system tests, and acceptance tests (performed by end-users or client representatives).</p><p>For us, developers and QA’s, we have unit, integration, and system tests. Unit tests validate small parts of the system, such as methods and functions. Integration tests verify how these units integrate, and system tests evaluate the system as a whole.</p><p>Usually, API tests are our integration tests, while tests dealing with the graphical interface (UI) are the system tests. The common division of work is:</p><ul><li>Developers =&gt; Unit Tests</li><li>QA =&gt; Integration Tests</li><li>QA =&gt; System Tests</li></ul><p>Of course, this division is just an example and can vary depending on the project.</p><h4>Which tools can we use to automate tests?</h4><p>Now that we understand the test levels, let’s see the tools that can help us with automated testing in C#.</p><p>For unit tests, the most popular ones are:</p><ul><li><a href="https://xunit.net/">Xunit</a></li><li><a href="https://nunit.org/">Nunit</a></li><li><a href="https://learn.microsoft.com/en-us/dotnet/core/testing/unit-testing-with-mstest">MSTest</a></li></ul><p>They offer annotations to mark our test methods and assertions to validate our results.</p><p>For integration tests or APIs, we need a tool for unit tests and another to make requests. <a href="https://restsharp.dev/">Restsharp</a> is common, but there’s a tool developed especially for API tests, <a href="https://github.com/basdijkstra/rest-assured-net/wiki/Usage-Guide">RestAssured.Net.</a></p><p>Finally, for system tests, we have options like:</p><ul><li><a href="https://www.selenium.dev/documentation/webdriver/getting_started/">Selenium</a></li><li><a href="https://playwright.dev/">Plawright</a></li><li><a href="https://github.com/appium/appium">Appium</a> (for mobile tests)</li></ul><p>Remember, these tools cater to various programming languages, including C#. When checking the documentation, choose Csharp or .NET to see the relevant examples.</p><p>Thank you for reading! In the next articles, we’ll address these topics in a more practical manner.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=06fa5dbf833e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Simplifying Cypress Configurations: Farewell /// <reference types= ‘cypress’>]]></title>
            <link>https://medium.com/@davisonalves/abandone-reference-types-cypress-no-topo-dos-seus-arquivos-de-teste-com-cypress-5c4fe096ea7e?source=rss-5650121f6d02------2</link>
            <guid isPermaLink="false">https://medium.com/p/5c4fe096ea7e</guid>
            <category><![CDATA[e2e-testing]]></category>
            <category><![CDATA[cypress]]></category>
            <category><![CDATA[test-automation]]></category>
            <category><![CDATA[qa]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Davison Alves da Silva]]></dc:creator>
            <pubDate>Thu, 19 Jan 2023 13:29:29 GMT</pubDate>
            <atom:updated>2023-12-01T15:14:17.056Z</atom:updated>
            <content:encoded><![CDATA[<p>It’s common to find the code snippet “/// &lt;reference types= ‘cypress’&gt;” at the beginning of Cypress test files in many test automation projects. This pattern provides code suggestions and usage examples in VSCode, as illustrated in the image below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*CAk2oDDzxst5T1fyvy9ZoA.png" /><figcaption>Screenshot — Code Suggestions</figcaption></figure><p>While highly beneficial, the need to add this snippet to every new file can be somewhat impractical. If you resonate with this viewpoint, a suggested solution is to create a “jsconfig.json” file at the root of your project and include the following content:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/18b98599722fb7a248c624e032a669cf/href">https://medium.com/media/18b98599722fb7a248c624e032a669cf/href</a></iframe><p>Para aprender mais, consulte a aba de ferramentas da <a href="https://docs.cypress.io/guides/tooling/IDE-integration">documentação do Cypress</a> de onde peguei essa dica e também entenda melhor sobre o que é o arquivo “jsconfig.json” <a href="https://code.visualstudio.com/docs/languages/jsconfig">aqui</a>.</p><p>This approach allows for maintaining code suggestions and examples while eliminating the manual addition of “/// &lt;reference…” in each new file.</p><p>If you wish to delve deeper into this topic, I recommend referring to the tools section in the Cypress documentation, where I found this tip. Additionally, you can learn more about the “jsconfig.json” file <a href="https://docs.cypress.io/guides/tooling/IDE-integration">IDE Integration | Cypress Documentation</a>.</p><p>This practice can streamline your workflow and simplify the maintenance of test files in Cypress, offering a more efficient organization.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5c4fe096ea7e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Customizing Allure Reports in Cypress with Environment Details]]></title>
            <link>https://medium.com/@davisonalves/exibindo-informa%C3%A7%C3%B5es-de-ambiente-nos-relat%C3%B3rios-do-allure-com-cypress-30786548a3e2?source=rss-5650121f6d02------2</link>
            <guid isPermaLink="false">https://medium.com/p/30786548a3e2</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[cypress]]></category>
            <category><![CDATA[qa]]></category>
            <category><![CDATA[test-automation]]></category>
            <category><![CDATA[allure-reporting]]></category>
            <dc:creator><![CDATA[Davison Alves da Silva]]></dc:creator>
            <pubDate>Mon, 09 Jan 2023 20:04:51 GMT</pubDate>
            <atom:updated>2023-12-01T15:05:52.304Z</atom:updated>
            <content:encoded><![CDATA[<p>If you’ve integrated Cypress with Allure reports, you’ve probably noticed that the environment section isn’t automatically populated. If you haven’t integrated yet, this image illustrates what I’m referring to:</p><figure><img alt="Imagem do relatório gerado com allure, destacando a área de environment sem nenhuma informação." src="https://cdn-images-1.medium.com/max/1024/1*YptoTh-SOShLWkE5cyz5hQ.png" /><figcaption>Screenshot — Allure Reports without environment information</figcaption></figure><p>Now, picture a fellow developer looking at your report and asking the following questions:</p><blockquote>In which environment was this test executed? (Staging, Development, Production…) Which browser was used? And in which version? (Chrome, Firefox, Safari…)</blockquote><p>To address this issue, we need to add environment information to Allure reports. Let’s utilize Node.js’s file system module and Cypress’s plugin API to obtain these details.</p><p>Here’s an example code snippet that automatically adds this information:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/0815f92ee85bd89205ace5b1195eeb16/href">https://medium.com/media/0815f92ee85bd89205ace5b1195eeb16/href</a></iframe><p>This code uses the allureWriter module to write environment information to an environment.properties file, including the test execution environment, the used browser, and its version.</p><p>When you open the Allure report after implementing this, the result will be as follows:</p><figure><img alt="Imagem do relatório gerado com allure, destacando a área de environment com as informações de ambiente." src="https://cdn-images-1.medium.com/max/1024/1*lUJijgUs6qa5dqIy9XnuyQ.png" /><figcaption>Screenshot — Allure Reports with environment information</figcaption></figure><blockquote>It’s worth noting that in the provided example, the environment used was “homolog,” and this information was captured from a .env file. Depending on your setup, environment information might be stored elsewhere, so adjust the data capture according to your context.</blockquote><p>This implementation simplifies the view for stakeholders to observe automated tests and identified issues during the project. Liked it? Don’t miss out on exploring other possibilities here!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=30786548a3e2" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>