Incorporate running c302 "unit tests" and "integration tests"
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.1k
- Forks
- 244
- PR merge metrics
- No merged PRs in 30d
Description
Proof of concept tests can begin with executing the muscle model tests. Once executed, a figure of simulated versus real data should appear in the output directory.
Beyond this, analyzing the output of the simulation as an "integration" test can be incorporated. Some new issues may need to be spawned to capture this part.
cc: @rgerkin
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 locating the muscle model tests and the c302 test execution entry point. Run the proof-of-concept tests and inspect the output directory for a figure comparing simulated and real data. The immediate outcome is executable unit tests that produce this figure; integration-test analysis is described as future work for separate issues.
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
- 25/100