Automate browser regression testing

[NoiSek]

Merged from #66, #68. Initial attempts to solve #68 lead down a long path of chained dependencies and unplanned requirements. It seems that solving the larger issue of browser regression testing is better outlined in it's own ticket before the underlying frontend testing tickets are addressed again.

Purpose:

This ticket is meant to address build instability at a very basic level, simple "Does it run without errors" testing. This would prevent developers from introducing breaking changes without being explicitly aware that they are doing so.

Resolution:

Introduce global page sanity checks as one of our tests. Load page, check for Javascript errors, pass or fail.

Steps to resolve:

While technically doable within Mocha, this is almost definitely better solved using Pytest.

• Install Selenium
• Create a pytest fixture for application URLs (derived from module blueprints)
• Write a test that loops through all URLs and checks for console errors.

Both of these require that the devserver is able to run on Travis. ( Making it partially blocked by #67 )