Auto-tools/Projects: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 8: | Line 8: | ||
| style="background:#efefef" | '''Status''' | | style="background:#efefef" | '''Status''' | ||
|- | |- | ||
| [[ | | [[Ateam/Winmo/1.0/todo| Android Automation]] | ||
| Jmaher & Ctalbert | | Jmaher & Ctalbert | ||
| Create full test integration for Android using the remote tests framework, support RelEng during roll out of that framework. | | Create full test integration for Android using the remote tests framework, support RelEng during roll out of that framework. | ||
| Line 79: | Line 79: | ||
| | | | ||
| | | | ||
|- | |||
| [[auto-tools/Projects/Loderunner|The Great Refactor (Loderunner)]] | |||
| all | |||
| Continual improvement step to refactor core common functionality into a set of shared components that can be used across the test harnesses. | |||
| | |||
| WAITING FOR TAKEOFF (early design) | |||
|} | |} | ||
Revision as of 20:41, 19 May 2010
| Description | Leader | Goal | ETA | Status |
| Android Automation | Jmaher & Ctalbert | Create full test integration for Android using the remote tests framework, support RelEng during roll out of that framework. | IN FLIGHT | |
| Integrate Mozmill into Buildbot | Jhammel | Integrate Mozmill test harness into Buildbot automation system | IN FLIGHT | |
| Universal Manifest Format for Tests | alice | Standardize manifest format for unit tests (+ talos?) | IN FLIGHT | |
| Improving Bugzilla Review process | Jmaher | Move REST API into MPT and improve the review process in bugzilla using Splinter or ReviewBoard | TAKING OFF | |
| Measure AddOn startup performance | Harth | Design and prototype a system for automating measuring addon startup performance, make it generalizable to do any type of "generated profile" testing, aka Dirty Harry | TAKING OFF | |
| Grafx Bot | Jgriffin | Create a crowd-source extension for graphics subsystem testing | TOUCH AND GO | |
| CrossWeave | Jgriffin | A new automated test framework for testing client/server interactions in Weave, using a Firefox extension | IN FLIGHT | |
| Crash & Valgrind Automation UI v2 | Harth & Bc | Create a UI that aids in correlation of crash and test data to help diagnose problems in the product. | IN FLIGHT | |
| Mozmill 1.5 | Ctalbert & Jgriffin | Fixes and a UI refresh plus new logging backend for Mozmill | IN FLIGHT | |
| Crash Automation Rollout | Bc | Work with IT to roll out the crash & valgrind automation system to a set of production machines in the colo | IN FLIGHT | |
| Purify Integration | Jgriffin | Integrate the new Purify machine into the larger Crash Automation and testing infrastructure | WAITING FOR TAKEOFF (on IT) | |
| Profile Manager Replacement | Jhammel | The profile manager is going away, we will need to build a better tool for a replacement. | ||
| The Great Refactor (Loderunner) | all | Continual improvement step to refactor core common functionality into a set of shared components that can be used across the test harnesses. | WAITING FOR TAKEOFF (early design) |
Proposed Projects
- Our own Big Ideas
- Integrate CoScriptor natural language with Mozmill
- Weave Thick Client Automation
Completed Projects
- Crash and Valgrind test Automation system
- Mozmill 1.4
- Remote (aka Mobile) Test Refactoring for Mochitest and Reftest and XPCShell
- Crash/Valgrind Automation UI 1.0
- QA Companion tool
- OOPP test infrastructure and NPAPI test creation
- JS Reftest test suite
Legend
Using the airplane metaphors that the Firefox team started with. Let me know if you have a better suggestion.
- (BLANK) - Not started
- WAITING FOR TAKEOFF - Project blocked by an external dependency
- TAKING OFF - Beginning design process, early work
- IN FLIGHT - In active development
- TOUCH AND GO - Find/fix mode. In early testing. (This refers to practice landings that pilots do)
- LANDED - Done
Template
We might change this in the future, but to get started we can use the Firefox Project Template if it helps create pages for these projects.