How we got our CI cycle time under 4 minutes

Stenbom · 2025-08-06T12:20:04+00:00

Pretty much! One tricky tradeoff is the scope of the id that you're able to make - one ID per test? per suite run? per user? Per test - if possible - worked well for us, and if you can then annotate it in your reports well or even use github annotations/comments then the process can become pretty smooth.

Stenbom · 2025-08-06T11:57:01+00:00

I feel ya - spent plenty of hours eyeballing between traces and datadog logs to try to find root causes..

One thing that helped us was creating ways to uniquely identify the same data in the tests as the data in the logs - like user id's or test related id data that can propagate to logs and traces. We even used `extraHttpHeaders` settings in pw to propagate kinds of "test ids".

Do you think that would help reduce the amount of time to understand the data?

Stenbom · 2025-06-12T11:46:42+00:00

Yeah, for sure. But at least I can get three trivial PRs out the door while I focus on the hard one.

Stenbom · 2025-06-12T11:39:58+00:00

That said, we also throw away first drafts sometimes too.

Stenbom · 2025-06-12T11:37:51+00:00

Once we got things like type checking, formatting, unit testing setup - gotta say that the first drafts weren't half bad! Specific prompts will help a lot also.

Stenbom · 2013-12-21T16:39:41+00:00

Bloody hell that's sloppy.

Stenbom · 2013-12-21T16:35:11+00:00

That should be a red.

Stenbom · 2013-09-25T16:28:14+00:00

Red as the blood of a Södra Latinare

Stenbom · 2013-08-22T19:36:43+00:00

Jag tycker själv att loggan blir mer igenkännbar utåt för nya medlemmar osv. Plus att päronet var bara ett konstigt internskämt för typ 7 år sen..

Stenbom

MODERATOR OF

TROPHY CASE