Ticket #22 (closed verification: worksforme)
build test suite for mystic core features
| Reported by: | mmckerns | Owned by: | mmckerns |
|---|---|---|---|
| Priority: | major | Milestone: | mystic-0.2a2 |
| Component: | mystic.tests | Keywords: | |
| Cc: |
Description
build test suite for mystic core features; utilize several of the examples, but add assert statements
add both failure and success tests
Change History
comment:2 Changed 6 years ago by mmckerns
- Milestone changed from mystic-dev to mystic-0.2a1
split off failure suite to ticket #89
test suite should concentrate on performance and accuracy
comment:4 Changed 6 years ago by mmckerns
Definitions...
- accuracy: how close are the results to the known solution?
- performance: what was the clock-time, # of iterations, and # of function evaluations?
comment:5 Changed 6 years ago by mmckerns
should build a suite of "known" (i.e. cited) problems, then obtain performance and accuracy information. run against the different solvers.
Additional: Write up results results of accuracy & performance tests. Show results for default settings and "best" settings. Demonstrate impact of using different termination conditions, and also highlight the ease of swapping termination and solvers.
comment:6 Changed 6 years ago by mmckerns
- Status changed from assigned to closed
- Resolution set to worksforme
added tests to check results in r424, and tests to check termination conditions in r423. SOW tests were added in r372. Should there also be a "strategy" test suite? or more testing of "tools"?
There are still several tests that should be recast to use unittest, however the desired functionality otherwise is tested... so I'm going to mark this as closed.
