<?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 Javier Caballero on Medium]]></title>
        <description><![CDATA[Stories by Javier Caballero on Medium]]></description>
        <link>https://medium.com/@caballerojavier?source=rss-279bd029494e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*zfrGKt9oRkFS8AAOCuSBzw.png</url>
            <title>Stories by Javier Caballero on Medium</title>
            <link>https://medium.com/@caballerojavier?source=rss-279bd029494e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 07:27:28 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@caballerojavier/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[Mobile Apps Traceability]]></title>
            <link>https://medium.com/@caballerojavier/mobile-apps-traceability-5f4d8c4a1d54?source=rss-279bd029494e------2</link>
            <guid isPermaLink="false">https://medium.com/p/5f4d8c4a1d54</guid>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[quality-assurance-testing]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[automation-testing]]></category>
            <category><![CDATA[automation-software]]></category>
            <dc:creator><![CDATA[Javier Caballero]]></dc:creator>
            <pubDate>Wed, 26 Jul 2023 17:37:15 GMT</pubDate>
            <atom:updated>2023-07-28T16:51:23.400Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<h2>How to control the traceability when the app and the test are in separate repositories</h2><h3>Introduction</h3><p>From my extensive experience working with mono-repo, I have observed that separating automation tests can cause issues with test synchronization and the system traceability. To solve these problems, I have developed an approach (POC) to creating a strong CI/CD process using GitHub Actions and BrowserStack for an Android app. This process covers a quality focus on building, testing, and releasing apps. However, this approach may only be suitable for some scenarios, and there may be potential drawbacks. Therefore, I encourage you to examine specific cases where this approach may be beneficial or provide feedback on any potential weaknesses in my solution.</p><p>This article aims to comprehensively understand traceability and its various types within the software development lifecycle (SDLC). I will focus the article on traceability in testing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/0*e5t6J2xhncwJstSw" /></figure><h3>Traceability</h3><p>Traceability is the capability to follow and record the entire lifecycle of products, materials, or services, including their history, location, and usage. This involves collecting and documenting data about a product or component&#39;s origin, production, handling, and distribution, enabling quick access to this information at any stage of the supply chain.</p><p>Traceability systems promote transparency and accountability, serving to ensure that products meet regulatory requirements, quality standards, and safety guidelines. They empower companies to detect and resolve issues related to product recalls, quality control, compliance, and sustainability.</p><blockquote>Traceability is like Hansel and Gretel laying a trail of breadcrumbs to be able to know the chosen path.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cEw4ATE00c5Qb-MKBBFYTA.jpeg" /></figure><h3>Traceability Applied to the Software Development Process</h3><p>Traceability is also applicable in the software development process, where it helps establish and maintain links between different artifacts and stages of software development. It enables understanding and managing the relationships between requirements, design elements, code, tests, and other project artifacts.</p><h4>Requirements Traceability</h4><p>Traceability ensures software requirements are properly documented, tracked, and linked throughout the development lifecycle. It allows stakeholders to understand how each requirement is addressed in the design, implementation, and testing phases. By maintaining traceability, changes to requirements can be managed effectively, and the impact of those changes on other parts of the system can be assessed.</p><h4>Design Traceability</h4><p>Traceability helps establish links between the software design artifacts, such as architectural diagrams, component specifications, and interface definitions. This enables developers to track how the design decisions align with the requirements and facilitates the identification of any gaps or inconsistencies.</p><h4>Code Traceability</h4><p>Traceability ensures that the codebase is aligned with the requirements and design specifications. Establishing links between code modules, functions, or classes and the corresponding requirements or design elements makes it easier to understand the rationale behind code implementation, track changes, and assess the impact of modifications.</p><h4>Test Traceability</h4><p>Traceability is essential for test management, allowing testers to track which requirements or design elements are covered by specific tests. It helps ensure that all requirements are adequately tested and provides a basis for evaluating test coverage. Traceability also aids in tracking defects back to their root causes, whether related to requirements, design, or implementation.</p><h4>Change Impact Analysis</h4><p>Traceability provides the ability to assess the impact of changes throughout the software development process. When a requirement or design change occurs, traceability links help identify which other artifacts are affected, enabling project teams to determine the necessary adjustments, estimate the effort required, and make informed decisions regarding the change implementation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/951/1*ZSHD0hfnJHeIJdK0z25A-w.png" /></figure><h3><strong>Benefits of Test Traceability</strong></h3><h4>Requirement Validation</h4><p>Traceability links requirements to test cases, enabling effective validation and verification of requirements. It ensures that all specified features and functionalities are thoroughly tested, reducing the risk of missed requirements.</p><h4>Impact Analysis</h4><p>Test traceability aids in understanding the impact of changes made to requirements or code. By tracing requirements to their corresponding test cases, teams can identify which tests are affected and need to be updated, minimizing the effort required for regression testing.</p><h4>Test Coverage Evaluation</h4><p>With traceability in place, teams can assess the completeness of their test coverage. It helps identify gaps or redundancies in the test suite, ensuring comprehensive testing and reducing the likelihood of critical defects slipping through.</p><h4>Defect Management</h4><p>Traceability links defects to test cases, enabling better tracking and resolution of issues. It helps identify the root cause of defects and provides insights into the quality of the testing process.</p><h3>Implementing the Code Traceability</h3><p>Now that you have a solid theoretical foundation, you have a better grasp of <em>why</em> we are here. However, we still need to figure out <em>how</em> to turn this idea into a reality. To achieve this, we need to outline the context in which we can conceptualize our idea.</p><h4>The APP</h4><p>Let&#39;s imagine that the development team implemented the next branching model:</p><figure><img alt="Git branching model for the mobile app" src="https://cdn-images-1.medium.com/max/841/1*6jTuBzUZ85ZZWdXEWtRHgQ.png" /><figcaption>A successful Git branching model: <a href="https://nvie.com/posts/a-successful-git-branching-model/">https://nvie.com/posts/a-successful-git-branching-model/</a></figcaption></figure><p>We can highlight two main concepts <em>release branch</em> and <em>tags </em>over the main branch:</p><ul><li><strong>Tags: </strong>Tags are primarily used to mark significant points in the project’s history, such as software releases or stable versions. By creating a tag, you’re essentially creating a named reference to a specific commit. This allows you to track and reference specific versions of your codebase easily. Tags are generally immutable and provide a reliable way to identify and access specific points in your project’s history. Unlike branches, which are typically meant for ongoing development and can evolve over time, tags are fixed references that don’t change.</li><li><strong>Release Branch: </strong>A release branch serves as a dedicated branch to prepare and stabilize a specific software release. It allows you to isolate the codebase for the upcoming release from ongoing development work in other branches. This is particularly useful when you must perform rigorous testing, bug fixing, and final adjustments to ensure the release is stable and ready for deployment.</li></ul><blockquote>Unlike branches, which are typically meant for ongoing development and can evolve over time, tags are fixed references that don’t change.</blockquote><h4>The tests</h4><p>Why overthink the automation test organization if we can easily mirror the app branching models? In that way, testers are developers that can stand on the same timeline point.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1001/1*D6bCMJDECgNd8FOTjku-Lw.png" /></figure><h3>Following the APP evolution</h3><p>At this point, each tag on the repository acts like a pointer that helps historians to analyze old behaviors and logic changes. So the tests are the hieroglyphics set in stone that document the application at that point. Therefore, it requires automation tests to be written comprehensively.</p><figure><img alt="Human evolution clipart" src="https://cdn-images-1.medium.com/max/593/0*SQ2Gf_bDkIB1Tu1w.jpg" /></figure><h4>Why are tests better for documenting changes instead of the code?</h4><p>The answer is not straightforward. While code may be effective in certain cases, it can take time to comprehend a complex business rule change or an intricate implementation.</p><p><strong>For example:</strong></p><p>Let’s imagine that the application has an input that accepts youtube URLs, and you implement a function to validate the user input.</p><pre>const youTubeValidator = (value) =&gt; /(?:https?:\/\/)?(?:youtu\.be\/|(?:www\.|m\.)?youtube\.com\/(?:watch|v|embed)(?:\.php)?(?:\?.*v=|\/))([a-zA-Z0-9\_-]+)/.test(value);</pre><p>Then write the tests:</p><pre>describe(&#39;youTubeValidator&#39;, () =&gt; {<br>  test.each([<br>    [&#39;https://www.youtube.com/watch?v=DFYRQ_zQ-gk&amp;feature=featured&#39;],<br>    [&#39;https://www.youtube.com/watch?v=DFYRQ_zQ-gk&#39;],<br>    [&#39;http://www.youtube.com/watch?v=DFYRQ_zQ-gk&#39;],<br>    [&#39;//www.youtube.com/watch?v=DFYRQ_zQ-gk&#39;],<br>    [&#39;www.youtube.com/watch?v=DFYRQ_zQ-gk&#39;],<br>    [&#39;https://youtube.com/watch?v=DFYRQ_zQ-gk&#39;],<br>    [&#39;http://youtube.com/watch?v=DFYRQ_zQ-gk&#39;],<br>    [&#39;//youtube.com/watch?v=DFYRQ_zQ-gk&#39;],<br>    [&#39;youtube.com/watch?v=DFYRQ_zQ-gk&#39;],<br>    [&#39;https://m.youtube.com/watch?v=DFYRQ_zQ-gk&#39;],<br>    [&#39;http://m.youtube.com/watch?v=DFYRQ_zQ-gk&#39;],<br>    [&#39;//m.youtube.com/watch?v=DFYRQ_zQ-gk&#39;],<br>    [&#39;m.youtube.com/watch?v=DFYRQ_zQ-gk&#39;],<br>    [&#39;https://www.youtube.com/v/DFYRQ_zQ-gk?fs=1&amp;hl=en_US&#39;],<br>    [&#39;http://www.youtube.com/v/DFYRQ_zQ-gk?fs=1&amp;hl=en_US&#39;],<br>    [&#39;//www.youtube.com/v/DFYRQ_zQ-gk?fs=1&amp;hl=en_US&#39;],<br>    [&#39;www.youtube.com/v/DFYRQ_zQ-gk?fs=1&amp;hl=en_US&#39;],<br>    [&#39;youtube.com/v/DFYRQ_zQ-gk?fs=1&amp;hl=en_US&#39;],<br>    [&#39;https://www.youtube.com/embed/DFYRQ_zQ-gk?autoplay=1&#39;],<br>    [&#39;https://www.youtube.com/embed/DFYRQ_zQ-gk&#39;],<br>    [&#39;http://www.youtube.com/embed/DFYRQ_zQ-gk&#39;],<br>    [&#39;//www.youtube.com/embed/DFYRQ_zQ-gk&#39;],<br>    [&#39;www.youtube.com/embed/DFYRQ_zQ-gk&#39;],<br>    [&#39;https://youtube.com/embed/DFYRQ_zQ-gk&#39;],<br>    [&#39;http://youtube.com/embed/DFYRQ_zQ-gk&#39;],<br>    [&#39;//youtube.com/embed/DFYRQ_zQ-gk&#39;],<br>    [&#39;youtube.com/embed/DFYRQ_zQ-gk&#39;],<br>    [&#39;https://youtu.be/DFYRQ_zQ-gk?t=120&#39;],<br>    [&#39;https://youtu.be/DFYRQ_zQ-gk&#39;],<br>    [&#39;http://youtu.be/DFYRQ_zQ-gk&#39;],<br>    [&#39;//youtu.be/DFYRQ_zQ-gk&#39;],<br>    [&#39;youtu.be/DFYRQ_zQ-gk&#39;],<br>  ])(&#39;Case %s&#39;,(url) =&gt; {<br>    expect(youTubeValidator(url)).toBeTruthy();<br>  });<br>});</pre><p>But now, YouTube released a new feature YouTube Live. Meaning that valid user inputs with live URLs are going to be rejected. To solve that the dev updates the regex:</p><pre> const youTubeValidator = (value = &#39;&#39;) =&gt; /^((?:https?:)?\/\/)?((?:www|m)\.)?((?:youtube(-nocookie)?\.com|youtu.be))(\/(?:[\w\-]+\?v=|embed\/|live\/|v\/)?)([\w\-]+)(\S+)?$/.test(value);</pre><p>At this point, you’re waiting for the unit tests to understand the new cases where the function works instead of trying to understand that complex regex.</p><p>Here are the new unit tests:</p><pre>describe(&#39;youTubeValidator&#39;, () =&gt; {<br>  test.each([<br>    [&#39;https://www.youtube.com/watch?v=DFYRQ_zQ-gk&amp;feature=featured&#39;],<br>    [&#39;https://www.youtube.com/watch?v=DFYRQ_zQ-gk&#39;],<br>    [&#39;http://www.youtube.com/watch?v=DFYRQ_zQ-gk&#39;],<br>    [&#39;//www.youtube.com/watch?v=DFYRQ_zQ-gk&#39;],<br>    [&#39;www.youtube.com/watch?v=DFYRQ_zQ-gk&#39;],<br>    [&#39;https://youtube.com/watch?v=DFYRQ_zQ-gk&#39;],<br>    [&#39;http://youtube.com/watch?v=DFYRQ_zQ-gk&#39;],<br>    [&#39;//youtube.com/watch?v=DFYRQ_zQ-gk&#39;],<br>    [&#39;youtube.com/watch?v=DFYRQ_zQ-gk&#39;],<br>    [&#39;https://m.youtube.com/watch?v=DFYRQ_zQ-gk&#39;],<br>    [&#39;http://m.youtube.com/watch?v=DFYRQ_zQ-gk&#39;],<br>    [&#39;//m.youtube.com/watch?v=DFYRQ_zQ-gk&#39;],<br>    [&#39;m.youtube.com/watch?v=DFYRQ_zQ-gk&#39;],<br>    [&#39;https://www.youtube.com/v/DFYRQ_zQ-gk?fs=1&amp;hl=en_US&#39;],<br>    [&#39;http://www.youtube.com/v/DFYRQ_zQ-gk?fs=1&amp;hl=en_US&#39;],<br>    [&#39;//www.youtube.com/v/DFYRQ_zQ-gk?fs=1&amp;hl=en_US&#39;],<br>    [&#39;www.youtube.com/v/DFYRQ_zQ-gk?fs=1&amp;hl=en_US&#39;],<br>    [&#39;youtube.com/v/DFYRQ_zQ-gk?fs=1&amp;hl=en_US&#39;],<br>    [&#39;https://www.youtube.com/embed/DFYRQ_zQ-gk?autoplay=1&#39;],<br>    [&#39;https://www.youtube.com/embed/DFYRQ_zQ-gk&#39;],<br>    [&#39;http://www.youtube.com/embed/DFYRQ_zQ-gk&#39;],<br>    [&#39;//www.youtube.com/embed/DFYRQ_zQ-gk&#39;],<br>    [&#39;www.youtube.com/embed/DFYRQ_zQ-gk&#39;],<br>    [&#39;https://youtube.com/embed/DFYRQ_zQ-gk&#39;],<br>    [&#39;http://youtube.com/embed/DFYRQ_zQ-gk&#39;],<br>    [&#39;//youtube.com/embed/DFYRQ_zQ-gk&#39;],<br>    [&#39;youtube.com/embed/DFYRQ_zQ-gk&#39;],<br>    [&#39;https://www.youtube-nocookie.com/embed/DFYRQ_zQ-gk?autoplay=1&#39;], // No cookie valid url<br>    [&#39;https://www.youtube-nocookie.com/embed/DFYRQ_zQ-gk&#39;],<br>    [&#39;http://www.youtube-nocookie.com/embed/DFYRQ_zQ-gk&#39;],<br>    [&#39;//www.youtube-nocookie.com/embed/DFYRQ_zQ-gk&#39;],<br>    [&#39;www.youtube-nocookie.com/embed/DFYRQ_zQ-gk&#39;],<br>    [&#39;https://youtube-nocookie.com/embed/DFYRQ_zQ-gk&#39;],<br>    [&#39;http://youtube-nocookie.com/embed/DFYRQ_zQ-gk&#39;],<br>    [&#39;//youtube-nocookie.com/embed/DFYRQ_zQ-gk&#39;],<br>    [&#39;youtube-nocookie.com/embed/DFYRQ_zQ-gk&#39;],<br>    [&#39;https://youtu.be/DFYRQ_zQ-gk?t=120&#39;],<br>    [&#39;https://youtu.be/DFYRQ_zQ-gk&#39;],<br>    [&#39;http://youtu.be/DFYRQ_zQ-gk&#39;],<br>    [&#39;//youtu.be/DFYRQ_zQ-gk&#39;],<br>    [&#39;youtu.be/DFYRQ_zQ-gk&#39;],<br>    [&#39;https://www.youtube.com/HamdiKickProduction?v=DFYRQ_zQ-gk&#39;],<br>    [&#39;https://www.youtube.com/live/sMbxjePPmkw?feature=share&#39;] // Live URLs<br>  ])(&#39;Case %s&#39;,(url) =&gt; {<br>    expect(youTubeValidator(url)).toBeTruthy();<br>  });<br>});</pre><p>In conclusion, the reader can get a clear idea of the changes by comparing the test differences between the two commits. But requires the commitment to writing test cases for every new behavior.</p><h3>The Synchronization Process</h3><p>Now, you know that there is a need to keep track of everything you do with the application, and the best place to tell the story is the test cases. Let&#39;s talk about the synchronization process that validates the consistency of the development with the existing tests.</p><p>The process is really simple, it starts when the development is finish.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/808/1*lAcBogz_OJrBTCBOULIPtQ.png" /></figure><p>The process requires the app and the tests to have version control and a unified versioning system. Nowadays, almost the entire world uses Git for version control, but for Software Versioning, there are multiple alternatives, I recommend using the popular <a href="https://en.wikipedia.org/wiki/Software_versioning">semantic versioning</a>.</p><p>It is simple to comprehend the idea presented in the preview diagram that a corresponding test version may exist or not for every app version. The tests aid developers in assessing whether the app changes are aligned with the user stories.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/395/1*DHMLxAAofHCTb_gsZCK0HQ.png" /></figure><p>You can customize the process according to your needs. For instance, you can make it mandatory to have tests for the new feature versions but not for hotfixes. These rules help the team keep tests aligned and updated with every app change.</p><h3>Continuous Delivery</h3><p>The presented process looks good in a diagram, so let’s turn the idea into reality using Continuous Delivery.</p><blockquote><strong>Continuous Delivery (CD)</strong> is a software development practice that focuses on ensuring that code changes are automatically built, tested, and prepared for release to production in a reliable and efficient manner. The primary goal of continuous delivery is to shorten the software development cycle, reduce risks, and improve the quality of software releases.</blockquote><p>In such a way, the CD converts a process into code. Being what we’re looking for, making our process easy to implement with minimum maintainability and effort. In my specific case, I have selected <a href="https://github.com/features/actions">GitHub Actions</a> because it’s free and popular, but whatever similar tool of your preference would be okay.</p><h4>App Continuous Delivery</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/804/1*9jH-FHB1UUra0Dt15Hxy6A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DIM4Y_BswgbaIqBmXaJ3kw.png" /></figure><h4>Test Continuous Delivery</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/686/1*0KhB1COee32Uvzwoxuoeiw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nUlkjRyKJ2kr6YetuW1iiA.png" /></figure><p>If you don’t know what <a href="https://docs.docker.com/get-started/">Docker</a> is, think of a software package similar to an apk for Android mobile apps.</p><blockquote><strong>Docker</strong> is an open-source platform that allows you to automate the deployment, scaling, and management of applications using containerization. It provides a way to package software and its dependencies into a standardized unit called a container.</blockquote><p>The flows enforce that the tests need to move at the same speed as the app and place both at the same level. The CD will pick an old version if no tests are available for the feature. Showing that the tests are left behind on the sprint.</p><p>In my career, companies&#39; development process always pulls the tests from the <em>main</em> (old <em>master</em>) branch to check the app at any stage. That results in QA engineers only caring about keeping one stable version of the test, not implementing the branching model, and ignoring the test versioning.</p><p>As a consequence, you’ll lose all the traceability. Tests are turned into pieces of code that only get constantly out-updated, losing its value and potential.</p><p>With the implementation of this Continuous delivery process, testers and the rest of the stakeholders are constantly reminded that the tests should be versioned and updated simultaneously as a new version of the app is intended to be released to keep the traceability. We cannot blame people for forgetting things/processes, this is the nature of entropy.</p><p>If we rely on software to be the guardians and the entropy preventers. We can focus our energy on improving the process instead of keeping it alive.</p><h3>Repositories</h3><p>Here are the example repositories that I made for this article:</p><h4>Application Repository</h4><p><a href="https://github.com/jayc13/android-notes-app-for-automation">GitHub - jayc13/android-notes-app-for-automation</a></p><h4>Automation Repository</h4><p><a href="https://github.com/jayc13/automation-java-appium-android-for-notes">GitHub - jayc13/automation-java-appium-android-for-notes</a></p><h3>Conclusion</h3><p>First, thanks for reaching out here and reading about what I made for you. I intended to share my experience and learning while writing the article.</p><p>The first conclusion is that you can apply the idea to whatever software you are developing. I pick up the example of mobile apps to make it natural to assimilate the concept of versioning that it’s generally omitted on frontends.</p><p>From my experience, traceability is the key to powering up the product/service quality. Something as simple as including the <a href="https://www.atlassian.com/es/software/jira">Jira</a> ticket id (task/story/bug) into the commit message or the pull request name, pushing the app version to <a href="https://sentry.io/welcome/">Sentry</a> or <a href="https://analytics.google.com/analytics/web/">Google Analytics</a> is the key to move back and forward in the software to fix a bug.</p><p>However, this long article is not only to solve bugs. It’s also to answer questions such as: “How many users are affected by an issue?”. Or improve the user experience, in a previous position, I had the opportunity to enhance the user experience by linking every <a href="https://www.zendesk.com/">Zendesk</a> ticket regarding a production bug reported by a client, to a Jira bug. This allowed customer support to notify the customer when the issue was resolved. We monitored metrics for production bugs reported by both customers and employees. The significance of this metric lies in demonstrating the customer’s loyalty to the product. They not only want to avoid switching to a competitor but also want to contribute to the improvement of your product. Despite the option to ignore the bug, they chose to report it.</p><p>There are tons of analyses that you will able to make with this traceability. For example, measure how good tests the teams are writing and how far the test scenarios implemented are from the real (production) cases.</p><p>It’s now your turn to take this concept and make it a reality in your company, good luck.</p><h3>Extra — Improvements</h3><p>The POC has as many improvements as you can imagine. But I’ll guide you into two interesting concepts that are going to power up your quality process and your software traceability.</p><h4>Test Observability</h4><p>Test observability is the ability to collect, analyze, and visualize data from tests in order to gain insights into the behavior of the system under test. This data can be used to identify and fix bugs, improve performance, and ensure that the system meets its requirements.</p><p>There are three main pillars of test observability:</p><ul><li><strong>Metrics: </strong>Metrics provide a high-level overview of the health of the system under test. They can be used to track things like the number of errors, the response time, and the throughput.</li><li><strong>Logs: </strong>Logs provide a detailed record of what happened during the test. They can be used to troubleshoot problems and identify the root cause of an issue.</li><li><strong>Traces:</strong> Traces provide a chronological view of the interactions between different components of the system under test. They can be used to identify performance bottlenecks and understand how the system is handling traffic.</li></ul><p>Here are some products that you can use for the implementation:</p><ul><li><a href="https://www.lambdatest.com/blog/test-observability/">LambdaTest</a></li><li><a href="https://www.browserstack.com/docs/test-observability/overview/what-is-test-observability">BrowserStack</a></li><li><a href="https://www.globalapptesting.com/blog/software-observability">GlobalAppTesting</a></li></ul><p>For more information about Test Observability, you can check this free course from the <em>Test Automation University</em>:</p><p><a href="https://testautomationu.applitools.com/observability-for-test-automation/">Introduction to Observability for Test Automation</a></p><h4>Release Notes</h4><p>The release note synthesizes the change that the app presents with the new version. By making the release notes part of the traceability process, final users can keep track of the app updates.</p><p>Here there is my special selection of some interesting articles:</p><ul><li><a href="https://medium.com/@freddiewrites/writing-great-app-store-release-notes-3f4cf291e9aa">Writing great App Store release notes</a></li><li><a href="https://levelup.gitconnected.com/how-we-have-automated-release-notes-generation-9365de451327">How We Have Automated Release Notes Generation</a></li><li><a href="https://medium.com/startup-grind/release-notes-that-get-people-excited-e73380af43f8">Release Notes that Get People Excited</a></li><li><a href="https://frill.co/blog/posts/how-to-write-release-notes">How to Write Release Notes: 23 Tips, Tools, and Examples</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5f4d8c4a1d54" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>