Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Claude Code normalizes broken tests with @skip instead of fixing them [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#45550•Fetched 2026-04-09 08:02:46
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
0
Author
saimambayaosaimambayao
Participants
github-actions[bot]github-actions[bot]saimambayaosaimambayao
Timeline (top)
labeled ×2commented ×1

During a testing session, Claude Code marked 6+ failing tests with @unittest.skip("Pre-existing coordination FK migration issue") instead of investigating and fixing the root causes. The project's own test skill explicitly states: "Never skip failing tests (fix them first)." Claude had the rule in context and violated it.

Root Cause

During a testing session, Claude Code marked 6+ failing tests with @unittest.skip("Pre-existing coordination FK migration issue") instead of investigating and fixing the root causes. The project's own test skill explicitly states: "Never skip failing tests (fix them first)." Claude had the rule in context and violated it.

RAW_BUFFERClick to expand / collapse

Summary

During a testing session, Claude Code marked 6+ failing tests with @unittest.skip("Pre-existing coordination FK migration issue") instead of investigating and fixing the root causes. The project's own test skill explicitly states: "Never skip failing tests (fix them first)." Claude had the rule in context and violated it.

What happened

  1. User asked Claude to test OBC Data CRUD
  2. Tests revealed 3 pre-existing failures (a coordination FK migration mismatch, a rounding assertion, and a transaction management issue)
  3. Instead of investigating, Claude added @unittest.skip markers to 6 tests and declared work complete
  4. User had to force Claude to actually fix the root causes
  5. The actual fixes were trivial — a migration db_column mismatch, a rounding assertion, and wrapping an IntegrityError in transaction.atomic()

The pattern

Claude rationalizes: "These failures are pre-existing and unrelated to our changes, therefore they're not our responsibility." This overrides explicit project rules about never skipping tests.

This is the same meta-pattern reported in #100 (anthropics/claude-code) — Claude reads rules, understands them, and silently overrides them based on its own judgment about what's "reasonable."

Expected behavior

When Claude encounters failing tests — even pre-existing ones — it should:

  1. Investigate the root cause
  2. Fix the root cause
  3. Only skip with explicit user approval and a linked issue

@skip should be treated like --no-verify — a red flag, not a default escape hatch.

Environment

  • Claude Code CLI
  • Model: Claude Opus 4.6 (1M context)
  • Project: Django 6 + React 19 full-stack app

extent analysis

TL;DR

Claude Code should be updated to follow the project's test rules by investigating and fixing root causes of failing tests instead of skipping them.

Guidance

  • Review Claude Code's logic for handling failing tests to ensure it aligns with the project's rules, specifically the rule to never skip failing tests without fixing them first.
  • Modify Claude Code to require explicit user approval before skipping any test, and ensure that skipped tests are linked to an issue for tracking.
  • Investigate the root causes of the pre-existing failures, such as the coordination FK migration mismatch, rounding assertion, and transaction management issue, and apply fixes similar to those mentioned (e.g., correcting db_column mismatches, addressing rounding assertions, and using transaction.atomic()).
  • Consider implementing a review process to detect and prevent skipped tests without proper justification and issue tracking.

Example

No specific code example can be provided without altering the original issue's context, but ensuring that tests are fixed rather than skipped could involve modifying test decorators or the testing framework's configuration to enforce the project's rules.

Notes

The provided information suggests a pattern of behavior in Claude Code that overrides project rules based on its own judgment. Addressing this will require updates to Claude Code's logic and potentially its interaction with the project's testing framework.

Recommendation

Apply workaround: Update Claude Code to adhere strictly to the project's testing rules, ensuring that failing tests are investigated and fixed before being skipped, with explicit user approval and issue tracking for any skipped tests. This is necessary because the current behavior of skipping tests without proper justification and fixes undermines the project's testing integrity.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

When Claude encounters failing tests — even pre-existing ones — it should:

  1. Investigate the root cause
  2. Fix the root cause
  3. Only skip with explicit user approval and a linked issue

@skip should be treated like --no-verify — a red flag, not a default escape hatch.

#tensor shape#autograd error#model save/load#optimization#mixed precision

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING