chore: rename integration tests e2e (#417)

* chore: rename integration tests e2e

Signed-off-by: Todd Baert <todd.baert@dynatrace.com>

* Update pom.xml

Co-authored-by: Giovanni Liva <giovanni.liva@dynatrace.com>
Signed-off-by: Todd Baert <toddbaert@gmail.com>

---------

Signed-off-by: Todd Baert <todd.baert@dynatrace.com>
Signed-off-by: Todd Baert <toddbaert@gmail.com>
Co-authored-by: Giovanni Liva <giovanni.liva@dynatrace.com>
This commit is contained in:
Todd Baert 2023-05-03 00:36:22 -04:00 committed by GitHub
parent 19415edb71
commit a5c93aca0a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
5 changed files with 12 additions and 12 deletions

View File

@ -38,8 +38,8 @@ jobs:
restore-keys: | restore-keys: |
${{ runner.os }}-maven- ${{ runner.os }}-maven-
- name: Build with Maven - name: Verify with Maven
run: mvn --batch-mode --update-snapshots verify -P integration-test run: mvn --batch-mode --update-snapshots verify -P e2e-test
- name: Upload coverage to Codecov - name: Upload coverage to Codecov
uses: codecov/codecov-action@5bf250470ea3e4bf9456e73127015eb78ce4c280 uses: codecov/codecov-action@5bf250470ea3e4bf9456e73127015eb78ce4c280

View File

@ -16,16 +16,16 @@ If you think we might be out of date with the spec, you can check that by invoki
If you're adding tests to cover something in the spec, use the `@Specification` annotation like you see throughout the test suites. If you're adding tests to cover something in the spec, use the `@Specification` annotation like you see throughout the test suites.
## Integration tests ## End-to-End Tests
The continuous integration runs a set of [gherkin integration tests](https://github.com/open-feature/test-harness/blob/main/features/evaluation.feature) using [`flagd`](https://github.com/open-feature/flagd). These tests do not run with the default maven profile. If you'd like to run them locally, you can start the flagd testbed with The continuous integration runs a set of [gherkin e2e tests](https://github.com/open-feature/test-harness/blob/main/features/evaluation.feature) using [`flagd`](https://github.com/open-feature/flagd). These tests do not run with the default maven profile. If you'd like to run them locally, you can start the flagd testbed with
``` ```
docker run -p 8013:8013 ghcr.io/open-feature/flagd-testbed:latest docker run -p 8013:8013 ghcr.io/open-feature/flagd-testbed:latest
``` ```
and then run and then run
``` ```
mvn test -P integration-test mvn test -P e2e-test
``` ```
## Releasing ## Releasing

10
pom.xml
View File

@ -11,8 +11,8 @@
<maven.compiler.source>1.8</maven.compiler.source> <maven.compiler.source>1.8</maven.compiler.source>
<maven.compiler.target>${maven.compiler.source}</maven.compiler.target> <maven.compiler.target>${maven.compiler.source}</maven.compiler.target>
<junit.jupiter.version>5.9.3</junit.jupiter.version> <junit.jupiter.version>5.9.3</junit.jupiter.version>
<!-- exclusion expression for integration tests --> <!-- exclusion expression for e2e tests -->
<testExclusions>**/integration/*.java</testExclusions> <testExclusions>**/e2e/*.java</testExclusions>
<module-name>${groupId}.${artifactId}</module-name> <module-name>${groupId}.${artifactId}</module-name>
</properties> </properties>
@ -495,10 +495,10 @@
<profiles> <profiles>
<profile> <profile>
<!-- this profile handles running the flagd integration tests --> <!-- this profile handles running the flagd e2e tests -->
<id>integration-test</id> <id>e2e-test</id>
<properties> <properties>
<!-- run the integration tests by clearing the exclusions --> <!-- run the e2e tests by clearing the exclusions -->
<testExclusions/> <testExclusions/>
</properties> </properties>
<build> <build>

View File

@ -1,4 +1,4 @@
package dev.openfeature.sdk.integration; package dev.openfeature.sdk.e2e;
import org.junit.platform.suite.api.ConfigurationParameter; import org.junit.platform.suite.api.ConfigurationParameter;
import org.junit.platform.suite.api.IncludeEngines; import org.junit.platform.suite.api.IncludeEngines;

View File

@ -1,4 +1,4 @@
package dev.openfeature.sdk.integration; package dev.openfeature.sdk.e2e;
import dev.openfeature.contrib.providers.flagd.FlagdProvider; import dev.openfeature.contrib.providers.flagd.FlagdProvider;
import dev.openfeature.sdk.Client; import dev.openfeature.sdk.Client;