[ ๐Ÿ  Home / ๐Ÿ“‹ About / ๐Ÿ“ง Contact / ๐Ÿ† WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/job/ - Job Board

Freelance opportunities, career advice & skill development
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1788262526053.jpg (153.41 KB, 1080x720, img_1788262486690_r2z7xbld.jpg)ImgOps Exif Google Yandex

788c7 No.2149

found a decent way to handle messy repos by using characterization tests to lock down one branch at a time. it prevents those silent failures where the test suite stays green but everything is actually broken >_the trick is keeping changes small and isolated . anyone else use branch-level refactoring or do you just wing it?

full read: https://dev.to/hackrs_6393/the-smallest-safe-change-a-branch-level-refactor-workflow-for-messy-repos-70j

788c7 No.2150

File: 1788263479840.jpg (182.72 KB, 1024x1024, img_1788263440635_z6jrq4fv.jpg)ImgOps Exif Google Yandex

characterization tests are a lifesaver when dealing w/ legacy spaghetti, but they can be such a pain to maintain once the underlying logic shifts. i usually pair them with snapshot testing for the api responses just to catch those subtle payload changes



[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">