Skip to content

test(fixtures): always run e2e tests in very verbose mode for test failure debugging #1258

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

codejedi365
Copy link
Contributor

Purpose

Rationale

How did you test?

How to Verify


PR Completion Checklist

  • Reviewed & followed the Contributor Guidelines

  • Changes Implemented & Validation pipeline succeeds

  • Commits follow the Conventional Commits standard
    and are separated into the proper commit type and scope (recommended order: test, build, feat/fix, docs)

  • Appropriate Unit tests added/updated

  • Appropriate End-to-End tests added/updated

  • Appropriate Documentation added/updated and syntax validated for sphinx build (see Contributor Guidelines)

@codejedi365 codejedi365 force-pushed the test/ensure-debug-logging-on-failure branch 2 times, most recently from 72dfdab to 8f1420a Compare May 25, 2025 19:51
@codejedi365 codejedi365 force-pushed the test/ensure-debug-logging-on-failure branch from 8f1420a to 8fb3e7b Compare May 25, 2025 19:55
@codejedi365 codejedi365 merged commit d099c20 into python-semantic-release:master May 25, 2025
13 checks passed
@codejedi365 codejedi365 deleted the test/ensure-debug-logging-on-failure branch May 25, 2025 20:15
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.

1 participant