Web Testing/Automation/automation-13-05-2011: Difference between revisions

Revision as of 16:27, 13 May 2011

Waverly working with WebQA now. Currently plowing through code reviews
Selenium Grid 2.0 progress
Renaming Selenium environments - proposal is here: https://github.com/davehunt/moz-grid-config/blob/new-environment-names/grid_configuration.yml
Py.Test doesn't give us a testrun duration in the results XML so we're missing out on some reporting. See http://qa-selenium.mv.mozilla.com:8080/job/input.stage/478/testReport/history/?
Conftest.py -- everyone know it?
Unless you have a specific need, we shouldn't be using Firefox4b;en-us;MacOSX6 in tests
- Related -- Raymond and I talked yesterday about auto-updating an Aurora build on Mac in our env.
  - wget the build, rm -rf the old build/dir, mv the new build to the Applications folder?
Would like dev/trunk, next/stage, prod test runs
Where are we with marking tests for specific environments, etc?
Wishlist from Stephen: BFT/smoketest-style suite for new Engagement projects
- Think: David's security suite (Garmr) + server status, basic tests, etc.
  - Really lightweight, but useful -- goal is to increase awareness of staging-server/project suck
    - I offer https://webifyme-dev.allizom.org/ as an example

Dave H. is currently fixing the broken build. Have brought in command-line stuff to simplify things.
- This impacts all open pull requests
- Removed vars.py completely - we should apply this to other test repos using conftest.py

@@ Line 13: / Line 13: @@
 * Where are we with marking tests for specific environments, etc?
 * Wishlist from Stephen: BFT/smoketest-style suite for new Engagement projects
-** Think: David's security suite + server status, basic tests, etc.
+** Think: [https://wiki.mozilla.org/WebAppSec/garmr David's security suite] (Garmr) + server status, basic tests, etc.
 *** Really lightweight, but useful -- goal is to increase awareness of staging-server/project suck
 **** I offer https://webifyme-dev.allizom.org/ as an example