Appium vs Selenium: Which One is Best for Your Project?


<p>TestNG and Cucumber are two distinct frameworks in automated testing, each with unique strengths and purposes. TestNG is known for its flexibility in creating and executing test cases across various test suites. Conversely, Cucumber is celebrated for its natural language-based approach, making it a favorite among those who prefer behavior-driven development (BDD).&nbsp;</p>



<p>In this comparison article, we&#8217;ll explore the key differences between these frameworks to help you choose the one that aligns best with your testing needs.</p>



<div id="toc_container" class="no_bullets"><p class="toc_title">Table Of Contents</p><ul class="toc_list"><li><a href="#TestNG_vs_Cucumber_8211_Overview"><span class="toc_number toc_depth_1">1</span> TestNG vs Cucumber &#8211; Overview</a><ul><li><a href="#What_is_TestNG_Framework"><span class="toc_number toc_depth_2">1.1</span> What is TestNG Framework?</a></li><li><a href="#Pros_of_TestNG"><span class="toc_number toc_depth_2">1.2</span> Pros of TestNG</a></li><li><a href="#What_is_Cucumber_Framework"><span class="toc_number toc_depth_2">1.3</span> What is Cucumber Framework?</a></li><li><a href="#Pros_of_Cucumber"><span class="toc_number toc_depth_2">1.4</span> Pros of Cucumber</a></li></ul></li><li><a href="#TestNG_vs_Cucumber_8211_How_to_Write_Tests"><span class="toc_number toc_depth_1">2</span> TestNG vs Cucumber &#8211; How to Write Tests?</a><ul><li><a href="#How_to_write_tests_in_TestNG"><span class="toc_number toc_depth_2">2.1</span> How to write tests in TestNG?</a></li><li><a href="#How_to_write_tests_in_Cucumber"><span class="toc_number toc_depth_2">2.2</span> How to write tests in Cucumber?</a></li></ul></li><li><a href="#TestNG_vs_Cucumber_8211_When_to_Use"><span class="toc_number toc_depth_1">3</span> TestNG vs Cucumber &#8211; When to Use ?</a><ul><li><a href="#When_to_use_TestNG"><span class="toc_number toc_depth_2">3.1</span> When to use TestNG</a></li><li><a href="#When_to_use_Cucumber"><span class="toc_number toc_depth_2">3.2</span> When to use Cucumber</a></li></ul></li><li><a href="#TestNG_vs_Cucumber_Which_is_Better"><span class="toc_number toc_depth_1">4</span> TestNG vs Cucumber: Which is Better?</a><ul><li><a href="#Programming_Language"><span class="toc_number toc_depth_2">4.1</span> Programming Language:</a></li><li><a href="#Support_for_Development"><span class="toc_number toc_depth_2">4.2</span> Support for Development:</a></li><li><a href="#Type_of_Testing"><span class="toc_number toc_depth_2">4.3</span> Type of Testing:</a></li><li><a href="#Use_Case"><span class="toc_number toc_depth_2">4.4</span> Use Case:</a></li><li><a href="#xUnit"><span class="toc_number toc_depth_2">4.5</span> xUnit:</a></li><li><a href="#Client-Side"><span class="toc_number toc_depth_2">4.6</span> Client-Side:</a></li><li><a href="#Server-Side"><span class="toc_number toc_depth_2">4.7</span> Server-Side:</a></li><li><a href="#Grouping"><span class="toc_number toc_depth_2">4.8</span> Grouping:</a></li><li><a href="#Mocks"><span class="toc_number toc_depth_2">4.9</span> Mocks:</a></li><li><a href="#Generators"><span class="toc_number toc_depth_2">4.10</span> Generators:</a></li></ul></li><li><a href="#Cucumber_vs_TestNG_vs_Testsigma"><span class="toc_number toc_depth_1">5</span> Cucumber vs TestNG vs Testsigma</a></li><li><a href="#Conclusion"><span class="toc_number toc_depth_1">6</span> Conclusion</a></li><li><a href="#Frequently_Asked_Questions"><span class="toc_number toc_depth_1">7</span> Frequently Asked Questions</a><ul><li><a href="#Why_use_TestNG_over_Cucumber"><span class="toc_number toc_depth_2">7.1</span> Why use TestNG over Cucumber?</a></li></ul></li></ul></div>
<h2 id="testng-vs-cucumber-overview"><span id="TestNG_vs_Cucumber_8211_Overview"><strong>TestNG vs Cucumber &#8211; Overview</strong></span></h2>



<h3 id="h-what-is-testng-framework"><span id="What_is_TestNG_Framework">What is TestNG Framework?</span></h3>



<p>TestNG, short for &#8220;Test Next Generation,&#8221; is a widely used testing framework primarily associated with Java. It offers comprehensive testing functionalities, allowing the creation of extensive test suites, parallel test execution, and detailed reporting. TestNG&#8217;s annotations provide a high level of customization for test cases, making it a popular choice for unit testing, integration testing, and <a href="https://testsigma.com/end-to-end-testing" target="_blank" rel="noreferrer noopener">end-to-end testing</a> of Java applications.</p>



<h3 id="h-pros-of-testng"><span id="Pros_of_TestNG">Pros of TestNG</span></h3>



<p>TestNG offers flexibility, <a href="https://testsigma.com/parallel-test-runs" target="_blank" rel="noreferrer noopener">parallel test execution</a>, and comprehensive reporting. It is highly customizable through annotations, making it a powerful framework for unit testing, integration testing, and end-to-end testing of Java applications.</p>



<h3 id="h-what-is-cucumber-framework"><span id="What_is_Cucumber_Framework">What is Cucumber Framework?</span></h3>



<p>Cucumber is an open-source testing framework that promotes behavior-driven development (BDD) practices. It is compatible with multiple programming languages, including Java, Ruby, and more. Cucumber tests are written in a natural language, making them highly readable, even for non-technical stakeholders.&nbsp;</p>



<p>Cucumber encourages collaboration between technical and non-technical team members by defining test scenarios in plain language, bridging the communication gap between developers, testers, and business analysts.</p>



<h3 id="h-pros-of-cucumber"><span id="Pros_of_Cucumber">Pros of Cucumber</span></h3>



<p>Cucumber&#8217;s standout features include natural language-based testing, fostering collaboration, and bridging the gap between technical and non-technical team members. Its readable and expressive Gherkin language promotes a better understanding of test scenarios.</p>



<h2 id="testng-vs-cucumber-how-to-write-tests"><span id="TestNG_vs_Cucumber_8211_How_to_Write_Tests"><strong>TestNG vs Cucumber &#8211; How to Write Tests?</strong></span></h2>



<h3 id="h-how-to-write-tests-in-testng"><span id="How_to_write_tests_in_TestNG">How to write tests in TestNG?</span></h3>



<p>In TestNG, tests are written as methods, and annotations play a pivotal role in defining the test flow.&nbsp;</p>



<p>TestNG offers annotations like @Test, @BeforeMethod, @AfterMethod, @DataProvider, and more. These annotations allow testers to define test setup, execution, and teardown procedures, enhancing test customization.</p>



<h3 id="h-how-to-write-tests-in-cucumber"><span id="How_to_write_tests_in_Cucumber">How to write tests in Cucumber?</span></h3>



<p>Cucumber tests are written in a natural language format using a plain-text format called Gherkin. Test scenarios are defined in feature files using keywords like Given, When, and Then. These feature files are complemented by step definitions and implemented in programming languages like Java or Ruby. The step definitions map the natural language steps to executable code.</p>



<h2 id="testng-vs-cucumber-when-to-use"><span id="TestNG_vs_Cucumber_8211_When_to_Use"><strong>TestNG vs Cucumber &#8211; When to Use ?</strong></span></h2>



<h3 id="h-when-to-use-testng"><span id="When_to_use_TestNG">When to use TestNG</span></h3>



<p>TestNG is an excellent choice when you need a versatile testing framework for unit, integration, and end-to-end testing of Java applications. It excels in handling test case management, parallel test execution, and reporting, making it suitable for a wide range of test automation scenarios.</p>



<h3 id="h-when-to-use-cucumber"><span id="When_to_use_Cucumber">When to use Cucumber</span></h3>



<p>Cucumber is the preferred option when you want to implement behavior-driven development (BDD) practices in your testing process. It is ideal for scenarios where collaboration between technical and non-technical team members is essential.&nbsp;</p>



<p>Cucumber&#8217;s natural language-based tests enhance the understanding of test cases across the team.</p>



