QA/Execution/Web Testing/mcomtests: Difference between revisions
< QA | Execution | Web Testing
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
===Mozilla.com Automated Test Tracking=== | ===Mozilla.com Automated Test Tracking=== | ||
*[http://github.com/retornam/mcom-tests Repository] | *[http://github.com/retornam/mcom-tests Repository] | ||
* This needs to be in Hudson, ASAP, to augment/replace the current failing tests | |||
*Tests | *Tests | ||
**Redirect tests , these should cover the redirects in [http://svn.mozilla.org/projects/mozilla.com/tags/production/.htaccess htaccess] | **Redirect tests , these should cover the redirects in [http://svn.mozilla.org/projects/mozilla.com/tags/production/.htaccess htaccess] | ||
Revision as of 21:15, 1 February 2011
Mozilla.com Automated Test Tracking
- Repository
- This needs to be in Hudson, ASAP, to augment/replace the current failing tests
- Tests
- Redirect tests , these should cover the redirects in htaccess
- Video page tests
- Newsletter page tests
- Download button tests
- Note that we don't have to test the mirror links themselves, just that http://www.mozilla.com/products/download.html?product=firefox-3.6.13&os=win&lang=en-US (e.g.) returns a 200 OK, and redirects the page to http://www.mozilla.com/en-US/products/download.html?product=firefox-3.6.13&os=win&lang=en-US, and, if possible, puts up the mirror link (can we test that some event is fired off?)
- This would be done using PyQuery and urllib (this is needed to switch user agents and verify that the correct button and message appears on each download page)
- Mobile page tests
- Auto-detection of device?
- Auto-redirect
- Customization page tests
- Features page tests
- Homepage tests