QA/Execution/Web Testing/Goals/2009/Q4
< QA | Execution | Web Testing
Jump to navigation
Jump to search
How do we want to list this? By project or type of goal?
Goals:
- Overview of the tools and how we'd done testing
- Shared goal of unit test w/WebDev -- new-function testing
- Split up who's going to test what (coordination)
- Target a small area vs. a number of testcases across the board
- BFTs for AMO, SUMO, SFx
- Smoketests for AMO, SUMO, SFx
- Metrics collection for the major projects
- FFT - linked to in the test-coverage spreadsheet
- Step 1
- Planning on coverage (survey of the areas)
- Step 2
- Create for a certain # of those areas, per project
- Step 1
- Basic backend testing - SQL queries -- automated Selenium
- Maybe better left as an individual goal?
- Create a document outlining guidelines for acceptance of new projects
- Evangelize the document
- For new/rushed projects, send out status updates to the team of open/closed bugs, etc.
Selenium presentations: 3 sessions
- General overview / lightning round (10 minutes per project)
- Selenium in PHP
- Selenium in the IDE