Skip to content

Replace a huge SpectralQuantity test with smaller ones#19049

Open
eerovaher wants to merge 1 commit into
astropy:mainfrom
eerovaher:spectralquantity-doppler-conversion-validation-tests
Open

Replace a huge SpectralQuantity test with smaller ones#19049
eerovaher wants to merge 1 commit into
astropy:mainfrom
eerovaher:spectralquantity-doppler-conversion-validation-tests

Conversation

@eerovaher
Copy link
Copy Markdown
Member

Description

I am replacing a test with many pytest.raises() checks with several parametrized tests which all have only a single pytest.raises() check. The advantage of doing this is that the smaller tests can be executed independently from each other, but in current main a failing pytest.raises() check will prevent the following checks from running at all.

Furthermore, I found a bug in SpectralQuantity involving UnitBase.is_equivalent() if unit equivalencies have been enabled, and the changes here make it much easier to write the regression test.

  • By checking this box, the PR author has requested that maintainers do NOT use the "Squash and Merge" button. Maintainers should respect this when possible; however, the final decision is at the discretion of the maintainer that merges the PR.

A single test with several `pytest.raises()` checks has been replaced
with several parametrized tests which all have only a single
`pytest.raises()` check. Previously one failing check prevented all the
following checks from being executed at all, but now they can be tested
independently from each other.
@github-actions
Copy link
Copy Markdown
Contributor

Thank you for your contribution to Astropy! 🌌 This checklist is meant to remind the package maintainers who will review this pull request of some common things to look for.

  • Do the proposed changes actually accomplish desired goals?
  • Do the proposed changes follow the Astropy coding guidelines?
  • Are tests added/updated as required? If so, do they follow the Astropy testing guidelines?
  • Are docs added/updated as required? If so, do they follow the Astropy documentation guidelines?
  • Is rebase and/or squash necessary? If so, please provide the author with appropriate instructions. Also see instructions for rebase and squash.
  • Did the CI pass? If no, are the failures related? If you need to run daily and weekly cron jobs as part of the PR, please apply the "Extra CI" label. Codestyle issues can be fixed by the bot.
  • Is a change log needed? If yes, did the change log check pass? If no, add the "no-changelog-entry-needed" label. If this is a manual backport, use the "skip-changelog-checks" label unless special changelog handling is necessary.
  • Is this a big PR that makes a "What's new?" entry worthwhile and if so, is (1) a "what's new" entry included in this PR and (2) the "whatsnew-needed" label applied?
  • At the time of adding the milestone, if the milestone set requires a backport to release branch(es), apply the appropriate "backport-X.Y.x" label(s) before merge.

@github-actions github-actions Bot added the Close? Tell stale bot that this issue/PR is stale label May 11, 2026
@github-actions
Copy link
Copy Markdown
Contributor

Hi humans 👋 - this pull request hasn't had any new commits for approximately 5 months. I plan to close this in a month if the pull request doesn't have any new commits by then.

In lieu of a stalled pull request, please consider closing this and open an issue instead if a reminder is needed to revisit in the future. Maintainers may also choose to add keep-open label to keep this PR open but it is discouraged unless absolutely necessary.

If this PR still needs to be reviewed, as an author, you can rebase it to reset the clock.

If you believe I commented on this pull request incorrectly, please report this here.

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

Labels

backport-v7.2.x on-merge: backport to v7.2.x Close? Tell stale bot that this issue/PR is stale coordinates no-changelog-entry-needed Refactoring testing

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant