Currently being reviewed by a human.

Summary

• Fix false positives for vitest/expect-expect and vitest/no-disabled-tests when using test.extend() to create fixture-based test contexts
• test.extend() is a test factory (creates new test functions with fixtures), not a test call itself, so it should not trigger these lint rules
• Follows the same pattern already used in valid-title rule and aligns with the upstream fix in eslint-plugin-vitest#584

Reproduction

import { describe, expect, test } from 'vitest';

describe('example', () => {
  const it = test.extend<{ result: number }>({
    result: async ({}, use) => {
      await use(42);
    },
  });

  it('works', ({ result }) => {
    expect(result).toBe(42);
  });
});

Before this fix, test.extend() was incorrectly flagged as:

• expect-expect: "Test has no assertions"
• no-disabled-tests: "Test is missing function argument"

Changes

expect_expect.rs

Added extend to the early-return check alongside todo and skip:

if property_name == "extend" {
    return;
}

no_disabled_tests.rs

Added an early-return when the first member is extend (same pattern as valid_title.rs):

if let Some(member) = members.first()
    && member.is_name_equal("extend")
{
    return;
}

Test plan

• Added pass test cases for test.extend() in both Jest and Vitest contexts for expect-expect
• Added pass test cases for test.extend() in both Jest and Vitest contexts for no-disabled-tests
• cargo test -p oxc_linter -- expect_expect passes
• cargo test -p oxc_linter -- no_disabled_tests passes
• cargo clippy -p oxc_linter passes without new warnings

AI Disclosure

This PR was authored with the assistance of Claude Code (AI).
The contributor has reviewed, tested, and validated all changes.