Nicht in der Lage, die fehlgeschlagenen Testfälle in der Selengurke mit Junit mit dem Befehl Maven Test von CMD erneut a ⇐ Java

[Anonymous]

failedrun.java:

Code: Select all

package myrunner;

import org.junit.runner.RunWith;

import io.cucumber.junit.Cucumber;
import io.cucumber.junit.CucumberOptions;

@RunWith(Cucumber.class)
@CucumberOptions(features = {"target\\failedrerun.txt"},
glue = {"com.qa.stepDefinitions", "com.qa.hooks" },
stepNotifications = true,
plugin = {"pretty","com.aventstack.extentreports.cucumber.adapter.ExtentCucumberAdapter:"},
monochrome = false,
dryRun = false)

public class FailedRun {
}

pom.xml:

Code: Select all

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
4.0.0

scmb
SeleniumCucumberMBDD
0.0.1-SNAPSHOT
SeleniumCucumberMBDD
http://www.example.com


UTF-8
17
17





org.seleniumhq.selenium
selenium-java
4.30.0




io.github.bonigarcia
webdrivermanager
5.8.0




io.cucumber
cucumber-java
7.14.0


io.cucumber
cucumber-junit
7.14.0


io.cucumber
cucumber-core
7.14.0


io.cucumber
cucumber-picocontainer
7.14.0
test




org.junit.jupiter
junit-jupiter-api
5.10.0
test



org.slf4j
slf4j-simple
2.0.9


org.slf4j
slf4j-api
2.0.9




com.aventstack
extentreports
5.1.0


tech.grasshopper
extentreports-cucumber7-adapter
1.9.0




org.apache.poi
poi-ooxml
5.2.3




javax.xml.bind
jaxb-api
2.3.1




org.projectlombok
lombok
1.18.30
provided







maven-compiler-plugin
3.10.1




org.apache.maven.plugins
maven-surefire-plugin
3.5.2


**/SuiteRunnerTest.java
**/FailedRun.java










rerun-failed



maven-compiler-plugin
3.10.1


org.apache.maven.plugins
maven-surefire-plugin
3.5.2


**/target/failedrerun.txt

**/SuiteRunnerTest.java

Maven -Befehle in CMD, die ich verwendet habe:

Code: Select all

mvn test -Dcucumber.features=target\\failedrerun.txt
mvn test -Dcucumber.features="target\\failedrerun.txt"
mvn test -Dcucumber.options="@target/failedrerun.txt"

Warnungen Ich bekomme:
Mar 28, 2025 2:59:17 PM io.cucumber.core.runtime.FeaturePathFeatureSupplier get
WARNING: No features found at file:/E:/Programming/workspace/SeleniumCucumberMBDD2/target/failedrerun.txt
Mar 28, 2025 2:59:18 PM io.cucumber.core.runtime.FeaturePathFeatureSupplier get
WARNING: No features found at file:/E:/Programming/workspace/SeleniumCucumberMBDD2/target/failedrerun.txt
Mar 28, 2025 2:59:18 PM io.cucumber.core.runtime.FeaturePathFeatureSupplier get
WARNING: No features found at file:/E:/Programming/workspace/SeleniumCucumberMBDD2/target/failedrerun.txt
Mar 28, 2025 2:59:18 PM io.cucumber.core.runtime.FeaturePathFeatureSupplier get
WARNING: No features found at file:/E:/Programming/workspace/SeleniumCucumberMBDD2/target/failedrerun.txt
< /code>
Ausgabe: < /strong>
Als ich versuchte, die fehlgeschlagenen Testcases erneut auszurotten, konnte die Gurke den Feature -Datei -Szenario -Pfad in der Textdatei failedrerun.txt nicht identifizieren. Und nach jedem Mal zeigt es die oben genannten Warnungen und löscht die Datei failedrerun.txt.