Quick resolve: what to test

Review branch review/quick-resolve · version 4.2 · based on production release 27c4a7b.

1. Work through the queue

1. With all filters cleared, expect 5 avisos · 4 para resolución rápida. The existing insurance alert has no quick action and is excluded from the queue.
2. Press Resolver pendientes. Ford Transit should appear as Pendiente 1 de 4. Try saving without a result: the form should stay open and ask for one.
3. Select Favorable, keep today's date and the suggested next inspection date, then Guardar y siguiente. You should reach the Toyota maintenance task without leaving Alerts.
4. Cruce de neumáticos is selected. Also select Filtro de combustible to simulate doing both jobs. Enter 100100 km and 45 as the total cost. Save once.
5. On the Nissan ITV, press Omitir por ahora. It stays pending. On its maintenance setup, enter Revisión del elevador and 10000 under Cada X km. Leave the historical date and mileage blank and save.
6. The summary should show 3 saves and 1 skipped. Back in Alerts, the Nissan still needs an ITV and now has a missing-history alert. Setup must not invent a completed service.

2. Check history and persistence

• Open Ford from the fleet. Its original failed ITV and the new favorable inspection should both remain in its history.
• Open Toyota. Expect one new service listing the two selected jobs, a service cost of €45, and mileage 100,100. Its total spending includes the demo's pre-existing €50 ITV, so it should show €95.
• The air-filter baseline should stay unchanged. Refresh the page: the saved service, mileage and inspections should persist.
• Return to the Nissan's Completar datos shortcut. Enter 29500 for the last maintenance mileage. Saving fills its baseline without creating a new service. The skipped ITV stays pending.

3. Test a failure and retry

1. Reset the demo. Press Probar fallo de guardado, then open Alerts and filter Tipo → Mantenimiento.
2. Start the queue. Enter 100100 km and 45 cost, then save. The intentional failure should keep the same vehicle, selected work and entered values visible.
3. Press save again. Expect one service, one mileage update and a completed queue. A quick double-click must not save the next vehicle's task.

4. Filters and single-item actions

• Reset again. Search DEMO 003 or Toyota: only its pending work should remain. Try Tipo and Prioridad together. The queue uses the visible filters.
• Use Registrar mantenimiento → on an individual alert. Its form should say Resolución rápida and have a plain Guardar button; saving returns to Alerts.
• On Ford, record another Desfavorable inspection. It should save into history but leave the vehicle requiring attention. The summary must not claim it was resolved.
• Enter a note, then cancel or skip. Declining the discard confirmation must preserve the form.

5. Phone and keyboard

Try a narrow browser or phone. Filters should fit, and the quick form should scroll while Guardar, Omitir and Cerrar stay reachable. Use Tab and Shift+Tab inside the form; Escape should close an unchanged form or ask before discarding edits.

Scope

This version adds maintenance, ITV, missing-history and initial maintenance-setup actions. It does not add insurance renewal, multi-vehicle bulk saves, booking states or reminder snoozing. Existing document alerts and editors remain available.

Quick maintenance entries explicitly link to selected maintenance rules, including custom names. Old service records retain their existing matching behaviour. Editing a linked service exposes its associations so you can deliberately remove one.

No Firebase rule changes, SDK upgrades or data migrations are required. Automated tests use fictional data and local emulators. The preview cannot validate production sign-in or real fleet data.

Return to the review app →