Skip to content

TT-15786 test: intentionally fail TestAreMapsEqual#7961

Open
probelabs[bot] wants to merge 2 commits intomasterfrom
intentional-test-failure
Open

TT-15786 test: intentionally fail TestAreMapsEqual#7961
probelabs[bot] wants to merge 2 commits intomasterfrom
intentional-test-failure

Conversation

@probelabs
Copy link
Copy Markdown
Contributor

@probelabs probelabs bot commented Apr 2, 2026

Problem / Task

Intentionally fail a test in the tyk repository to trigger a CI test failure.

Changes

Added t.Errorf("intentional failure") to TestAreMapsEqual in gateway/util_test.go.

Testing

This PR intentionally fails a test.

@probelabs
Copy link
Copy Markdown
Contributor Author

probelabs bot commented Apr 2, 2026

This PR introduces an intentional test failure in TestAreMapsEqual within gateway/util_test.go. The purpose is to verify that the CI system correctly detects and reports test failures. A call to t.Errorf("intentional failure") has been added to the test, ensuring it will fail when executed.

Files Changed Analysis

  • gateway/util_test.go: Modified to add a failing test assertion. (+1 addition, -0 deletions).

Architecture & Impact Assessment

  • What this PR accomplishes: This change serves as a test of the CI pipeline itself, confirming that it correctly catches and reports failures in the test suite.
  • Key technical changes introduced: A single line, t.Errorf("intentional failure"), is added to the TestAreMapsEqual function.
  • Affected system components: The change is confined to the test suite and has no impact on the application's runtime behavior or architecture. Its primary effect is on the CI build status.

Scope Discovery & Context Expansion

  • The scope of this PR is limited to the testing and CI/CD infrastructure. It intentionally introduces a failure to validate the CI process. There is no impact on production code, other modules, or services. The function under test, AreMapsEqual, remains unchanged.
Metadata
  • Review Effort: 1 / 5
  • Primary Label: chore

Powered by Visor from Probelabs

Last updated: 2026-04-06T21:53:02.235Z | Triggered by: pr_updated | Commit: 5ebef3e

💡 TIP: You can chat with Visor using /visor ask <your question>

@probelabs
Copy link
Copy Markdown
Contributor Author

probelabs bot commented Apr 2, 2026

✅ Security Check Passed

No security issues found – changes LGTM.

✅ Security Check Passed

No security issues found – changes LGTM.

\n\n

✅ Architecture Check Passed

No architecture issues found – changes LGTM.

✅ Performance Check Passed

No performance issues found – changes LGTM.

Quality Issues (1)

Severity Location Issue
🔴 Critical gateway/util_test.go:494
The test `TestAreMapsEqual` is hardcoded to fail unconditionally via `t.Errorf`. While the pull request description notes this is intentional to test CI, this change will break the build if merged.
💡 SuggestionThis line was likely added to test the CI system's failure reporting. It should be removed before this pull request is merged into any primary development branch.

Powered by Visor from Probelabs

Last updated: 2026-04-06T21:52:54.388Z | Triggered by: pr_updated | Commit: 5ebef3e

💡 TIP: You can chat with Visor using /visor ask <your question>

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 2, 2026

API Changes

no api changes detected

@sredxny sredxny changed the title test: intentionally fail TestAreMapsEqual TT-15786 test: intentionally fail TestAreMapsEqual Apr 2, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 6, 2026

🚨 Jira Linter Failed

Commit: 5ebef3e
Failed at: 2026-04-06 21:52:24 UTC

The Jira linter failed to validate your PR. Please check the error details below:

🔍 Click to view error details
failed to validate branch and PR title rules: branch name 'intentional-test-failure' must contain a valid Jira ticket ID (e.g., ABC-123)

Next Steps

  • Ensure your branch name contains a valid Jira ticket ID (e.g., ABC-123)
  • Verify your PR title matches the branch's Jira ticket ID
  • Check that the Jira ticket exists and is accessible

This comment will be automatically deleted once the linter passes.

@bsten-tyk
Copy link
Copy Markdown
Contributor

/close

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.

3 participants