HN Explorer

How to control unit tests in Agentic Pipelines

2 points by n4pw01f ↗ HN
Have some wins but many struggles here

When generating new features using agents, we must then update the unit tests

This is counter to the purpose of unit tests.

Allowing the system to update its unit tests is introducing risk and uncertainty, even with scoped PRs

Not allowing the system to update unit tests will negatively impact velocity…

How are folks in the field handling this? Have a real rube-Goldberg situation going on here

5 comments

[ 4.7 ms ] story [ 9.7 ms ] thread
tensward
I just don't let AI write any unit tests, only e2e tests, if you allow it to write unit test you end up with 5000 tests for each button, it's useless and takes a lot of resource.

AI now can do very accurate and trustworthy e2e tests, and this is how your end users will use the product anyway, but you can run a lot of scenarios in parallel and fix bugs faster than before, the approach of testing need to change imo