<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cucumber on Software Factory</title><link>/tags/cucumber/</link><description>Recent content in Cucumber on Software Factory</description><generator>Hugo</generator><language>en</language><atom:link href="/tags/cucumber/index.xml" rel="self" type="application/rss+xml"/><item><title>Gherkin tests in Java</title><link>/use/howto/test/bdd-java/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/use/howto/test/bdd-java/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;a class="td-heading-self-link" href="#introduction" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;In this guide, we&amp;rsquo;ll walk you through using Gherkin for behavior-driven development (BDD) tests
for a Maven project in GitLab.&lt;/p&gt;
&lt;p&gt;We’ll start from a use case or a new feature request, write Gherkin scenarios,
implement step definitions, and integrate these tests into GitLab CI/CD.&lt;/p&gt;
&lt;h3 id="step-1-capture-the-use-case-or-new-feature-request"&gt;Step 1: Capture the Use Case or New Feature Request&lt;a class="td-heading-self-link" href="#step-1-capture-the-use-case-or-new-feature-request" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h3&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Define the Use Case&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Begin with a use case or new feature request from the stakeholder. For example, a
new feature request for a &amp;ldquo;User Login&amp;rdquo; functionality:&lt;/p&gt;</description></item></channel></rss>