Use more than a successful code-generation message as evidence.
1. Compilation and analysis
Build the affected variant and run relevant static checks. A successful generated snippet does not establish integration compatibility.
2. Runtime checks
Verify the changed behavior on an emulator or device, including recreation and relevant OS differences. UI work often needs screenshots or interaction evidence.
3. Failure handling
If a check fails, preserve the failure output and investigate the actual cause. Do not silence tests or weaken assertions merely to produce green results.
Worked scenario
An inset migration compiles but places a bottom button under system navigation. A device interaction catches the issue that compilation cannot.
Apply it
Create a before-and-after verification record with a relevant negative or edge case.
Check your understanding
Your evidence demonstrates behavior rather than merely successful generation. Explain the decision and show evidence from your implementation or design. If you cannot demonstrate it yet, revisit the relevant section before continuing.