What is @Test(enabled=false) in TestNG and when should you use it?

@Test(enabled = false) // disabled — will not run
public void brokenFeatureTest() {
    // Known defect: JIRA-456 — payment gateway returns 500
    // Re-enable when JIRA-456 is fixed
    driver.findElement(By.id("payBtn")).click();
    Assert.assertEquals(getPaymentStatus(), "Success");
}

@Test // enabled = true is default
public void workingTest() {
    Assert.assertTrue(driver.getTitle().contains("Home"));
}

// 1. Known production bug — test would always fail, blocking CI
@Test(enabled = false, description = "Disabled: JIRA-789 — search returns wrong results")
public void searchFilterTest() { ... }

// 2. Feature in development — not ready yet
@Test(enabled = false, description = "WIP: Checkout flow not implemented")
public void checkoutTest() { ... }

// 3. Test is environment-specific — not applicable to current environment
@Test(enabled = false, description = "Only runs on staging — disabled for prod")
public void dataResetTest() { ... }

public class ConditionalEnableTransformer implements IAnnotationTransformer {

    @Override
    public void transform(ITestAnnotation annotation, Class testClass,
                          Constructor testConstructor, Method testMethod) {

        String env = System.getProperty("env", "staging");

        // Disable prod-data-reset tests on production
        if (testMethod != null && testMethod.isAnnotationPresent(ProdOnly.class)
                && !env.equals("production")) {
            annotation.setEnabled(false);
        }
    }
}

@Test(
    enabled = false,
    description = "DISABLED: JIRA-1234 — dropdown broken on Chrome 120. Re-enable after hotfix."
)
public void dropdownTest() { ... }