Add more test coverage
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 270
- Forks
- 123
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 3
Description
Description
Unit tests
- test that the Solution object contains the right info
-
objectives -
constraints -
variables - can be correctly cold-started (document this!)
-
- FD/CS tests
Integration tests
- MPI tests
- fake COMM object works on single proc
- optimization in parallel runs fine, with only the root proc running the optimization itself but calling the objective/sensitivity functions on all procs
- parallel DV/constraint adding works as expected
- other optimization problems?
- FD/CS tests
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 Solution object and the existing unit tests, then review the MPI integration-test entry points and the fake COMM behavior. Cover the unchecked Solution fields, cold-start behavior, and MPI cases listed in the issue, with passing unit and integration tests as the completion criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- distributed-systems, testing-qa
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100