A base assumption of the nemweb library is the expected files & formats on the nemweb file server(s).
Shifting to using HTTP mocks with fixtures (ref: #7) will mean the current test breakages caused by both file & format changes and/or intermittent issues with nemweb won't be visible. Thus it is advisable to include integration tests that ensure the assumptions remain correct.
Questions:
- should there be live integration tests?
- should they be run on PRs? (Note: travis or similar to be set up)
- should they break a build?