Tests: Make resources locally accessible

[adamjanovsky]

For now, many of tests rely on downloads from commoncriteria.org, which itself is quite unreliable webpage. Apart from test that check the correctness of such downloads, we should rely more on local resources, so that the tests don't fail due to inaccessible cc web.

[J08nY]

We could maybe cache the commoncriteria contents somewhere (I could setup a caching proxy at seccerts.org) or just dump it periodically (again at seccerts.org) and point tests there.

[adamjanovsky]

No need really, I was just being comfy. Basically we distinguish two situations:

1. We want to test download from CC site: We should really download from CC site
2. We want to test something else: Usually one pdf will do, no more than 5 distinct are needed, we can store them in git, they do not change.

The problem is that even in the second case, I'm now fetching the pdfs from commoncriteria.org, which sometimes fails.

[adamjanovsky]

Temporary workaround -- make those test not fail the pipeline.

[adamjanovsky]

@mmstanone Can you imagine dividing your tests into two parts: (i) tests of downloads; (ii) test of other functionality? Where:

• (i) test that downloading works properly from the website, these are allowed to fail
• (ii) tests anything else and uses local pre-downloaded resources that. Alternatively, these don't have to be hosted in git, but on seccerts.org. Probably, we would need some toy datasets, otherwise we get too large downloads.

[adamjanovsky]

Tests that require remote and unreliable resources can fail now. This was done as a part of #275