Test Your Code Changes
Test your code changes for an endpoint with existing tests
Kerno runs your updated code, compares the results with the baseline, and shows you any behaviour differences that appear. This flow is designed to give you fast feedback, a reliable safety net, and a clear understanding of how each change affects your system. Your tests remain useful without extra maintenance work since Kerno handles the analysis and updates for you.
Run Tests After a Change
Once an endpoint has a baseline, every test run follows a clear flow:
Kerno executes all existing scenarios for the endpoint.
Kerno compares the new behaviour with the saved baseline.
Kerno highlights any behaviour that no longer matches what was recorded.
If everything matches, the run completes with no actions needed.
Review the Diff
If the behaviour changes in any way, Kerno shows you a diff view. This can include changes in responses, status codes, sequence steps, or any other observable behaviour.
You can review the differences directly in your IDE and decide how to move forward:
Accept the change if the new behaviour is correct.
Update your code if the change is unintended.
Kerno never forces a decision. It shows the differences and waits for your choice.
Accept the Diff
When you accept a change, Kerno updates the scenario to match the new behaviour. It then analyzes your code again to check if new scenarios should be added or if any old ones no longer apply.
This keeps your testing aligned with the current behaviour of your system.
Fix your Code
If you decide the change is incorrect:
Update the code.
Run the tests again.
Kerno checks once more against the baseline.
Last updated