Skip to content

Fail builds on all Pester failures - #53

Merged
lipkau merged 1 commit into
masterfrom
codex/fail-on-pester-block-container-failures
Sep 11, 2026
Merged

lipkau merged 1 commit into
masterfrom
codex/fail-on-pester-block-container-failures

Conversation

@lipkau

@lipkau lipkau commented Sep 10, 2026 •

Copy link
Copy Markdown
Member

Summary

  • fail module tests when Pester reports failed blocks or containers
  • add a build-script regression check for all three Pester 5 counts

Context

This applies the failure gate from AtlassianPS/ConfluencePS#256, contributed by @nohwnd.

Validation

Invoke-Build -Task Lint, Build, Test

945 passed, 19 skipped.

Release intent

Build infrastructure only. No package release.

Related changes

Count setup and discovery failures in build gates so Pester cannot report a failed run while the build exits successfully.

Co-authored-by: Jakub Jareš <me@jakubjares.com>
@lipkau lipkau added the release:none No release note or version impact label Sep 10, 2026
lipkau added a commit to AtlassianPS/JiraPS that referenced this pull request Sep 11, 2026
## Summary

- report failed tests, blocks, and containers separately in the parallel
runner
- use their combined count for success, NUnit suite status, and process
exit
- record block and container failures as NUnit errors without inflating
failed test counts

## Context

This applies the failure gate from AtlassianPS/ConfluencePS#256,
contributed by @nohwnd.

## Validation

- `Invoke-Build -Task Lint, Build, Test`
- explicit `Invoke-Build -Task Test` exit code: 0
- generated results: 4,624 checks, 0 failures, 0 errors, 69 skipped
- container-only negative fixture: exit code 1 with one failed container

## Release intent

Test infrastructure only. No package release.

## Related changes

- AtlassianPS/ConfluencePS#256
- AtlassianPS/AtlassianPS.Configuration#53
- AtlassianPS/AtlassianPS.Standards#65
- AtlassianPS/JiraAgilePS#55
- #716

Co-authored-by: Jakub Jareš <me@jakubjares.com>
lipkau added a commit to AtlassianPS/JiraAgilePS that referenced this pull request Sep 11, 2026
## Summary

- fail integration tests when Pester reports failed blocks or containers
- add a build-script regression check for all three Pester 5 counts

## Context

This applies the failure gate from AtlassianPS/ConfluencePS#256,
contributed by @nohwnd.

## Validation

`Invoke-Build -Task Build, Test`

603 passed.

## Release intent

Build infrastructure only. No package release.

## Related changes

- AtlassianPS/ConfluencePS#256
- AtlassianPS/AtlassianPS.Configuration#53
- AtlassianPS/AtlassianPS.Standards#65
- #55
- AtlassianPS/JiraPS#716

Co-authored-by: Jakub Jareš <me@jakubjares.com>
lipkau added a commit to AtlassianPS/AtlassianPS.Standards that referenced this pull request Sep 11, 2026
## Summary

- count failed Pester tests, blocks, and containers in lint and
module-test gates
- preserve the Pester 4 `ContainersFailedCount` compatibility fallback
- cover test, block-only, container-only, and legacy container failures

## Context

This applies the failure gate from AtlassianPS/ConfluencePS#256,
contributed by @nohwnd.

## Validation

`Invoke-Build -Task Lint, Build, Test`

The test suite passed with 95 tests passed and 35 not run. Lint and
PSScriptAnalyzer also passed.

## Release intent

Patch release so downstream build scripts can consume the corrected
gates.

## Related changes

- AtlassianPS/ConfluencePS#256
- AtlassianPS/AtlassianPS.Configuration#53
- #65
- AtlassianPS/JiraAgilePS#55
- AtlassianPS/JiraPS#716

Co-authored-by: Jakub Jareš <me@jakubjares.com>
@lipkau
lipkau merged commit c912213 into master Sep 11, 2026
10 checks passed
@lipkau
lipkau deleted the codex/fail-on-pester-block-container-failures branch September 11, 2026 06:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

release:none No release note or version impact

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant