cucumber-jvm-starter-maven-java - GitLite

KO | EN

gitlite — search

#react #ai #typescript #golang #go #machine-learning #deep-learning #docker #windows #awesome #cli #security #pytorch #open-source

cucumber-jvm-starter-maven-java

(★ 499)

This is the simplest possible setup for Cucumber-JVM using Java with Maven.

파일 탐색기

최종 버전 다운로드 (.zip)

- - test-java.yaml
  - zizmor-analysis.yaml
- renovate.json
- - maven-wrapper.jar
  - maven-wrapper.properties
  - MavenWrapperDownloader.java
.gitignore
LICENSE
mvnw
mvnw.cmd
pom.xml
README.md

# 설치 가이드

1. 코드 내려받기

git clone https://github.com/cucumber/cucumber-jvm-starter-maven-java

깃허브에서 프로젝트 코드 전체를 내 컴퓨터로 내려받습니다.

cd cucumber-jvm-starter-maven-java

방금 내려받은 프로젝트 폴더 안으로 이동합니다.

2. Maven (Java)

보통 추천

사전 준비물

Git GitHub에서 프로젝트 코드를 내려받으려면 필요합니다.
JDK (Java) Java 프로젝트를 빌드/실행하려면 필요합니다.
Maven mvn 명령어를 쓰기 위한 빌드 도구입니다.

mvn verify -DexcludedGroups="Haricots" -Dgroups="Zucchini | Gherkin"

Maven으로 의존성 설치와 빌드를 진행합니다.

✅ BUILD SUCCESS 메시지가 뜨면 성공입니다. target/ 폴더에 결과물이 생성됩니다.

이 레포의 README에 적힌 실제 명령어를 그대로 가져왔습니다.

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# Cucumber-JVM Starter: Java with Maven

This is the simplest possible setup for Cucumber-JVM using Java with Maven.
There is nothing fancy like a webapp or browser testing. All this does is to
show you how to set up and run Cucumber! If this is your first time using
Cucumber have a look at the [10-minute tutorial](https://cucumber.io/docs/guides/10-minute-tutorial)
first.

To write assertions the project comes with [AssertJ](https://assertj.github.io/doc/#assertj-core-assertions-guide)
included.

## Get the code

Git:

git clone https://github.com/cucumber/cucumber-jvm-starter-maven-java.git
    cd cucumber-jvm-starter-maven-java

Or [download a zip](https://github.com/cucumber/cucumber-jvm-starter-maven-java/archive/main.zip) file.

## Run the tests

Open a command window and run:

On macOS/Linux:

```shell
./mvnw test
```

On Windows PowerShell:

```powershell
.\mvnw.cmd test
```

This runs Cucumber features using Cucumber's JUnit Platform Engine. The `Suite`
annotation on the `RunCucumberTest` class tells JUnit to kick off Cucumber.

```text
[INFO] Running com.example.project.RunCucumberTest

Scenario: a few cukes                 # classpath:com/example/project/belly.feature:3
  ✔ Given I have 42 cukes in my belly # com.example.project.StepDefinitions.I_have_cukes_in_my_belly(int)
  ↷ When I wait 1 hour                # com.example.project.StepDefinitions.i_wait_seconds(java.lang.Integer)
        org.opentest4j.TestAbortedException: TODO: Implement me
                at com.example.project.StepDefinitions.i_wait_seconds(StepDefinitions.java:19)
                at ✽.I wait 1 hour(classpath:com/example/project/belly.feature:5)
  ↷ Then my belly should growl
```

The output show that there is a single feature file with one scenario. The
scenario has three steps, one passing, one pending, and one undefined. See if
you make can each step pass.

## Configuration

The [Cucumber JUnit Platform Engine](https://github.com/cucumber/cucumber-jvm/tree/main/cucumber-junit-platform-engine) uses configuration parameters to know what features to run,
where the glue code lives, what plugins to use, etc. When using JUnit, these
configuration parameters are provided through the `@ConfigurationParameter`
annotation on your test.

For available parameters see: `io.cucumber.junit.platform.engine.Constants`

## Run a subset of Features or Scenarios

Specify a particular scenario by *line*

@SelectClasspathResource(value = "com/example/project/belly.feature", line = 3)

In case you have multiple feature files or scenarios to run against repeat the
annotation.

You can also specify what to run by *tag*.

First add a tag to a scenario:

```feature
Feature: Belly

@Zucchini
  Scenario: a few cukes
```

Then add an annotation to `RunCucumberTest`.

```java
@IncludeTags("Zucchini")
```

Tags can be selected from the CLI using the `groups` and `excludedGroups` parameters. These take a
[JUnit5 Tag Expression](https://junit.org/junit5/docs/current/user-guide/#running-tests-tag-expressions). 
Note: When using JUnit, the `@` is not part of the tag.

```
mvn verify -DexcludedGroups="Haricots" -Dgroups="Zucchini | Gherkin"
```

### Running a single scenario or feature

Maven does not (yet) support selecting single features or scenarios
with JUnit selectors. As a work around the `cucumber.features` property can be
used. Because this property will cause Cucumber to ignore any other selectors
from JUnit it is prudent to only execute the Cucumber engine.

To select the scenario on line 3 of the `belly.feature` file use:

```
./mvnw test -Dsurefire.includeJUnit5Engines=cucumber -Dcucumber.features=src/test/resources/com/example/project/belly.feature:3 
```

Note: Add `-Dcucumber.plugin=pretty` to get a more detailed output during test
execution.