Identity/Test Automation Crew: Difference between revisions
< Identity
Jump to navigation
Jump to search
| Line 3: | Line 3: | ||
'''This crew has been deactivated.''' There's still work to do, but no core dev is primarily focused on it. | '''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 | Interested in getting involved? Have a look at the bugs and code, and the [https://groups.google.com/forum/#!topic/mozilla.dev.identity/Y2zvYaw1cdo final status update] for context, and get to hacking :-) | ||
We're using the wd node library to write Selenium tests in JS. | We're using the wd node library to write Selenium tests in JS. | ||
| Line 14: | Line 14: | ||
* Bugs filed against the [https://github.com/mozilla/browserid/issues?labels=crew%3Aautomated-tests&state=open browserid repo on github] with the crew:test-automation label. | * Bugs filed against the [https://github.com/mozilla/browserid/issues?labels=crew%3Aautomated-tests&state=open browserid repo on github] with the crew:test-automation label. | ||
* Code lives inside the [https://github.com/mozilla/browserid/tree/dev/automation-tests browserid repo], under the automation-tests directory. | * Code lives inside the [https://github.com/mozilla/browserid/tree/dev/automation-tests browserid repo], under the automation-tests directory. | ||
* Previous status updates on the dev-identity mailing list: [https://groups.google.com/d/topic/mozilla.dev.identity/bWfI_PrS3Wc/discussion 10/10], [https://groups.google.com/d/topic/mozilla.dev.identity/u-nmeS-2eoA/discussion 11/1], [https://groups.google.com/forum/#!topic/mozilla.dev.identity/yoXn4RPQHQY 11/7]. | * Previous status updates on the dev-identity mailing list: [https://groups.google.com/d/topic/mozilla.dev.identity/bWfI_PrS3Wc/discussion 10/10], [https://groups.google.com/d/topic/mozilla.dev.identity/u-nmeS-2eoA/discussion 11/1], [https://groups.google.com/forum/#!topic/mozilla.dev.identity/yoXn4RPQHQY 11/7], final update [https://groups.google.com/forum/#!topic/mozilla.dev.identity/Y2zvYaw1cdo 12/21]. | ||
* Other sources of procedural info: | * Other sources of procedural info: | ||
** We used the [https://id.etherpad.mozilla.org/test-automation-spec test-automation-spec] etherpad as a planning tool in the past. | ** We used the [https://id.etherpad.mozilla.org/test-automation-spec test-automation-spec] etherpad as a planning tool in the past. | ||
Latest revision as of 04:57, 22 December 2012
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