Add unit-tests for scaling workflow steps.
Open
Nobody has claimed this yet.
essnmx
good first issue
- Dominant language
- Python
- Stars
- 1
- Forks
- 3
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 17
Description
The scaling workflow steps and test datasets are still being investigated and updated relatively frequently.
We have tests for file IO functionalities, but we still don't have any tests for each steps.
Once we fix mandatory steps, we shall write proper tests for them.
I'm opening this issue so that we don't forget....
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
Review the scaling workflow steps and the current test datasets, then compare them with the existing file IO tests. Identify the mandatory steps first; done means each fixed mandatory step has a focused unit test using an appropriate dataset.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100