**Goal**
To get a baseline of user satisfaction in our browser-testing infrastructure/tooling.
**Target audience**
- [[ https://lists.wikimedia.org/mailman/listinfo/wikitech-l | wikitech-l ]]
- [[ https://lists.wikimedia.org/mailman/listinfo/engineering | engineering ]]
- [[ https://lists.wikimedia.org/mailman/listinfo/qa | qa ]]
**Notes**
[[ https://www.youtube.com/watch?v=R2hdLfPFcQk | Testing: Where does it hurt? ]] video might be good inspiration for questions.
**Scale**
Three level scale might be enough for our purpose:
- :)
- :|
- :(
**Jenkins**
- Gerrit triggered Selenium+Jenkins jobs (after patch set submission)
- are stable enough
- are fast enough
- Time triggered Selenium+Jenkins jobs (daily)
- are stable enough
- are fast enough
- CI entry points make sense to me
- Rake
- Grunt
**Ruby**
- I like current Selenium+Ruby framework
- I like writing Ruby
- I like Cucumber testing library
- I would prefer to write tests in RSpec
- Fixing failed tests is easy
**Selenium**
- I like writing Selenium tests
**JavaScript**
- I would prefer to write Selenium tests in JavaScript
- I like Mocha testing library
- I would prefer to write tests in QUnit
**Getting help**
- I know how to get help (Mediawiki.org, IRC, Phabricator, QA mailing list...)
- There is sufficient documentation on how to do testing
- Getting started documentation is good enough
- I need help with getting started with testing
- I would like to pair with somebody
- I would like to attend on-line workshop
- I would like to attend in person workshop (hackathon, conference)
- I need help with fixing failed tests
- I would like to pair with somebody
- I would like to attend on-line workshop
- I would like to attend in person workshop (hackathon, conference)