Page MenuHomePhabricator

Follow up workshop & brown bag ideas from Testing: Where does it hurt? (tracking)
Open, MediumPublic

Description

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

Event Timeline

ggellerman raised the priority of this task from to Needs Triage.
ggellerman updated the task description. (Show Details)
ggellerman added subscribers: Aklapper, dduvall, ggellerman.
dduvall updated the task description. (Show Details)Aug 5 2015, 10:19 PM
dduvall set Security to None.
Awjrichards triaged this task as Medium priority.Aug 12 2015, 7:39 PM
Awjrichards moved this task from To Triage to General backlog on the Team-Practices board.
hashar renamed this task from Follow up workshop & brown bag ideas from Testing: Where does it hurt? to [tracking] Follow up workshop & brown bag ideas from Testing: Where does it hurt? .Aug 25 2015, 9:26 AM
greg moved this task from INBOX to Backlog on the Release-Engineering-Team board.Sep 24 2015, 1:33 AM
Danny_B renamed this task from [tracking] Follow up workshop & brown bag ideas from Testing: Where does it hurt? to Follow up workshop & brown bag ideas from Testing: Where does it hurt? (tracking).May 27 2016, 5:57 PM

@ggellerman @dduvall is this stuff still moving forward at all? If not, perhaps these tickets can be closed given their age and inactivity.

ggellerman added a comment.EditedJun 29 2016, 5:25 PM

@Awjrichards

We decided that the project could end. We had a retro, RelEng got something out of the effort, and I have renamed the Phab project from Testing-Initiative-2015 to Testing-Initiative.

I have removed Team-Practices project from here.

Aklapper edited projects, added Epic; removed Tracking-Neverending.Apr 7 2019, 7:42 PM
hashar removed a subscriber: hashar.Apr 8 2019, 8:58 AM
greg moved this task from Backlog to INBOX on the Release-Engineering-Team board.Oct 17 2019, 5:24 PM