<h2 id="h-testng-vs-cucumber-which-is-better"><span id="TestNG_vs_Cucumber_Which_is_Better"><strong>TestNG <strong>vs</strong></strong> <strong><strong>Cucumber</strong>: Which is Better?</strong></span></h2>



<h3 id="h-programming-language"><span id="Programming_Language">Programming Language:</span></h3>



<p>&#8211; TestNG: Primarily designed for Java, but offers support for multiple languages through various plugins.</p>



<p>&#8211; Cucumber: Supports multiple programming languages, including Java, Ruby, and JavaScript, making it versatile for diverse development environments.</p>



<h3 id="h-support-for-development"><span id="Support_for_Development">Support for Development:</span></h3>



<p>&#8211; TestNG: Well-suited for developers, especially in Java-centric environments, providing annotations for test configuration.</p>



<p>&#8211; Cucumber: Geared towards collaboration between developers and non-technical stakeholders, as it uses Gherkin syntax for writing tests in plain language.</p>



<h3 id="h-type-of-testing"><span id="Type_of_Testing">Type of Testing:</span></h3>



<p>&#8211; TestNG: Widely used for unit, integration, and end-to-end testing.</p>



<p>&#8211; Cucumber: Primarily focuses on behavior-driven development (BDD) and acceptance testing, allowing tests to be written in natural language.</p>



<h3 id="h-use-case"><span id="Use_Case">Use Case:</span></h3>



<p>&#8211; TestNG: Ideal for testing a broad range of applications and scenarios, offering flexibility in test design.</p>



<p>&#8211; Cucumber: Best suited for scenarios where collaboration between technical and non-technical team members is crucial, promoting clear communication through feature files.</p>



<h3 id="h-xunit"><span id="xUnit">xUnit:</span></h3>



<p>&#8211; TestNG: Follows the xUnit architecture and provides annotations for test lifecycle management.</p>



<p>&#8211; Cucumber: Has its unique Gherkin syntax, deviating from the traditional xUnit structure, emphasizing <a href="https://en.wikipedia.org/wiki/Behavior-driven_development" target="_blank" rel="noreferrer noopener">behavior-driven development</a>.</p>



<h3 id="h-client-side"><span id="Client-Side">Client-Side:</span></h3>



<p>&#8211; TestNG: Primarily used for client-side testing, covering a wide array of scenarios in application development.</p>



<p>&#8211; Cucumber: Suitable for client-side testing, especially when behavior-driven development and collaboration are essential.</p>



<h3 id="h-server-side"><span id="Server-Side">Server-Side:</span></h3>



<p>&#8211; TestNG: Well-suited for server-side testing, ensuring comprehensive coverage in application testing.</p>



<p>&#8211; Cucumber: Can be applied to server-side testing, focusing on behavior-driven development principles.</p>



<h3 id="h-grouping"><span id="Grouping">Grouping:</span></h3>



<p>&#8211; TestNG: Provides flexible grouping mechanisms, allowing the execution of specific test groups.</p>



<p>&#8211; Cucumber: Uses feature files and scenarios for organization, but grouping is less explicit than in TestNG.</p>



<h3 id="h-mocks"><span id="Mocks">Mocks:</span></h3>



<p>&#8211; TestNG: Supports mocks and can be integrated with mock frameworks for effective testing.</p>



<p>&#8211; Cucumber: Can be used with mocking frameworks but might require additional configurations for seamless integration.</p>



<h3 id="h-generators"><span id="Generators">Generators:</span></h3>



<p>&#8211; TestNG: Offers data-driven testing capabilities, allowing the use of data providers for dynamic test case generation.</p>



<p>&#8211; Cucumber: Excels in data-driven testing through scenarios and tables in feature files, providing a clear structure for test generation.</p>



<p>In comparing Cucumber and TestNG, the choice depends on the project&#8217;s nature, team composition, and the emphasis on behavior-driven development principles. While TestNG is versatile and well-suited for various testing scenarios, Cucumber excels in scenarios where collaboration and communication through natural language are pivotal.</p>



<h2 id="h-cucumber-vs-testng-vs-testsigma"><span id="Cucumber_vs_TestNG_vs_Testsigma"><strong>Cucumber vs TestNG vs Testsigma</strong></span></h2>



<p>When considering the trio of Cucumber, TestNG, and Testsigma, each serves distinct purposes in the testing landscape. Cucumber, focusing on behavior-driven development (BDD), promotes collaboration between technical and non-technical stakeholders through its Gherkin syntax. TestNG, a versatile testing framework, caters to various testing needs, emphasizing annotations for Java-based development. Testsigma, on the other hand, stands out as a cloud-based automation testing tool, streamlining the testing process with its no-code approach and comprehensive test management.</p>



<div class="cta-banner-v5">
<div class="title-with-description ">
<p class="title">Automate Your Tests for Web, Mobile <br> and Desktop Applications from the same place </p>
</div>
<a href="https://testsigma.com/" target="_blank" class="cta-btn-v1" rel="noopener">Check out Testsigma</a>
</div>



<h2 id="h-conclusion"><span id="Conclusion"><strong>Conclusion</strong></span></h2>



<p>In conclusion, the choice between Cucumber, TestNG, and Testsigma hinges on project requirements and team dynamics. Cucumber excels in BDD scenarios, TestNG offers versatility in testing types, and Testsigma is a modern, no-code solution for efficient test automation. The decision rests on aligning the tool&#8217;s strengths with the specific needs and methodologies of the testing environment.</p>



<h2 id="h-frequently-asked-questions"><span id="Frequently_Asked_Questions"><strong>Frequently Asked Questions</strong></span></h2>



<h3 id="h-why-use-testng-over-cucumber"><span id="Why_use_TestNG_over_Cucumber">Why use TestNG over Cucumber?</span></h3>



<p>TestNG becomes a pragmatic choice if the project demands a focus on unit testing, integration testing, and a comprehensive set of annotations for test configuration..</p>


TestNG vs Cucumber | Top Key Differences

Top Copado Alternatives List to look for

Swagger vs Postman Top 10 Differences You Should Know

Swagger vs Postman | Top 10 Differences You Should Know

Apache JMeter vs Selenium The Key Difference

Apache JMeter vs Selenium: The Key Difference

Cypress vs. Selenium- Which framework to choose

Cypress vs Selenium- Which Framework is Best Fit for You?

Playwright vs Selenium: Which one should you choose?

Playwright vs Selenium: Which One should You Choose?

CircleCI Vs Travis CI: Which is the Best CI/CD Tool?


<p>In this post, we will introduce CI/CD by taking reference to two of the most popular tools used in software development today: GitLab vs Jenkins. With their benefits to methods of working, we will explore more of CI/CD and why it is an integral part of SDLC today.</p>



<p id="h-a-brief-introduction-to-ci-cd"><strong>A brief introduction to <a href="https://testsigma.com/continuous-integration#Continuous_Integration:~:text=too%20many%20conflicts.-,Continuous%20Integration%20Vs%20Continuous%20Deployment%20Vs%20Continuous%20Delivery,-Continuous%20Integration%2C%20Continuous" target="_blank" rel="noreferrer noopener">Continuous Integration/Continuous Delivery</a></strong></p>



<div class="wp-block-image"><figure class="aligncenter is-resized"><img loading="lazy" src="https://images.storychief.com/account_36412/image_d44f7e683445451a189eb6e9d83d02eb_2000.png" alt="GitLab vs Jenkins -  introduction to CI/CD" width="600" height="200" /></figure></div>



<p>When these concepts are attached to one another to work in automation on a project, we call this <strong>a pipeline</strong>. A “<strong>pipeline</strong>” because it is serial like a pipe and no state can be jumped or skipped. You cannot achieve continuous delivery when continuous integration is not achieved. However, for this post, we can limit ourselves to just this brief introduction of CI/CD pipelines. Although, with the detailed analysis of GitLab vs Jenkins, we will touch on the concepts at various places.</p>



