DREAM: Test outputs of different workflow configs
Open
Nobody has claimed this yet.
essdiffraction
- Dominant language
- Python
- Stars
- 1
- Forks
- 3
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 17
Description
Add tests for the different workflow configurations:
- Regression tests with a reference
- Check that the output isn't complete rubbish, see linked issue.
We should really have a test in place that catches this...
Originally posted by @nvaytet in https://github.com/scipp/essdiffraction/pull/145#discussion_r2040253739
Contributor guide
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
No files, tests, or entry points are named in the issue. Start by locating the existing workflow configuration tests and the linked issue or reference outputs, then run the workflows for each configuration. Done means regression results are checked against references and a separate assertion rejects clearly invalid output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100