Aspera Testing

The existing test base for Aspera is very small/limited and doesn't give us the enough confidence to rely on it as a safety net for all the developments, refactors and also bug fixes that are needed.

The main goal is to improve and expand our testing coverage for the Aspera Connector. But, to achieve that, we should consider the following goals:

1. Analyse and document the existing test base;
2. Make sure we have a clear distinction between all the test layers (e.g. linting, unit, visual regression, integration, functional, manual, ...) and that we are aware of what should be tested, how it should be done and in which layer;
3. Identify technical requirements and limitations around the chosen strategy;
4. Consider the usage of Rainforest and its possible challenges (e.g. environment setup to include Aspera Connect Client, Aspera nodes setup, S3 space, time needed to test)

Aspera Regression tests: https://nuxeowiki.atlassian.net/wiki/spaces/QA/pages/864289074/Aspera+-+Regression+Tests