Add nightly CI workflow for slow-tagged Beauti tests #147 - #148
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix #147
.github/workflows/beauti-tests.yml: runs the beast-fx/Beauti TestFX suite, including tests taggedslowthatci-publish.ymlskips on every push/PR (surefire.excludedGroups=slowin the rootpom.xml). These are headless-JavaFX GUI tests — slower and more flake-prone — so they run nightly (cron '0 13 * * *', 01:00 NZST/02:00 NZDT) plus on-demand viaworkflow_dispatch, rather than gating every PR.mvn -pl beast-fx -am test -Pslow-tests -Dtest='test.beastfx.app.**' -Dsurefire.failIfNoSpecifiedTests=false:-pl beast-fx -amalso pullsbeast-base/beast-pkgmgmtinto the reactor (beast-fx depends on both), so without scoping it would rerun their entire unrelated test suites too.-Dtest='test.beastfx.app.**'restricts execution to the Beauti/TestFX package, which only exists in beast-fx.-Dsurefire.failIfNoSpecifiedTests=falsestops surefire from hard-failing the build in beast-base/beast-pkgmgmt, where that pattern matches zero classes ("No tests were executed!" is an error by default) — those modules should just build and skip tests, not fail the job.DivergenceDatingTestandRateTutorialTest(beast-base) as@Deprecated, pointing to their beast-fx replacementsBeautiDivergenceDatingTest/BeautiRateTutorialTest.Tested in local :
Tests run: 45, Failures: 0, Errors: 0, Skipped: 6