jugglinmike

Got it--added that to the table

Thanks, @jscholes. That's in the table, now, too.

Yup!

Hey there @mcking65, I have returned! > Could you please add a link to the spec that @jugglinmike wrote. If I recall correctly, this mockup is not for the MVP...

@isaacdurazo I don't think we have any need for pausing (plus, I don't think the design can support it--it would need yet another state for collection jobs, e.g. "paused"). Regarding...

Thanks, @mcking65! When we designed this proposal internally, we tried to honor your vision of treating the automation system like a user. Much of my response below is geared toward...

Got it, @mcking65. Isaac and I reviewed your requests, and we'll have a new iteration ready for review soon. Regarding this detail from your original feedback: > Assign to should...

@mcking65 We've learned through the ongoing implementation work that the constraints of the job execution environment present significant hurdles to supporting a "retry" operation on a per-test basis. This, in...

> @jugglinmike wrote: > > > 4. The Test Admin notices that the response collector appears to have stalled > > 5. (CHANGE) The Test Admin makes the Test Plan...

@mcking65 It's been a long time since we attempted to describe the design holistically, so (after conferring with Isaac), I'm going to write a spec for for the automation UI...