12 things need you, first: Say go on the Client D outline: 60 E2E tests. 9 features running.
Away ModeShip
Off
VoiceOnClaude speaks its lines
MAIN swapOffOn your word or the button
UsageThis session 71% used, resets 3:25 PM · this week 63% used, resets Sun 1:00 PM
Every repo is clean and pushed
mission-control: clean. Claude ships this one. Last shipped today 1:08 PM (“Runs view grouped by client”).
client-a-tests: clean. Claude ships this one. Last shipped today 1:42 PM (“Pay button now inside the payment dialog”).
client-b-tests: clean. Claude ships this one. Last shipped today 1:26 PM (“Menu opens by its button”).
client-c-tests: clean. Claude ships this one. Last shipped today 1:19 PM (“Card entry inside its hosted frame”).
client-d-tests: clean. Claude ships this one. Last shipped today 12:55 PM (“Wait for the seat map”).
client-e-tests: clean. Claude ships this one. Last shipped today 1:32 PM (“Show the video controls first”).
client-f-tests: clean. Claude ships this one. Last shipped today 1:13 PM (“Cart drawer settles before reading”).
Overview
11 features openIn order: the vital signs, what needs you, the test runs going now, what is running, what moves on its own, not started, paused on purpose, finished
Needs you 12 each row names its action
Say go on the Client D outline: 60 E2E testsplain: say go and the 60 E2E tests are built in 4 batches, trips first | why you: a plan…Decidea9121open 14 minutes
Census button name: pick Group by cause (my pick) or Sort failuresplain: say Group by cause or Sort failures; my pick is Group by cause, because it says…Decidea9123open 50 minutes
Overnight stop line: set the weekly usage that ends tonight's runs (my pick 85%)plain: say a number; my pick is 85%, which leaves a day's room | why you: the overnight…Decidea9124open 2 hours
Client E smoke time: move it from 6 AM to 7 AM (my pick)plain: say 7 AM or keep 6 AM; at 6 AM it overlaps Client F's nightly run on the same pods…Decidea9125open 1 hour
Weekly retro: say go on its 4 rule changesplain: say go and the 4 changes apply, each one undoable | why you: rule changes wait on…Decidea9126open 3 hours
Runner pods: allow 16 at once on busy mornings (my pick yes)plain: say yes and the cap goes from 12 to 16 under the same billing guard | why you: it…Decidea9127open 4 hours
Client C release run: send the 2 product-change questions to the client (my pick yes)plain: say send and the two questions go to Client C's team as written | why you: it…Decidea9128open 35 minutes
Sign in to the bug tracker again: your sign-in ends at 6 PMplain: sign in once on the tracker's page | why you: your sign-in | no page: the…Decidea9129open 2 hours
Teammate review note: send it as written (my pick yes)plain: say send and the note on 4 E2E tests goes to your teammate; 3 pass, 1 misses its…Decidea9132open 1 hour
Old run traces: clear 14 GB from last month (my pick yes)plain: say clear and last month's traces go; this month's stay | why you: it deletes data…Decidea9133open 2 hours
Look at Two platform passes for created E2E tests (GATE2) and approve itbuilt, waiting on your lookApprove9e15
Look at Runs view grouped by client (RUNSVIEW) and approve itbuilt, waiting on your lookApprove9e16
Running 9 soonest done first
Group failures by their last trace frameW8Your pickBuild · stage 2 of 3CENSUSrunning 1 hourdone by about 2:13 PM
New E2E tests for Client B's team calendar: 12 casesW7Build · stage 1 of 2CREATEBrunning 2 hoursdone by about 3:19 PM
Client D outline: 60 E2E testsMAINYour pickOutline · stage 1 of 2OUTLINEDrunning 12 minutesdone by about 4:44 PM
Client D nightly run: 64 failing E2E testsW4InvestigationLEADDrunning 3 hourspast its usual 43m
Client E smoke run: 56 failing E2E testsW5InvestigationLEADErunning 2 hourspast its usual 43m
Client F nightly run: 50 failing E2E testsW6InvestigationLEADFrunning 2 hourspast its usual 43m
Client A nightly run: 107 failing E2E testsW1InvestigationLEADArunning 4 hourslonger than usual
Client B nightly run: 80 failing E2E testsW2InvestigationLEADBrunning 4 hourslonger than usual
Client C release run: 71 failing E2E testsW3InvestigationLEADCrunning 3 hourslonger than usual
Waiting for 2 newest first; waits on a run, a worker or a gate, not on you; each moves to Running or Needs you on its own
Raise the runner pod cap to 16MAINa free slotWaits for: a free worker slotExpected: starts when a worker slot frees; none is freeBuild · stage 2 of 2PODCAPwaiting 56 minutesdone by about 2:56 PM
Nightly suite calendar on InvestigationsMAINa shipWaits for: the ship line: two changes aheadExpected: waits on a ship; the ship queue is empty nowShip · stage 2 of 2NIGHTCALwaiting 1 hourNOT MEASURED
Queued 3 in your order of work, then rows you said to start now
Runner swarm at 16 wideExpected: next in line; starts when a worker slot frees; none is freeStarts next9e12queued 1 hourNOT MEASURED
Client E bug recheckExpected: next in line; starts when a worker slot frees; none is freeStarts next9e13queued 1 hourNOT MEASURED
Weekly look at E2E test run times across six clients, queued by you 1:20 PM 10-29Expected: next in line; starts when a worker slot frees; none is freeStarts next9e14queued 40 minutesNOT MEASURED
Done today 7 7 features, 29 parts
Runs view grouped by clientMAINProof · stage 2 of 2RUNSVIEW1:08 PM
Two platform passes for created E2E testsMAINProof · stage 2 of 2GATE212:38 PM
Morning census of six suitesMAINCensusMORNING11:53 AM
8 new E2E tests for Client A's gift cardsMAINProof · stage 2 of 2GIFTA9:05 AM
Bug lists synced for six clientsMAINSyncBUGSYNC8:48 AM
Weekly report of flaky E2E testsMAINWriteFLAKES8:22 AM
Review of a teammate's 4 E2E testsMAINReviewREVIEWT7:35 AM
Running
9 featuresRunning 9 soonest done first
Group failures by their last trace frameW8Your pickBuild · stage 2 of 3CENSUSrunning 1 hourdone by about 2:13 PM
New E2E tests for Client B's team calendar: 12 casesW7Build · stage 1 of 2CREATEBrunning 2 hoursdone by about 3:19 PM
Client D outline: 60 E2E testsMAINYour pickOutline · stage 1 of 2OUTLINEDrunning 12 minutesdone by about 4:44 PM
Client D nightly run: 64 failing E2E testsW4InvestigationLEADDrunning 3 hourspast its usual 43m
Client E smoke run: 56 failing E2E testsW5InvestigationLEADErunning 2 hourspast its usual 43m
Client F nightly run: 50 failing E2E testsW6InvestigationLEADFrunning 2 hourspast its usual 43m
Client A nightly run: 107 failing E2E testsW1InvestigationLEADArunning 4 hourslonger than usual
Client B nightly run: 80 failing E2E testsW2InvestigationLEADBrunning 4 hourslonger than usual
Client C release run: 71 failing E2E testsW3InvestigationLEADCrunning 3 hourslonger than usual
Waiting for 2 newest first; waits on a run, a worker or a gate, not on you; each moves to Running or Needs you on its own
Raise the runner pod cap to 16MAINa free slotWaits for: a free worker slotExpected: starts when a worker slot frees; none is freeBuild · stage 2 of 2PODCAPwaiting 56 minutesdone by about 2:56 PM
Nightly suite calendar on InvestigationsMAINa shipWaits for: the ship line: two changes aheadExpected: waits on a ship; the ship queue is empty nowShip · stage 2 of 2NIGHTCALwaiting 1 hourNOT MEASURED
Queued
3 itemsQueued 3 in your order of work, then rows you said to start now; a line holding several items opens into them
Runner swarm at 16 wideExpected: next in line; starts when a worker slot frees; none is freeStarts next9e12queued 1 hourNOT MEASURED
Client E bug recheckExpected: next in line; starts when a worker slot frees; none is freeStarts next9e13queued 1 hourNOT MEASURED
Weekly look at E2E test run times across six clients, queued by you 1:20 PM 10-29Expected: next in line; starts when a worker slot frees; none is freeStarts next9e14queued 40 minutesNOT MEASURED
Done today
7 features · 29 partsDone today 7 newest first; a row opens into its parts
Runs view grouped by clientMAINProof · stage 2 of 2RUNSVIEW1:08 PM
Two platform passes for created E2E testsMAINProof · stage 2 of 2GATE212:38 PM
Morning census of six suitesMAINCensusMORNING11:53 AM
8 new E2E tests for Client A's gift cardsMAINProof · stage 2 of 2GIFTA9:05 AM
Bug lists synced for six clientsMAINSyncBUGSYNC8:48 AM
Weekly report of flaky E2E testsMAINWriteFLAKES8:22 AM
Review of a teammate's 4 E2E testsMAINReviewREVIEWT7:35 AM
Decided for you today
0 decisionsNothing decided for you today.
To review
2 items built, waiting on your lookTo review 2 approve: open the item, then press Approve
Look at Two platform passes for created E2E tests (GATE2) and approve itbuilt, waiting on your look9e15
Look at Runs view grouped by client (RUNSVIEW) and approve itbuilt, waiting on your look9e16
Sessions
9 open sessionsMAIN 8.12amMAIN0de1b00bworking
Nightly suite calendar on InvestigationsMAINa shipWaits for: the ship line: two changes aheadShip · stage 2 of 2NIGHTCAL
Client D outline: 60 E2E testsMAINYour pickOutline · stage 1 of 2OUTLINEDdone by about 4:44 PM
Raise the runner pod cap to 16MAINa free slotWaits for: a free worker slotBuild · stage 2 of 2PODCAP
W1 LEADA Client A nightly run: 107 failing E2E tests0de1b0a1working
Client A nightly run: 107 failing E2E testsW1InvestigationLEADAlonger than usual
W2 LEADB Client B nightly run: 80 failing E2E tests0de1b0b2working
Client B nightly run: 80 failing E2E testsW2InvestigationLEADBlonger than usual
W3 LEADC Client C release run: 71 failing E2E tests0de1b0c3working
Client C release run: 71 failing E2E testsW3InvestigationLEADClonger than usual
W4 LEADD Client D nightly run: 64 failing E2E tests0de1b0d4idle
Client D nightly run: 64 failing E2E testsW4InvestigationLEADDpast its usual 43m
W5 LEADE Client E smoke run: 56 failing E2E tests0de1b0e5working
Client E smoke run: 56 failing E2E testsW5InvestigationLEADEpast its usual 43m
W6 LEADF Client F nightly run: 50 failing E2E tests0de1b0f6working
Client F nightly run: 50 failing E2E testsW6InvestigationLEADFpast its usual 43m
W7 CREATEB New E2E tests for Client B's team calendar: 12 cases0de1b0a7working
New E2E tests for Client B's team calendar: 12 casesW7Build · stage 1 of 2CREATEBdone by about 3:19 PM
W8 CENSUS Group failures by their last trace frame0de1b0a8working
Group failures by their last trace frameW8Your pickBuild · stage 2 of 3CENSUSdone by about 2:13 PM
Planned
0 plans written for you · none waits on youNo plan docs yet.
Plan docs, newest first.
Systems
all fineNo system checks found.
Order of work
16 itemsOrder of work 16 your whole list in its own order: in progress, built and waiting on your look, next, done today
Client A nightly run: 107 failing E2E tests (LEADA, W1)9e1in progress
Client B nightly run: 80 failing E2E tests (LEADB, W2)9e2in progress
Client C release run: 71 failing E2E tests (LEADC, W3)9e3in progress
Client D nightly run: 64 failing E2E tests (LEADD, W4)9e4in progress
Client E smoke run: 56 failing E2E tests (LEADE, W5)9e5in progress
Client F nightly run: 50 failing E2E tests (LEADF, W6)9e6in progress
New E2E tests for Client B's team calendar: 12 cases (CREATEB, W7)9e7in progress
Group failures by their last trace frame (CENSUS, W8)9e8in progress
Client D outline: 60 E2E tests, then your go (OUTLINED)9e9in progress
Nightly suite calendar on Investigations (NIGHTCAL)9e10in progress
Raise the runner pod cap to 16 (PODCAP)9e11in progress
Runner swarm at 16 wide: Client A's last 20 E2E tests proven at once on the runner, queued by you 12:30 PM 10-299e12next
Client E bug recheck: the 2 bug-blocked E2E tests re-run on the runner, queued by you 12:55 PM 10-299e13next
Weekly look at E2E test run times across six clients, queued by you 1:20 PM 10-299e14next
Two platform passes for created E2E tests (GATE2)9e15built, waits on your look
Runs view grouped by client (RUNSVIEW)9e16built, waits on your look
MAIN 8.12am
0de1b00b · MAINMAIN 8.12amMAIN0de1b00bworking
Bug lists synced for six clientsMAINSyncBUGSYNC8:48 AM
Weekly report of flaky E2E testsMAINWriteFLAKES8:22 AM
Two platform passes for created E2E testsMAINProof · stage 2 of 2GATE212:38 PM
8 new E2E tests for Client A's gift cardsMAINProof · stage 2 of 2GIFTA9:05 AM
Morning census of six suitesMAINCensusMORNING11:53 AM
Nightly suite calendar on InvestigationsMAINa shipWaits for: the ship line: two changes aheadShip · stage 2 of 2NIGHTCAL
Client D outline: 60 E2E testsMAINYour pickOutline · stage 1 of 2OUTLINEDdone by about 4:44 PM
Raise the runner pod cap to 16MAINa free slotWaits for: a free worker slotBuild · stage 2 of 2PODCAP
Review of a teammate's 4 E2E testsMAINReviewREVIEWT7:35 AM
Runs view grouped by clientMAINProof · stage 2 of 2RUNSVIEW1:08 PM
Parts done today 20
W1 LEADA Client A nightly run: 107 failing E2E tests
0de1b0a1W1 LEADA Client A nightly run: 107 failing E2E tests0de1b0a1working
Client A nightly run: 107 failing E2E testsW1InvestigationLEADAlonger than usual
Parts done today 1
W2 LEADB Client B nightly run: 80 failing E2E tests
0de1b0b2W2 LEADB Client B nightly run: 80 failing E2E tests0de1b0b2working
Client B nightly run: 80 failing E2E testsW2InvestigationLEADBlonger than usual
Parts done today 1
W3 LEADC Client C release run: 71 failing E2E tests
0de1b0c3W3 LEADC Client C release run: 71 failing E2E tests0de1b0c3working
Client C release run: 71 failing E2E testsW3InvestigationLEADClonger than usual
Parts done today 1
W4 LEADD Client D nightly run: 64 failing E2E tests
0de1b0d4W4 LEADD Client D nightly run: 64 failing E2E tests0de1b0d4idle
Client D nightly run: 64 failing E2E testsW4InvestigationLEADDpast its usual 43m
Parts done today 2
W5 LEADE Client E smoke run: 56 failing E2E tests
0de1b0e5W5 LEADE Client E smoke run: 56 failing E2E tests0de1b0e5working
Client E smoke run: 56 failing E2E testsW5InvestigationLEADEpast its usual 43m
Parts done today 1
W6 LEADF Client F nightly run: 50 failing E2E tests
0de1b0f6W6 LEADF Client F nightly run: 50 failing E2E tests0de1b0f6working
Client F nightly run: 50 failing E2E testsW6InvestigationLEADFpast its usual 43m
Parts done today 1
W7 CREATEB New E2E tests for Client B's team calendar: 12 cases
0de1b0a7W7 CREATEB New E2E tests for Client B's team calendar: 12 cases0de1b0a7working
New E2E tests for Client B's team calendar: 12 casesW7Build · stage 1 of 2CREATEBdone by about 3:19 PM
Parts done today 1
W8 CENSUS Group failures by their last trace frame
0de1b0a8W8 CENSUS Group failures by their last trace frame0de1b0a8working
Group failures by their last trace frameW8Your pickBuild · stage 2 of 3CENSUSdone by about 2:13 PM
Parts done today 1
Bug lists synced for six clients
BUGSYNCDoneSync2 of 2 parts · took 18m · finished 8:48 AMMAIN 8.12am
In short
Every client's open bugs read again, each bug-blocked E2E test checked against them
Stages 1 estimate against the time taken
Sync2 of 2 · estimate about 15 minutes · took 18m · done
Every part, in order 2 click one for what it produced
Read each client's open bugsdone1finished 8:39 AM · took 9m
Check each bug-blocked E2E test against its bugdone2finished 8:48 AM · took 8m
record: progress/BUGSYNC.tsv
Weekly report of flaky E2E tests
FLAKESDoneWrite2 of 2 parts · took 42m · finished 8:22 AMMAIN 8.12am
In short
The week's flaky E2E tests, one line each with its cause, ready to send
Stages 1 estimate against the time taken
Write2 of 2 · estimate about 30 minutes · took 42m · done
Every part, in order 2 click one for what it produced
Collect the week's flaky E2E testsdone1finished 7:58 AM · took 18m
Write one line each with its causedone2finished 8:22 AM · took 22m
record: progress/FLAKES.tsv
Two platform passes for created E2E tests
GATE2DoneProof · stage 2 of 22 of 2 parts · took 1h 28m · finished 12:38 PMMAIN 8.12am
In short
A created E2E test is handed over only after two platform passes on the same code, not one
- Built
- The hand-over check that wants two platform passes for a created E2E test
- Where to see it
- the proof run's report
Stages 2 estimate against the time taken
Build1 of 1 · estimate about an hour · took 45m · done
Proof1 of 1 · estimate about 20 minutes · took 40m · done
starts on its own when the stage before it is done
Every part, in order 2 click one for what it produced
Count platform passes per created E2E testdone1finished 11:55 AM · took 45m
A single pass is refused, two passdone2finished 12:38 PM · took 40m
record: progress/GATE2.tsv
8 new E2E tests for Client A's gift cards
GIFTADoneProof · stage 2 of 23 of 3 parts · took 2h 45m · finished 9:05 AMMAIN 8.12am
In short
8 E2E tests created from Client A's gift card cases, each written step proven
Stages 2 estimate against the time taken
Build1 of 1 · estimate about 3 hours · took 1h 50m · done
Proof2 of 2 · estimate about an hour · took 53m · done
starts on its own when the stage before it is done
Every part, in order 3 click one for what it produced
Build the 8 E2E testsdone1finished 8:10 AM · took 1h 50m
Prove each one twice on the runnerdone2finished 8:55 AM · took 43m
A second agent reviews all 8 against their casesdone3finished 9:05 AM · took 8m
record: progress/GIFTA.tsv
Morning census of six suites
MORNINGDoneCensus3 of 3 parts · took 2h 58m · finished 11:53 AMMAIN 8.12am
In short
Six overnight suites read at once: each failure grouped, each client handed to its own lead
Stages 1 estimate against the time taken
Census3 of 3 · estimate about 40 minutes · took 2h 58m · done
Every part, in order 3 click one for what it produced
Read the six suites' failuresdone1finished 9:08 AM · took 13m
Group each suite's failures by causedone2finished 9:20 AM · took 12m
Open a lead for each clientdone3finished 11:53 AM · took 2h 43m
record: progress/MORNING.tsv
Nightly suite calendar on Investigations
NIGHTCALWaitingShip · stage 2 of 21 of 2 parts · 2h 20m so farMAIN 8.12am
In short
A calendar strip of each client's nightly suite, so a late suite shows before its failures do
Stages 2 estimate against the time taken
Build1 of 1 · estimate about an hour · took 45m · done
Ship0 of 1 · estimate about 10 minutes · running 1h 33m · waiting
starts on its own when the stage before it is done
paused: Ship the calendar strip: waits for the ship line: two changes ahead
Every part, in order 2 click one for what it produced
Draw each client's nightly suite on a stripdone1finished 12:25 PM · took 45m
Ship the calendar stripwaiting2started 12:27 PM ·
record: progress/NIGHTCAL.tsv
Client D outline: 60 E2E tests
OUTLINEDRunningOutline · stage 1 of 22 of 4 parts · 3h 20m so farMAIN 8.12am
In short
Client D's new loyalty pages outlined into 60 named test cases, built once Kevin says go
Right now: Split the build into batches of 15
Stages 2 estimate against the time taken
Outline2 of 3 · estimate about 2 hours · running 3h 20m · in progress
Build0 of 1 · estimate about two days · not started · not started
starts on its own when the stage before it is done
Every part, in order 4 click one for what it produced
Read the loyalty, trips and account pagesdone1finished 11:25 AM · took 45m
Write 60 test cases with steps and expected resultsdone2finished 12:55 PM · took 1h 28m
Split the build into batches of 15doing3started 1:48 PM · running 12m
Build the 60 E2E testsnext4
record: progress/OUTLINED.tsv
Raise the runner pod cap to 16
PODCAPWaitingBuild · stage 2 of 21 of 2 parts · 1h 10m so farMAIN 8.12am
In short
Sixteen runner pods at once for the busy mornings, under the same billing guard
Stages 2 estimate against the time taken
Plan1 of 1 · estimate about 15 minutes · took 12m · done
Build0 of 1 · estimate about 30 minutes · running 56m · waiting
starts on its own when the stage before it is done
paused: Raise the cap and prove the guard: waits for a free worker slot
Every part, in order 2 click one for what it produced
Plan the higher cap with its guarddone1finished 1:02 PM · took 12m
Raise the cap and prove the guardwaiting2started 1:04 PM ·
record: progress/PODCAP.tsv
Review of a teammate's 4 E2E tests
REVIEWTDoneReview2 of 2 parts · took 40m · finished 7:35 AMMAIN 8.12am
In short
Four of a teammate's E2E tests checked against their written steps, with a note for the teammate
Stages 1 estimate against the time taken
Review2 of 2 · estimate about 45 minutes · took 40m · done
Every part, in order 2 click one for what it produced
Read each test's code, trace and videodone1finished 7:25 AM · took 30m
Write the summary and the note for the teammatedone2finished 7:35 AM · took 8m
record: progress/REVIEWT.tsv
Runs view grouped by client
RUNSVIEWDoneProof · stage 2 of 22 of 2 parts · took 48m · finished 1:08 PMMAIN 8.12am
In short
The Runs view groups the runs in flight by client, so six investigations at once stay readable
- Built
- Runs view grouped by client, each group with its own count
- Where to see it
- the proof run's report
Stages 2 estimate against the time taken
Build1 of 1 · estimate about 40 minutes · took 32m · done
Proof1 of 1 · estimate about 15 minutes · took 14m · done
starts on its own when the stage before it is done
Every part, in order 2 click one for what it produced
Group the runs in flight by clientdone1finished 12:52 PM · took 32m
Six planted clients, each count rightdone2finished 1:08 PM · took 14m
record: progress/RUNSVIEW.tsv
Client A nightly run: 107 failing E2E tests
LEADARunningInvestigation1 of 3 parts · 4h 46m so farW1 LEADA Client A nightly run: 107 failing E2E tests
In short
The client lead for Client A: every failing E2E test re-run first, then only the ones that fail twice are diagnosed
Right now: Diagnose the ones that failed twice, Fix and prove each cause on the runner
Stages 1 estimate against the time taken
Investigation1 of 3 · estimate about 5 hours · running 4h 46m · in progress
Every part, in order 3 click one for what it produced
Re-run every failing E2E test on the runnerdone1finished 10:02 AM · took 48m
Diagnose the ones that failed twicedoing2started 10:05 AM · running 3h 55m
Fix and prove each cause on the runnerdoing3started 10:50 AM · running 3h 10m
record: progress/LEADA.tsv
Client B nightly run: 80 failing E2E tests
LEADBRunningInvestigation1 of 3 parts · 4h 16m so farW2 LEADB Client B nightly run: 80 failing E2E tests
In short
The client lead for Client B: every failing E2E test re-run first, then only the ones that fail twice are diagnosed
Right now: Diagnose the ones that failed twice, Fix and prove each cause on the runner
Stages 1 estimate against the time taken
Investigation1 of 3 · estimate about 5 hours · running 4h 16m · in progress
Every part, in order 3 click one for what it produced
Re-run every failing E2E test on the runnerdone1finished 10:20 AM · took 36m
Diagnose the ones that failed twicedoing2started 10:22 AM · running 3h 38m
Fix and prove each cause on the runnerdoing3started 11:10 AM · running 2h 50m
record: progress/LEADB.tsv
Client C release run: 71 failing E2E tests
LEADCRunningInvestigation1 of 3 parts · 3h 50m so farW3 LEADC Client C release run: 71 failing E2E tests
In short
The client lead for Client C: every failing E2E test re-run first, then only the ones that fail twice are diagnosed
Right now: Diagnose the ones that failed twice, Fix and prove each cause on the runner
Stages 1 estimate against the time taken
Investigation1 of 3 · estimate about 5 hours · running 3h 50m · in progress
Every part, in order 3 click one for what it produced
Re-run every failing E2E test on the runnerdone1finished 10:48 AM · took 38m
Diagnose the ones that failed twicedoing2started 10:50 AM · running 3h 10m
Fix and prove each cause on the runnerdoing3started 11:40 AM · running 2h 20m
record: progress/LEADC.tsv
Client D nightly run: 64 failing E2E tests
LEADDRunningInvestigation2 of 3 parts · 3h 35m so farW4 LEADD Client D nightly run: 64 failing E2E tests
In short
The client lead for Client D: every failing E2E test re-run first, then only the ones that fail twice are diagnosed
Right now: Fix and prove each cause on the runner
Stages 1 estimate against the time taken
Investigation2 of 3 · estimate about 5 hours · running 3h 35m · in progress
Every part, in order 3 click one for what it produced
Re-run every failing E2E test on the runnerdone1finished 11:02 AM · took 37m
Diagnose the ones that failed twicedone2finished 12:30 PM · took 1h 26m
Fix and prove each cause on the runnerdoing3started 12:32 PM · running 1h 28m
record: progress/LEADD.tsv
Client E smoke run: 56 failing E2E tests
LEADERunningInvestigation1 of 3 parts · 2h 30m so farW5 LEADE Client E smoke run: 56 failing E2E tests
In short
The client lead for Client E: every failing E2E test re-run first, then only the ones that fail twice are diagnosed
Right now: Diagnose the ones that failed twice, Fix and prove each cause on the runner
Stages 1 estimate against the time taken
Investigation1 of 3 · estimate about 5 hours · running 2h 30m · in progress
Every part, in order 3 click one for what it produced
Re-run every failing E2E test on the runnerdone1finished 11:58 AM · took 28m
Diagnose the ones that failed twicedoing2started 12:00 PM · running 2h 00m
Fix and prove each cause on the runnerdoing3started 12:38 PM · running 1h 22m
record: progress/LEADE.tsv
Client F nightly run: 50 failing E2E tests
LEADFRunningInvestigation1 of 3 parts · 2h 05m so farW6 LEADF Client F nightly run: 50 failing E2E tests
In short
The client lead for Client F: every failing E2E test re-run first, then only the ones that fail twice are diagnosed
Right now: Diagnose the ones that failed twice, Fix and prove each cause on the runner
Stages 1 estimate against the time taken
Investigation1 of 3 · estimate about 5 hours · running 2h 05m · in progress
Every part, in order 3 click one for what it produced
Re-run every failing E2E test on the runnerdone1finished 12:19 PM · took 24m
Diagnose the ones that failed twicedoing2started 12:20 PM · running 1h 40m
Fix and prove each cause on the runnerdoing3started 1:02 PM · running 58m
record: progress/LEADF.tsv
New E2E tests for Client B's team calendar: 12 cases
CREATEBRunningBuild · stage 1 of 21 of 4 parts · 2h 38m so farW7 CREATEB New E2E tests for Client B's team calendar: 12 cases
In short
12 new E2E tests from Client B's written cases, each step mapped to an assertion seen passing
Right now: Build the 12 E2E tests
Stages 2 estimate against the time taken
Build1 of 2 · estimate about 4 hours · running 2h 38m · in progress
Proof0 of 2 · estimate about an hour · not started · not started
starts on its own when the stage before it is done
Every part, in order 4 click one for what it produced
Read the team calendar pages as each roledone1finished 11:55 AM · took 33m
Build the 12 E2E testsdoing2started 11:57 AM · running 2h 03m
Prove each one twice on the runnernext3
A second agent reviews all 12 against their casesnext4
record: progress/CREATEB.tsv
Group failures by their last trace frame
CENSUSRunningBuild · stage 2 of 31 of 3 parts · 1h 53m so farW8 CENSUS Group failures by their last trace frame
In short
The morning census groups a suite's failures by the screen they stopped on, so one fix is found once
Right now: Read each failure's last frame and group them
Stages 3 estimate against the time taken
Plan1 of 1 · estimate about 20 minutes · took 13m · done
Build0 of 1 · estimate about 2 hours · running 1h 38m · in progress
starts on its own when the stage before it is done
Proof0 of 1 · estimate about 40 minutes · not started · not started
starts on its own when the stage before it is done
Every part, in order 3 click one for what it produced
Plan the grouping from the briefdone1finished 12:20 PM · took 13m
Read each failure's last frame and group themdoing2started 12:22 PM · running 1h 38m
Planted suites group the way a person wouldnext3
record: progress/CENSUS.tsv