<?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 Omer Talmi on Medium]]></title>
        <description><![CDATA[Stories by Omer Talmi on Medium]]></description>
        <link>https://medium.com/@omertalmi5?source=rss-192a79c0bf16------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*xQP_jx8nmAGdzEHqiGFWtg@2x.jpeg</url>
            <title>Stories by Omer Talmi on Medium</title>
            <link>https://medium.com/@omertalmi5?source=rss-192a79c0bf16------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 02:18:05 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@omertalmi5/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[Benefiting the most of cypress report]]></title>
            <link>https://blog.devgenius.io/benefiting-the-most-of-cypress-report-10279fd9feb6?source=rss-192a79c0bf16------2</link>
            <guid isPermaLink="false">https://medium.com/p/10279fd9feb6</guid>
            <category><![CDATA[gitlab]]></category>
            <category><![CDATA[ci-cd-pipeline]]></category>
            <category><![CDATA[cypress]]></category>
            <category><![CDATA[gitlab-page]]></category>
            <category><![CDATA[mochawesome]]></category>
            <dc:creator><![CDATA[Omer Talmi]]></dc:creator>
            <pubDate>Mon, 14 Sep 2020 19:22:48 GMT</pubDate>
            <atom:updated>2021-03-12T13:17:36.469Z</atom:updated>
            <content:encoded><![CDATA[<h3>Benefit the Most Out of Cypress Reports</h3><h4><strong>How to integrate Mochawesome reports with GitLab Pages</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XvX5H2x_urnYKNS6_PCUnA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@isaacmsmith">Isaac Smith</a> on <a href="https://unsplash.com/s/photos/guide?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>As the popularity of <a href="https://www.cypress.io/">Cypress</a> as a testing framework increases, it is important to reflect the tests results in a clear and accessible way.</p><p>In the <a href="https://en.wikipedia.org/wiki/Continuous_integration">Continuous Integration</a> era, many CI/CD pipelines, including Cypress tests, run all the time. The team developers should have an easy way to know the state of the product and to quickly analyse the reason for test failures. The purpose of this is to reduce the time and effort spent looking at the report.</p><p>This can be achieved by using the combination of <a href="https://www.npmjs.com/package/mochawesome">Mochawesome reporter</a> and <a href="https://docs.gitlab.com/ee/user/project/pages/">GitLab Pages</a>. The pair provides a convenient report in a fixed place.</p><p>Let’s dive into both of them:</p><h4><strong>Mochawesome reporter</strong></h4><p>“<em>Mochawesome is a custom reporter for use with the Javascript testing framework </em><a href="https://mochajs.org/"><em>mocha</em></a>”, according to <a href="https://www.npmjs.com/package/mochawesome">npm</a>. It is widely used for End-To-End Testing with Cypress. It offers a clear and friendly UI, which clarifies the reason of the test failure swiftly and clearly.</p><h4><strong>GitLab Pages</strong></h4><p>GitLab Pages is a feature of GitLab, which enables us to publish static websites directly from our GitLab CI/CD pipeline. It takes the artifacts from our CI/CD pipeline and transforms them into a static website. All your team developers can access this website easily.</p><p>The GitLab Page is declared in the configuration file of the CI/CD pipeline, usually with the name .gitlab-ci.yml. The file contains different blocks called stages, each defining a step in the CI/CD pipeline (building, testing, deploying…).</p><h4><strong>Integrating the two of them</strong></h4><p>We’re going to assume here that Mochawesome is already configured in your project. If not, you can learn how to do that <a href="https://docs.cypress.io/guides/tooling/reporters.html#Custom-reporter">here</a>.</p><p>Let’s integrate generating the report in our CI pipeline:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/59e11951d581e9557cb3edb47e38fa25/href">https://medium.com/media/59e11951d581e9557cb3edb47e38fa25/href</a></iframe><h4>Editing the .gitlab-ci.yml</h4><p>First, we add our commands to create a GitLab Page in the .gitlab-ci.yml. We should create a separate stage with the name pages.</p><p>After generating a Mochawesome report, a folder named mochawesome-report will be created. The folder contains the html page and all the results files that are needed in order to publish the report. Next, we should rename this folder public, a reserved word for GitLab, in order to make it a GitLab Page. In addition, we need to declare the folder as an artifact of the pipeline.</p><p>After running the pipeline, GitLab will automatically create another stage called ‘deploy’, and deploy the report directly to the GitLab Page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Kn10NKH8dOijKIz6hcOPpg.png" /><figcaption>Notice the extra stage created named ‘deploy’</figcaption></figure><h4>Accessing the GitLab Page</h4><p>Finally, we can navigate to Settings -&gt; Pages in the navigation menu, and find our GitLab Page URL address. In order to show the report we need to add our report name (click the link below for an example report):</p><p><a href="https://omertalmi5.gitlab.io/cypress-example/mochawesome.html">https://omertalmi5.gitlab.io/cypress-example/mochawesome.html</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/837/1*1ue1QfxVyryhyYqcZsggkw.png" /><figcaption>The GitLab Page URL address</figcaption></figure><p>So far, we have learned how to integrate Mochawesome reports with GitLab Pages. Now, every time we enter the URL address, we can watch the report. With every build of the CI/CD pipeline, the report will be updated.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Epg071eHnheZJmDpEvFM7A.png" /><figcaption>A Mochawesome report example</figcaption></figure><h4><strong>Conclusion</strong></h4><p>My goal for this article is to improve your daily work-flow. This article presents a way to eliminate the many invaluable hours you’ll probably spend trying to understand your Cypress reports. I hope the information presented helps you achieve this.</p><p>Thank you for taking the time to read this article.</p><p>A full example can be found in my <a href="https://gitlab.com/omertalmi5/cypress-example">GitLab page</a>.</p><p>Feel free to ask any questions in the comments.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=10279fd9feb6" width="1" height="1" alt=""><hr><p><a href="https://blog.devgenius.io/benefiting-the-most-of-cypress-report-10279fd9feb6">Benefiting the most of cypress report</a> was originally published in <a href="https://blog.devgenius.io/">Dev Genius</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>