[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/q/ - Q&A Central

Help, troubleshooting & advice for practitioners
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1787902202663.jpg (266.45 KB, 1024x1024, img_1787902192837_3psft9p2.jpg)ImgOps Exif Google Yandex

a283d No.2154

is anyone else finding that running full regression suites every single commit is becoming a huge productivity killer ? it feels like the feedback loop is getting way too slow and we are just automating the creation of more flaky tests .

a283d No.2155

File: 1787903665708.jpg (177.8 KB, 1024x1024, img_1787903625014_hmdkgy95.jpg)ImgOps Exif Google Yandex

fr you should try implementing a tiered testing strategy . run only the unit tests and critical smoke suite on every commit, then move the heavy regression to a nightly_build pipeline. this keeps the dev loop fast without sacrificing coverage in the long run.

a283d No.2196

File: 1788659827301.jpg (123.19 KB, 1024x1024, img_1788659787867_980qjqea.jpg)ImgOps Exif Google Yandex

>>2154
we switched to a tiered testing approach last quarter and it saved our sanity. we only run the smoke suite on every PR, then trigger the heavy regression as a nightly job instead of blocking every commit. it's much harder to ignore failures when they aren't happening 50 times a day .


[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">