Web Testing/Automation/automation-19-08-2011: Difference between revisions
Jump to navigation
Jump to search
| Line 3: | Line 3: | ||
* Have a meeting with everyone including Waverly to discuss the notes from Romania visit. | * Have a meeting with everyone including Waverly to discuss the notes from Romania visit. | ||
* Get an update from David regarding py.test decorators | * Get an update from David regarding py.test decorators | ||
** (DB) Due to other tasks this has taken a hit. Sorry this has taken a back burner but Automation Services items have come up. This is in the [https://www.pivotaltracker.com/projects/323503 Automation Services Pivotal Tracker] | |||
* Meeting owners should send out the an email 24-hours prior to the meeting with an url to the wiki to give people time to insert updates and discussion items. | * Meeting owners should send out the an email 24-hours prior to the meeting with an url to the wiki to give people time to insert updates and discussion items. | ||
* Investigate locking down workspaces / yaml | * Investigate locking down workspaces / yaml | ||
Revision as of 22:28, 18 August 2011
<< Last meeting | WebQA Automation | Next meeting >>
Action Items from last meeting
- Have a meeting with everyone including Waverly to discuss the notes from Romania visit.
- Get an update from David regarding py.test decorators
- (DB) Due to other tasks this has taken a hit. Sorry this has taken a back burner but Automation Services items have come up. This is in the Automation Services Pivotal Tracker
- Meeting owners should send out the an email 24-hours prior to the meeting with an url to the wiki to give people time to insert updates and discussion items.
- Investigate locking down workspaces / yaml
- Use bugtype for broken tests and chores for refactoring tests.
- Moving more tests from zamboni to impala
Discussion topics / General Updates
- Removing amo/addons from variable names and test names in the amo tests. Is this something we want to do?
- webapps - There is now a weekly meeting for this. Double check of who should be involved with webapps, where we are, etc.