devs/cproof
1
2
Fork 1
Code Issues 43 Pull Requests 6 Actions Packages Projects 1 Releases Wiki Activity

Add fault injection testing CI infrastructure #73

New Issue
Closed
opened 2026-01-21 15:44:52 +00:00 by jabber.developer2 · 0 comments
jabber.developer2 commented 2026-01-21 15:44:52 +00:00
Collaborator
Copy Link

Summary

Add infrastructure for fault injection testing to verify that tests correctly detect failures and CI pipeline properly reports them.

Motivation

Currently there's no automated way to verify that:

  1. Unit tests actually fail when expected behavior is broken
  2. CI pipeline correctly reports test failures
  3. Cached Docker images don't mask test failures

Requirements

  1. Test failure verification at CI startup

    • Create a deliberately failing test
    • Verify exit code is non-zero
    • Abort CI if failure detection is broken

  2. Parallel failure detection verification

    • Simulate parallel test execution with mixed results
    • Verify that failures in background processes are caught

  3. Run automatically on every CI build

    • No manual trigger needed
    • Clear output showing verification status

Acceptance Criteria

  • CI aborts with clear error if test failures are not detected
  • Parallel test failures are properly caught
  • Verification runs before actual tests
### Summary Add infrastructure for fault injection testing to verify that tests correctly detect failures and CI pipeline properly reports them. ### Motivation Currently there's no automated way to verify that: 1. Unit tests actually fail when expected behavior is broken 2. CI pipeline correctly reports test failures 3. Cached Docker images don't mask test failures ### Requirements 1. **Test failure verification at CI startup** - Create a deliberately failing test - Verify exit code is non-zero - Abort CI if failure detection is broken 2. **Parallel failure detection verification** - Simulate parallel test execution with mixed results - Verify that failures in background processes are caught 3. **Run automatically on every CI build** - No manual trigger needed - Clear output showing verification status ### Acceptance Criteria - [ ] CI aborts with clear error if test failures are not detected - [ ] Parallel test failures are properly caught - [ ] Verification runs before actual tests
jabber.developer2 added this to the Plans (2025-2026) project 2026-01-21 15:44:59 +00:00
jabber.developer2 self-assigned this 2026-01-21 15:45:04 +00:00
jabber.developer2 added reference feat/parallel-tests-clean 2026-01-21 15:45:14 +00:00
jabber.developer2 added the
Kind/Testing
 label 2026-01-21 15:45:31 +00:00
jabber.developer2 changed title from Add fault injection testing infrastructure to Add fault injection testing CI infrastructure 2026-01-21 15:50:34 +00:00
jabber.developer moved this to Done in Plans (2025-2026) on 2026-01-21 15:55:10 +00:00
Sign in to join this conversation.
feat/parallel-tests-clean
Branches Tags
Labels
Clear labels
Compat/Breaking
Breaking change that won't be backward compatible
Kind/Bug
Something is not working
Kind/Documentation
Documentation changes
Kind/Enhancement
Improve existing functionality
Kind/Feature
New functionality
Kind/Security
This is security issue
Kind/Testing
Issue or pull request related to testing
Priority
Critical
1
The priority is critical
Priority
High
2
The priority is high
Priority
Low
4
The priority is low
Priority
Medium
3
The priority is medium
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Abandoned
3
Somebody has started to work on this but abandoned work
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
No Label
Kind/Testing
Milestone
No items
No Milestone
Projects
Clear projects
No project Plans (2025-2026)
Assignees
Clear assignees
admin jabber.developer jabber.developer2
No Assignees jabber.developer2
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: devs/cproof#73
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?