Add standard module tests to TestProcessor #23222
Conversation
The test processor can now check how a module responds to a job with - no Runs or - no LuminosityBlocks or - no Events
The module skeleton code generators will now also create default tests which make use of the TestProcessor.
|
The code-checks are being triggered in jenkins. |
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-23222/4687 |
|
A new Pull Request was created by @Dr15Jones (Chris Jones) for master. It involves the following packages: FWCore/Skeletons @cmsbuild, @smuzaffar, @Dr15Jones can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
|
please test |
|
+1 |
|
The tests are being triggered in jenkins. |
|
This pull request is fully signed and it will be integrated in one of the next master IBs after it passes the integration tests. This pull request will now be reviewed by the release team before it's merged. @davidlange6, @slava77, @smuzaffar, @fabiocos (and backports should be raised in the release meeting by the corresponding L2) |
|
+1 The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: |
|
Comparison job queued. |
|
Comparison is ready Comparison Summary:
|
|
+1 the differences in tests look induced by overlapping merged PRs |
The TestProcessor now provides standard tests for non-event processing. These cover the cases where a job does not process any Runs, or any LuminosityBlocks or any Events.
In addition, the module skeleton code generators have been updated to autogenerate tests for the module.