Simply Testable Blog

Figuring out how to automate away the pain of routine front-end web testing; the story behind

211 posts covering the initial idea, growth of the service, features, advances, failures and successes.

I noticed yesterday that some full-site JavaScript static analysis tests were failing quite ungracefully.

Such tests would fail without completing correctly, leaving the test appearing to be stuck in progress and never completing. This was not good.

A quick investigation revealed that such tests were being performed for web pages that linked to external JavaScript files which did not exist.

Such issues are now recognised. If a JS static analysis test is run against a web page that links to a 404ing JS resource, such a problem will be noted and present in the results for the specific test.

As a bonus side effect, any non-200 HTTP status code encountered when trying to retrieve external JS resources (not including redirects) will be recognised and reported in a similar manner.