<div id="toc_container" class="no_bullets"><p class="toc_title">Table Of Contents</p><ul class="toc_list"><li><a href="#GitLab_vs_Jenkins_Point-by-Point_Comparison"><span class="toc_number toc_depth_1">1</span> GitLab vs Jenkins – Point-by-Point Comparison</a></li><li><a href="#Icebreaker_Between_GitLab_CICD_vs_Jenkins"><span class="toc_number toc_depth_1">2</span> Icebreaker Between GitLab CI/CD vs Jenkins</a></li><li><a href="#Alternatives_to_GitLab_CICD_and_Jenkins"><span class="toc_number toc_depth_1">3</span> Alternatives to GitLab CI/CD and Jenkins</a></li><li><a href="#Conclusion"><span class="toc_number toc_depth_1">4</span> Conclusion</a></li><li><a href="#Frequently_Asked_Questions"><span class="toc_number toc_depth_1">5</span> Frequently Asked Questions</a><ul><li><a href="#Does_GitLab_use_Jenkins"><span class="toc_number toc_depth_2">5.1</span> Does GitLab use Jenkins?</a></li><li><a href="#Can_GitHub_Actions_replace_Jenkins"><span class="toc_number toc_depth_2">5.2</span> Can GitHub Actions replace Jenkins?</a></li><li><a href="#Is_GitLab_good_for_CI-CD"><span class="toc_number toc_depth_2">5.3</span> Is GitLab good for CI-CD?</a></li><li><a href="#How_does_Jenkins_connect_to_GitLab"><span class="toc_number toc_depth_2">5.4</span> How does Jenkins connect to GitLab?</a></li></ul></li></ul></div>
<h2 id="gitlab-vs-jenkins-point-by-point-comparison"><span id="GitLab_vs_Jenkins_Point-by-Point_Comparison"><strong>GitLab vs Jenkins – Point-by-Point Comparison</strong></span></h2>



<p>For a quick reference for testers and developers, we have created the following table that highlights GitLab vs Jenkins comparison,</p>



<figure class="wp-block-table"><table><tbody><tr><td><strong>Parameter</strong></td><td><strong>GitLab</strong></td><td><strong>Jenkins</strong></td></tr><tr><td><strong>Integrated Platform</strong></td><td>Majorly a CI/CD platform. But lacks code review, version control, and other DevOps features.</td><td>A comprehensive DevOps platform with proper version control, code review, bug tracking, <a href="https://about.gitlab.com/topics/ci-cd/" target="_blank" rel="noreferrer noopener">CI/CD,</a> and more.</td></tr><tr><td><strong>Development method</strong></td><td>Open-source</td><td>Open-source</td></tr><tr><td><strong>Price</strong></td><td>Free version + Paid Version</td><td>Free</td></tr><tr><td><strong>Language</strong></td><td>Ruby</td><td>Java</td></tr><tr><td><strong>Working Architecture</strong></td><td>GitLab CI and GitLab Runner</td><td>Master-Slave</td></tr><tr><td><strong>Plugins</strong></td><td>Limited plugins</td><td>1700+ Plugins to choose from</td></tr><tr><td><strong>Community Size</strong></td><td>Comparatively Smaller</td><td>Large Community</td></tr><tr><td><strong>Platform Support</strong></td><td>Supports only Unix-based OS such as Debian, Red Hat Linux, Ubuntu, Scientific Linux, CentOS, Oracle Linux, etc. It does not support Windows or macOS.</td><td>Supports Windows, macOS, Linux, and other Unix-like OS</td></tr><tr><td><strong>Support</strong></td><td>Provides 24&#215;5 support for paid users, and community support is available for free users</td><td>Offers community support and documentation</td></tr><tr><td><strong>Ease of use</strong></td><td>Modern and easy-to-use, user-friendly interface</td><td>Older interface, so can be complex to use</td></tr><tr><td><strong>CI/CD integration</strong></td><td>Provides native CI/CD capabilities</td><td>Focuses on CI/CD automation</td></tr><tr><td><strong>Containerization</strong></td><td>Provides built-in support for Docker containers and Kubernetes orchestration</td><td>Provides support via plugins, but does not offer extensive native integration</td></tr><tr><td><strong>Setup </strong></td><td>Intuitive configuration and navigation</td><td>Configuration can be complex for new users</td></tr><tr><td><strong>Release frequency</strong></td><td>Provides updates and feature releases on a regular basis</td><td>Provides frequent updates and feature releases</td></tr></tbody></table></figure>



<h2 id="h-icebreaker-between-gitlab-ci-cd-vs-jenkins"><span id="Icebreaker_Between_GitLab_CICD_vs_Jenkins"><strong>Icebreaker Between GitLab CI/CD vs Jenkins</strong></span></h2>



<p>While GitLab CI/CD and Jenkins both are exceptionally good software that currently rules the market but there can be an ice-breaking point that can help you decide clearly which tool to choose.</p>



<p>Firstly, GitLab’s main strength comes from being cloud-based and having good monitoring features. Be it branch monitoring or performance monitoring, GitLab has a really good UI and great metric system that help analyze things clearly at any point in software development. This is not true with Jenkins or maybe with any other CI tool currently available. However, it all comes at a price as GitLab comes in free and premium packages. The main point of this section is to let you know that if monitoring and metrics are your priority, your bucks will be well spent on GitLab.</p>



<p>On the other hand, Jenkins is completely free to use and is a popular choice just for this part. As free software, it gives you a lot of things that the majority of paid CI tools do not give. The main strength of Jenkins comes from its plugins, which are thousands in number. As a tester, whatever you may need can be found in a plugin which gives a lot more flexibility. </p>



<p>Another good thing about having an open-source plugin-based system is that you can build your own if feasible. It has a good UI (which is rare in CI-based systems) and is continuously updated by developers. Jenkins should be your first choice when the team is satisfied with the available plugins, and there are no major requirements that Jenkins can’t suffice. It is also extremely easy to learn and use for a beginner.</p>



<h2 id="h-alternatives-to-gitlab-ci-cd-and-jenkins"><span id="Alternatives_to_GitLab_CICD_and_Jenkins"><strong>Alternatives to GitLab CI/CD and Jenkins</strong></span></h2>



<p><p style="padding-bottom: 20px">For people who wish to explore a few more tools other than GitLab and Jenkins for CI capabilities can refer to the following list of five most preferred:</p></p>



<ul><li>Circle CI</li><li>Bamboo</li><li>Teamcity</li><li>Travis CI</li><li>Codeship</li></ul>



<p><p style="padding-top: 20px">Let us know in the comment section if you are a user of one of these tools and how it compares with GitLab vs Jenkins.</p></p>



<h2 id="h-conclusion"><span id="Conclusion"><strong>Conclusion</strong></span></h2>



<p>The concept of continuous integration and continuous development has seeped too deep into SDLC that even smaller companies of just a few developers also find it relevant. It helps merge code smoothly and run various tests upgrading the application&#8217;s quality and minimizing the chances of errors at the user’s end. </p>



<p>In this post about Gitlab vs Jenkins, we took two of the most popular tools that help us achieve just that. GitLab CI/CD and Jenkins are equally efficient with uniquely different features that help us make a clear choice between them. </p>



<p>Starting with why to choose each of them to how to set them up on your machine, I hope this post will help you start your journey with the best <a href="https://testsigma.com/blog/ci-cd-tools/" target="_blank" rel="noreferrer noopener">CI/CD tools</a> in the market. For any clarifications and suggestions, do let us know in the comment section. Thank you for giving this post your valuable time.</p>



<h2 id="h-frequently-asked-questions"><span id="Frequently_Asked_Questions"><strong>Frequently Asked Questions</strong></span></h2>



<h3 id="h-does-gitlab-use-jenkins"><span id="Does_GitLab_use_Jenkins">Does GitLab use Jenkins?</span></h3>



<p>No. GitLab and Jenkins are two popular tools used for continuous integration and continuous development/deployment features. They both offer their own set of pros and cons which are discussed in this post. None of the tools takes the help of another; they work independently.</p>



<h3 id="h-can-github-actions-replace-jenkins"><span id="Can_GitHub_Actions_replace_Jenkins">Can GitHub Actions replace Jenkins?</span></h3>



<p>GitHub actions and Jenkins both provide great workflow features to build, test, release, and deploy your code. For a developer, they both are equally popular and equally powerful. In the end, the question comes down to which one you should choose between Jenkins and GitHub actions rather than which one will replace what.</p>



<h3 id="h-is-gitlab-good-for-ci-cd"><span id="Is_GitLab_good_for_CI-CD">Is GitLab good for CI-CD?</span></h3>



<p>Yes, GitLab is a very powerful CI/CD tool with tons of features crafted just for developers and testers. It has excellent UI and monitoring capabilities.</p>



<h3 id="h-how-does-jenkins-connect-to-gitlab"><span id="How_does_Jenkins_connect_to_GitLab">How does Jenkins connect to GitLab?</span></h3>



<p>GitLab is available as a plugin system for Jenkins. To add GitLab to Jenkins, visit the plugin section and install GitLab and Git plugins to enjoy Jenkins along with GitLab.</p>
