Skip to content

separate time evolution tests into individual @testitems #505

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

ytdHuang
Copy link
Member

@ytdHuang ytdHuang commented Jul 8, 2025

Checklist

Thank you for contributing to QuantumToolbox.jl! Please make sure you have finished the following tasks before opening the PR.

  • Please read Contributing to Quantum Toolbox in Julia.
  • Any code changes were done in a way that does not break public API.
  • Appropriate tests were added and tested locally by running: make test.
  • Any code changes should be julia formatted by running: make format.
  • All documents (in docs/ folder) related to code changes were updated and able to build locally by running: make docs.
  • (If necessary) the CHANGELOG.md should be updated (regarding to the code changes) and built by running: make changelog.

Request for a review after you have completed all the tasks. If you have not finished them all, you can also open a Draft Pull Request to let the others know this on-going work.

Description

Although there is a lot of lines changing in this PR. But basically it's just re-organizing the structure of time evolution runtests.

By using the @testmodule macro (see here for more details), we can divide the current time evolution tests into individual @testitems.

This advantages runtests on both local VS-code extension and CI pipeline:

  • For local VS-code extension, we don't need to run through all time evolution tests while debugging.
  • For CI pipeline, individual @testitems can run in parallel.

I separate it into several code-blocks:

  • @testmodule TESetup, this includes:
    • Global operator and parameter definitions
    • a mesolve solution used for comparing results from mcsolve, ssesolve, and smesolve with mesolve
  • @testitems "sesolve"
  • @testitems "mesolve"
  • @testitems "mcsolve"
  • @testitems "ssesolve"
  • @testitems "smesolve"
  • @testitems "Time-dependent Hamiltonian"
  • @testitems "mcsolve, ssesolve and smesolve reproducibility"

@ytdHuang ytdHuang added the Skip ChangeLog Skip changelog update check in PR label Jul 8, 2025
Copy link

codecov bot commented Jul 8, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.99%. Comparing base (a2ade17) to head (ee3aea4).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #505      +/-   ##
==========================================
- Coverage   94.05%   92.99%   -1.06%     
==========================================
  Files          51       51              
  Lines        3514     3514              
==========================================
- Hits         3305     3268      -37     
- Misses        209      246      +37     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@ytdHuang ytdHuang requested a review from albertomercurio July 8, 2025 06:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Skip ChangeLog Skip changelog update check in PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant