Identity/Test Automation Crew
From MozillaWiki
< Identity
Overview
This crew has been deactivated. There's still work to do, but no core dev is primarily focused on it.
Interested in getting involved? Have a look at the bugs and code, and the final status update for context, and get to hacking :-)
We're using the wd node library to write Selenium tests in JS.
- Weekly test automation triage: 9:30am PST in 6a68's Vidyo
- Meeting notes: 11/13
- internal folks welcome
- external folks, ping dev-identity if interested in joining & we'll add you to the meeting (Vidyo is internal-only, sadly, so we'll switch to something else)
- Bugs filed against the browserid repo on github with the crew:test-automation label.
- Code lives inside the browserid repo, under the automation-tests directory.
- Previous status updates on the dev-identity mailing list: 10/10, 11/1, 11/7, final update 12/21.
- Other sources of procedural info:
- We used the test-automation-spec etherpad as a planning tool in the past.
- More on selenium:
- see the README under the automation-tests directory
- slides from work week intro to selenium, including why we moved from python (used by other Mozilla services) to node.js
