Unified developer test(s) platform
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 0
- Forks
- 8
- Avg merge
- 7h 21m
- Merged PRs (30d)
- 3
Description
It would be ideal to have a unified testing platform for trigger development.
This could take the form of a single python script where the developer can configure that test to confirm the functionality of their new feature produces the expected result. This could also update a spreadsheet/table and link to readme to automate logging.
Could include:
- date and time
- configuration
- used branches
- result: PASS/FAIL
- X/TOT passed
- path to trigger log
- ensure no 'warning' or 'error' messages
The trigger log / other logs should be used as input for the test. The test should be run with DAQ configuration generated with the '--debug' flag to ensure maximal logging.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the proposed trigger-log inputs and DAQ configurations generated with the --debug flag. Define the unified test workflow around the requested date, configuration, branches, PASS/FAIL result, pass count, log path, and warning/error checks, with its results linked from the README or recorded in a table.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100