能否将Cucumber场景钩子（@Before、@After）与Glue代码分包存储？如何实现？

Absolutely! Cucumber fully supports separating scenario hooks (like @Before, @After, @BeforeStep, etc.) from your business-focused glue code packages. This is a fantastic way to keep your test framework modular—centralizing reusable hooks in your core framework while keeping step definitions tied to your project's specific features. Here's how to set it up:

Step 1: Organize Your Hooks in a Framework Package #

First, move all your hook classes into a dedicated package within your main framework code. For example:

• Framework hooks: com.yourcompany.testframework.hooks
• Project-specific glue code: com.yourcompany.yourproject.stepdefinitions

Your hook class might look like this (Java example):

package com.yourcompany.testframework.hooks;

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

public class FrameworkHooks {

    @Before
    public void setupTestEnvironment() {
        // Reusable setup logic (e.g., initialize driver, load config)
        System.out.println("Running framework-level before hook");
    }

    @After
    public void teardownTestEnvironment() {
        // Reusable teardown logic (e.g., quit driver, clean up resources)
        System.out.println("Running framework-level after hook");
    }
}

Step 2: Configure Cucumber to Scan Both Packages #

You need to tell Cucumber where to find both your glue code and your framework hooks. The method depends on how you're running Cucumber:

Option A: Using @CucumberOptions Annotation (Java) #

In your test runner class, add both packages to the glue parameter (comma-separated):

package com.yourcompany.yourproject.runners;

import io.cucumber.junit.Cucumber;
import io.cucumber.junit.CucumberOptions;
import org.junit.runner.RunWith;

@RunWith(Cucumber.class)
@CucumberOptions(
    features = "src/test/resources/features",
    glue = {"com.yourcompany.yourproject.stepdefinitions", "com.yourcompany.testframework.hooks"},
    plugin = {"pretty", "html:target/cucumber-reports"}
)
public class TestRunner {}

Option B: Using Properties File #

If you prefer using a cucumber.properties file (placed in src/test/resources), add the cucumber.glue property with both packages:

cucumber.glue=com.yourcompany.yourproject.stepdefinitions,com.yourcompany.testframework.hooks
cucumber.features=src/test/resources/features

Option C: For JavaScript/TypeScript #

In your cucumber.js configuration file, use the --require flag to specify both directories:

module.exports = {
  default: {
    paths: ['features/**/*.feature'],
    require: [
      './framework/hooks/**/*.js',
      './step-definitions/**/*.js'
    ]
  }
}

Step 3: Verify the Setup #

Run your Cucumber tests and check if the framework hooks execute as expected. You should see your hook logs (or side effects) alongside your step definition logic.

Key Notes #

• Hooks don't need any special inheritance or interfaces—just ensure they have the correct Cucumber annotations (@Before, @After, etc.).
• You can use tag expressions on hooks to control when they run (e.g., @Before("@smoke")), even if they're in a separate package.
• This approach works for all Cucumber-supported languages (Java, JS/TS, Ruby, Python, etc.)—the core idea is telling Cucumber to scan multiple locations for glue code and hooks.

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