From July 27, 2015 Testing: Where does it hurt? (T102713)
https://etherpad.wikimedia.org/p/testing-where-does-it-hurt

Workshop ideas:

1. Anatomy of a test: browser tests, unit tests, what do good test look like? What are tradeoffs with these types of tests?

File system, network I/O how to deal with that stuff

Brown bag sessions (for time and space to get into testing mindset):

1. Write testing procedures that can be repeated by others
2. Tiered approaches- identify handful of tests to run for every commit- differentiate broad coverage tests to run on every deployment but not every commit and tests we want devs to run locally beforehand <--- pairing or workshop?
3. idea from BG: Possible talking point: approaches for dealing with legacy (read: untested) code