CloudServices/Sync/FxSync/Crossweave2: Difference between revisions
< CloudServices | Sync | FxSync
Jump to navigation
Jump to search
(→Plan) |
No edit summary |
||
Line 6: | Line 6: | ||
* provide reliable perf measurements (track regressions, etc.) | * provide reliable perf measurements (track regressions, etc.) | ||
= | = Plan for Crossweave / TPS 2.0 = | ||
* Rename to '''Test harness and Profiler for Sync''' (TPS) | * Rename to '''Test harness and Profiler for Sync''' (TPS) | ||
Line 31: | Line 25: | ||
** make all test execution async | ** make all test execution async | ||
** move test files themselves to services/sync/tests/tps | ** move test files themselves to services/sync/tests/tps | ||
= Plan beyond TPS 2.0 = | |||
* Perf instrumentation | |||
** event loop blocking | |||
** memory usage | |||
** object allocations | |||
= rnewman desires = | |||
* embed in JS tests? (embedded HTTP server?) | |||
* support fuzz consistency tests | |||
* more operations (restore from bookmarks to test wipe, for example) |
Revision as of 20:02, 26 May 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.)
Plan for Crossweave / TPS 2.0
- Rename to Test harness and Profiler for Sync (TPS)
- Python
- [DONE] refactor using Mozmill 2.0
- [DONE] remove support for the fx-sync repo and the the XPI version of sync
- [DONE] improve error handling for timeout conditions and python exceptions
- [DONE] connect to autolog
- [DONE] convert config and manifest file format to JSON
- remove result reporting to the MySQL db on brasstacks
- 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
Plan beyond TPS 2.0
- Perf instrumentation
- event loop blocking
- memory usage
- object allocations
rnewman desires
- embed in JS tests? (embedded HTTP server?)
- support fuzz consistency tests
- more operations (restore from bookmarks to test wipe, for example)