Repeatable test workflow
Vehicle Template Validation Checklist
Use this checklist before spending time on a complex design. It separates template selection, browser export, USB preparation, and vehicle-side behavior so a failed test produces useful evidence.
1. Record the test context
- Vehicle model and the closest template name shown in the editor.
- Browser, operating system, and editor page URL.
- Vehicle software version and region when known.
- Date of the test and whether the feature appears in the vehicle UI.
2. Create a diagnostic design
Start with four large, distinct color regions and one simple original shape. Avoid logos, photographs, tiny text, gradients, and transparent edges. A diagnostic design makes rotation, mirroring, cropping, or wrong-panel mapping obvious without introducing artwork complexity.
3. Verify the browser export
- Export directly from the matching editor without resizing afterward.
- Confirm the downloaded file is a PNG and opens normally.
- Record its pixel dimensions and filename.
- Keep the original export unchanged for comparison.
4. Prepare storage carefully
Follow the instructions currently displayed by your own vehicle. Check the drive format, expected root folder, filename rules, and whether another vehicle feature shares the storage device. Do not assume instructions from a different model, market, or software release are identical.
5. Change one variable per test
If the file does not appear, first test a shorter filename; then test a clean folder; then test another known-good drive. If it appears but maps incorrectly, keep the storage setup unchanged and try the nearest template variant. Changing one variable at a time makes the result reproducible.
6. Report a useful result
A useful report includes the editor URL, selected template, export dimensions, expected result, actual result, and exact reproduction steps. Screenshots of the browser preview and vehicle display can help, but remove account, location, VIN, and other private information before sending them.
What this test cannot prove
A successful visual test does not certify universal compatibility, color accuracy, rights to uploaded artwork, or support across future software versions. It only documents one reproducible result under the recorded conditions.