Skip to content

tests: test_510/issue_519: needs fixing / should be removed #6814

Closed

Description

@blueyed

See #6813 for more details.

Activity

  1. symonk commented on May 24, 2020

    @symonk
    Member

    @RonnyPfannschmidt / @nicoddemus / @bluetech can we close this? looks like a PR was merged some time ago removing test_510

  2. RonnyPfannschmidt commented on May 24, 2020

    @RonnyPfannschmidt
    Member

    This does not look like it was merged from the downstream to the main repo, im on mobile and can't verify

  3. symonk commented on May 24, 2020

    @symonk
    Member

    keen eye, your right it was a fork :) sorry about that

  4. Zac-HD commented on Jul 22, 2026

    @Zac-HD
    Member

    Closing as resolved: the concern here was that test_510/test_issue519.py's assertion was brittle and broke after path-reporting changes (see the never-merged fix proposed in #6813), and possibly that the file should be removed; on current main test_510 no longer exists anywhere in the repo, and testing/examples/test_issue519.py already uses the robust form proposed in #6813 (pytester.copy_example("issue_519.py") + res.assert_outcomes(passed=8)), verified passing.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    type: bugproblem that needs to be addressedtype: selftestsa problem in the tests of pytest

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions