User Story #43 (closed)
Integration tests should behave more properly.
| Reported by: | jamoore | Owned by: | jamoore |
|---|---|---|---|
| Priority: | major | Milestone: | 3.0-M2 |
| Component: | Deployment | Keywords: | iteration4,testing |
| Cc: | sfrank | Story Points: | n.a. |
| Sprint: | n.a. | Importance: | n.a. |
| Total Remaining Time: | n.a. | Estimated Remaining Time: | n.a. |
Change History (5)
comment:1 Changed 18 years ago by jmoore
comment:2 Changed 18 years ago by jmoore
- Cc sfrank added
- Milestone set to cycle1
This is tied to the installation of CruiseControl? #74. Let's make a deal, once CruiseControl? is setup and things are failing, I'll guarantee to have this done.
comment:3 Changed 18 years ago by jmoore
- Keywords iteration4 added
- Status changed from new to assigned
Server tests are doing quite well. I'll move on to client tests next, and this should then clear up.
comment:4 Changed 18 years ago by jmoore
- Keywords testing added
- Resolution set to fixed
- Status changed from assigned to closed
Didn't get a chance to fix all the client tests (and in fact the ApiConstraintChecker? changes from #192 caused some server tests to regress) but in general adding a call to "deploy" to /app's integration build target now lets the entire test suite (java omero integration) run through.
/server is currently the only component that fails on test failure or skip, but as soon as all tests pass, we can make the whole test suite strict.
In general, I'd say this is "well-behaved". Now it's just a matter of fixing the tests. Closing. Open more specific tickets if need be.
#64 should make all integration tests behave initially more properly. After that, it'll need to be determined what sort of test groups ("launch", "init", "deploy", etc.) are needed.