Skip to content

Conversation

@ManuelPalenzuelaDD
Copy link
Contributor

@ManuelPalenzuelaDD ManuelPalenzuelaDD commented Jan 21, 2026

Summary

  • Add documentation for AI-powered flaky test fix requirements: tests need @error.message and @test.source.file

@ManuelPalenzuelaDD ManuelPalenzuelaDD requested review from a team as code owners January 21, 2026 16:04
Document that tests need @error.message and @test.source.file tags
to be eligible for AI-powered fixes, and note that generating fixes
may take some time.

Co-Authored-By: Claude Opus 4.5 <[email protected]>
@ManuelPalenzuelaDD ManuelPalenzuelaDD force-pushed the mpalenzuela/add-ai-flaky-test-fix-requirements branch from 7c1bff1 to e0cbb17 Compare January 21, 2026 16:07
@github-actions
Copy link
Contributor

Preview links (active after the build_preview check completes)

Modified Files


To enable AI-powered flaky test fixes, enable Bits AI Dev Agent for Test Optimization by following the setup instructions in the [Bits AI Dev Agent documentation][16]. Bits AI Dev Agent automatically create fixes for flaky tests detected by Test Optimization.

<div class="alert alert-info">A flaky test must have at least one failed execution that includes both <code>@error.message</code> and <code>@test.source.file</code> tags to be eligible for a fix. Generating a fix may take some time.</div>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you clarify what "some time" entails? Is this a few minutes, an hour?

Copy link
Contributor Author

@ManuelPalenzuelaDD ManuelPalenzuelaDD Jan 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This really depends, it could be from ~30m to couple of hours or more in case of elevated traffic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants