Browser Support - Mission Impossible?
Agree browser and device combinations from audience needs, including acceptable functional and visual differences. Verify real tasks rather than recording browser names alone.
Putting implementation and maintenance into practice
Implementation includes normal, empty, error and recovery states. The interface provides feedback while the server owns authorisation, validation and persistence.
Checking the result
Test valid, invalid and missing inputs, including back, retry and duplicate handling. Keep release records and usable recovery material.
