optimization testing
Open
Nobody has claimed this yet.
feature
interface
testing
- Dominant language
- C++
- Stars
- 2.8k
- Forks
- 388
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 15
Description
The optimizers need tests.
The command-line optimization needs tests.
Ben suggested (on stan-dev) using the same kinds of tests as used for optimization in Eigen.
- optimizer tests
- command-line optimization tests
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
Start by locating the optimizer implementation, the command-line optimization entry point, and any existing optimization tests. Review the optimization test patterns in Eigen as suggested in the issue. Done means both the optimizer and command-line optimization have appropriate test coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100