CloudServices/Sync/FxSync/Crossweave2: Difference between revisions
< CloudServices | Sync | FxSync
Jump to navigation
Jump to search
(→Plan) |
(Add some thoughts.) |
||
| Line 5: | Line 5: | ||
* be a stable test suite across upcoming refactorings (War On Sync) | * be a stable test suite across upcoming refactorings (War On Sync) | ||
* provide reliable perf measurements (track regressions, etc.) | * provide reliable perf measurements (track regressions, etc.) | ||
= rnewman desires = | |||
* embed in JS tests? (embedded HTTP server?) | |||
* support fuzz consistency tests | |||
* more operations (restore from bookmarks to test wipe, for example) | |||
= Plan = | = Plan = | ||
Revision as of 18:05, 9 April 2011
Goals
- JavaScript-ability
- improved error reporting (more finegrained, helpful, etc.)
- be a stable test suite across upcoming refactorings (War On Sync)
- provide reliable perf measurements (track regressions, etc.)
rnewman desires
- embed in JS tests? (embedded HTTP server?)
- support fuzz consistency tests
- more operations (restore from bookmarks to test wipe, for example)
Plan
- Rename to Test harness and Profiler for Sync (TPS)
- Python
- ...
- Harness
- [DONE] clone tps repo from crossweave repo
- refactor tests to JSON format
- support JavaScript tests
- refactor verify/verify-not/sync/... to be function calls
- make all test execution async
- move test files themselves to services/sync/tests/tps