如何在Cucumber中跳过Scenario执行？前序失败时跳过后序可行吗？

Absolutely, this is totally achievable—most modern test frameworks have built-in features or simple workarounds to handle this exact scenario. The core idea is to track the execution status of the previous Scenario, then check that status before running the next one to decide whether to skip it.

Here’s how you can implement this across common frameworks:

Cucumber (since you specifically referenced "Scenario") #

Cucumber’s hooks are perfect for this. You can use a thread-local variable (to avoid issues with parallel testing) to track if the last Scenario passed, then use a @Before hook to skip the current Scenario if the previous one failed.

Example in Java:

import io.cucumber.java.After;
import io.cucumber.java.Before;
import io.cucumber.java.Scenario;

public class ScenarioDependencyHooks {
    // ThreadLocal ensures safety for parallel test runs
    private static final ThreadLocal<Boolean> previousScenarioPassed = ThreadLocal.withInitial(() -> true);

    @Before
    public void checkPreviousScenarioStatus(Scenario scenario) {
        if (!previousScenarioPassed.get()) {
            scenario.skip("Skipping this scenario because the previous one failed");
        }
    }

    @After
    public void updateScenarioStatus(Scenario scenario) {
        previousScenarioPassed.set(scenario.isPassed());
    }
}

TestNG #

For TestNG, you can use a test listener to track failure status, then check that status in a @BeforeMethod hook to skip subsequent tests (which map to your Scenarios).

First, create a listener:

import org.testng.ITestContext;
import org.testng.ITestResult;
import org.testng.TestListenerAdapter;

public class ScenarioSkipListener extends TestListenerAdapter {
    @Override
    public void onTestFailure(ITestResult tr) {
        ITestContext context = tr.getTestContext();
        // Store failure status in the test context
        context.setAttribute("previousScenarioFailed", true);
    }

    @Override
    public void onTestSuccess(ITestResult tr) {
        ITestContext context = tr.getTestContext();
        context.setAttribute("previousScenarioFailed", false);
    }
}

Then use it in your test class:

import org.testng.SkipException;
import org.testng.annotations.BeforeMethod;
import org.testng.annotations.Listeners;
import org.testng.annotations.Test;

@Listeners(ScenarioSkipListener.class)
public class ScenarioTestSuite {
    @BeforeMethod
    public void checkPreviousScenarioStatus(ITestContext context) {
        Boolean previousFailed = (Boolean) context.getAttribute("previousScenarioFailed");
        if (previousFailed != null && previousFailed) {
            throw new SkipException("Skipping scenario: previous scenario failed");
        }
    }

    @Test
    public void firstScenario() {
        // Your test logic here
    }

    @Test
    public void secondScenario() {
        // Your test logic here
    }
}

JUnit 5 #

In JUnit 5, you can build a custom extension to track test execution status. The extension will store whether the last test failed, and you can check this state in a @BeforeEach method to skip subsequent tests.

Key Things to Keep in Mind #

• Parallel Testing: Always use thread-local storage for status tracking if you run tests in parallel—this prevents cross-thread interference that could break your skip logic.
• Suite Reset: Add logic to reset the status at the start of your test suite, so a failure in one run doesn’t incorrectly skip tests in the next.
• Clear Messaging: Include descriptive skip messages so anyone reviewing test results immediately understands why a scenario was skipped.

内容的提问来源于stack exchange，提问作者Shashank Bharide