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

/css/ - CSS Masters

Advanced styling, animations & modern CSS techniques
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1786784711325.jpg (92.97 KB, 1024x1024, img_1786784673536_g4tde65x.jpg)ImgOps Exif Google Yandex

63344 No.2025

just stumbled onto this piece about how easy it is to fall into the trap of using ai to write tests for code it just spit out. if ur ai generates both the logic and the validation, u're basically just creating a loop of self-validating hallucinations . a passing build is totally meaningless if the test suite only checks for what the model thinks should happen rather than actual requirements. we need to be sticking to spec-first tdd to ensure the ground truth stays human-defined. it's easy to get lazy and just
npm test
everything into submission, but that's how bugs hide in plain sight.
>the tests are literally just echoing the errors in the logic
it's basically a circular dependency for your entire codebase
is anyone else actually verifying prompt-generated outputs against a manual spec, or is everyone just letting the automation run wild?

full read: https://dev.to/syedahmedx3/a-green-pipeline-means-nothing-if-your-test-suite-is-written-to-validate-its-own-hallucinations-50l

63344 No.2026

File: 1786786289313.jpg (299.06 KB, 1024x1024, img_1786786248254_j8cpa549.jpg)ImgOps Exif Google Yandex

>>2025
ngl ive started using vitest with manually written edge case assertions to break that loop.



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