Move ManualScheduler (for tests) to separate test-artifact
See original GitHub issueManualScheduler
, a scheduler used for testing that allows for manual triggering of activites, currently lives in the main maven artifact db-scheduler
. It is a leftover from before db-scheduler was a multi-module maven project. We should move the package com.github.kagkarlsson.scheduler.testhelper
into a new maven artifact db-scheduler-test
so that it can be included specifically for tests with <scope>test</scope>
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
Delete test artifacts in Azure Boards - Microsoft Learn
Removes the deleted test artifact from the test case management (TCM) data store and deletes the underlying work item; Runs a job to...
Read more >How to create a jar containing test classes - Apache Maven
Create a separate project with the test-classes. ... Move the sources files from src/test/java you want to share from the original project ...
Read more >Managing test artifact sections - Jazz.net
Open a test plan, test case, test suite, or keyword. From the list of test artifact sections, click Manage Sections to open the...
Read more >Deleting and restoring test artifacts - IBM
Artifact type Delete support Restore support Permanent delete support
Attachments Yes Yes Yes
Build definitions and build records Yes Yes Yes
Category Yes Yes Yes
Read more >Unit test reports - GitLab Docs
The failed tests are listed as a string with the tests separated by spaces. To copy the name of a single failed test:...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I tried clarifying the description. Makes sense?
I think there is no need for that. I did not put much work on that. Maybe we could try to add a maven shade plugin to exclude some classes from the final artifact. I’m not sure what would be the impact to the project, but that’s an option.