Basic Integration Tests for trigger: Automation
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 0
- Forks
- 8
- Avg merge
- 7h 21m
- Merged PRs (30d)
- 3
Description
As part of the code development, it is compulsory to run basic integration tests. These are located:
dfmodules/integtest.
It's currently agreed that at least these should be run:
- minimal_system_quick_test.py
- fake_data_producer_test.py
These should be run for each new fix/feature.
The idea is to automate running these when making PR, adding the result/log to a spreadsheet or table. This can be linked via readme, showing tests taken in the last X months.
Optionally, it would be great to also run 3ru_3df_multirun_test.py, however, this requires significant computing resources, so may not be possible (to automate).
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 with integtest/minimal_system_quick_test.py and integtest/fake_data_producer_test.py, then inspect how pull-request automation is configured in the repository. Done means both tests run for each new fix or feature, with their results or logs recorded in a spreadsheet or table linked from the README. Treat integtest/3ru_3df_multirun_test.py as optional because it requires significant computing resources.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, python
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100