EV charging app testing checklist

Download the checklistMarkdownCSVBrief (Markdown)

1. 1.release smoke testsDone when: On the release build, using the demo station and test account given to store review, a test driver finds a station on the map, starts a session on a test charger, stops it and receives a receipt, and billing on the receipt stops at the stop tap.Risks: store-rejection, money-loss. Tool class: mobile automation. Usually run by: QA engineer.
2. 2.resilience and failure testingDone when: With the roaming network or charger link cut mid-session, the app shows the session as interrupted, billing stops, and the receipt matches the energy delivered before the cut.Risks: dependency-failure, money-loss. Tool class: chaos tool. Usually run by: developer.
3. 3.data integrity and migration testingDone when: For a sample of sessions, the kWh on each receipt matches the charger's meter values and the amount charged matches the price shown at start.Risks: money-loss. Tool class: data validation. Usually run by: developer.
4. 4.payment and money-flow testingDone when: A session stopped early, a session the charger aborts and a declined card each end with one charge matching the energy delivered and no held amount left on the test card.Risks: money-loss. Tool class: API client. Usually run by: QA engineer.
5. 5.end-to-end functional testsDone when: The price per kWh shows before the driver taps start, and a charger the backend marks out of order shows as unavailable on the map.Risks: wrong-decisions, regulatory-penalty. Tool class: mobile automation. Usually run by: QA engineer.
6. 6.accessibility testingDone when: A screen reader user finds a station, starts a session and pays in the app without sighted help.Risks: accessibility-liability. Tool class: accessibility checker. Usually run by: accessibility specialist.
7. 7.compliance checksDone when: A signed checklist for each market shows price display before start, accepted payment methods and the published reliability data, with a screenshot or link for each.Risks: regulatory-penalty. Tool class: test management. Usually run by: product manager.
8. 8.integration testsDone when: Start, stop and meter messages between the backend and a test charger, and through a roaming partner, produce the same session record on both sides.Risks: dependency-failure. Tool class: API client. Usually run by: developer.