Open the context
Choose the project folder and name the files or behavior involved.
Workflows
Coding workflows · Test coverage gaps
03
A concrete starting point
Read a coverage report alongside the assertions. Find a branch that runs without checking its result, then add a test that would fail when the behavior is wrong.
Define the change
Describe the input, expected output and boundaries that must stay intact.
Inspect the work
Review the proposed edits and any commands before relying on their result.
Check the outcome
Compare actual behavior with the expected result. If a check fails, investigate it before applying more changes.
Test coverage gaps
A concrete starting point
test('rejects a duplicate key', () => {
expect(() => insertExistingKey())
.toThrow(DuplicateKeyError);
});The example is a starting point for a real project, not a claim that generated code is already tested. Adjust paths, dependencies and expected behavior to match your application.