Revision 4e2aad5edc375c9ae27420bce8ae3251661cc7e0 authored by jugglinmike on 22 February 2017, 20:04:24 UTC, committed by Simon Pieters on 22 February 2017, 20:04:24 UTC
At the onset of a given test, the shared application manifest may or may not already be available in the user agent's cache. Because this variability is controlled by external factors (specifically: the previous tests executed in the session), the status of the application cache may not be consistent. Tests whose semantics are effected by this status must therefore explicitly control for the variability in order to exercise the same behavior in all circumstances. Update the test for successful invocation by accounting for both "manifest ready" and "manifest not ready" states. Update the test for unsuccessful invocation by specifying a URL to a non-existent resource.
1 parent cec5972
Computing file changes ...
