Write test automation infrastructure

[plutec]

Write all the infrastructure necessary for all the automated testing, from deployment to end-to-end tests.

[drimer]

Just tracking some of the work on this.

Basic test coverage that doesn't have any dependency on network capabilities can already be implemented. This was introduced in 3ccb5a64a5baa22d2ff83943a09e053ab8300586.

Now, I'm working on network-dependant tests. I've got two possible approaches, which I'm looking into at the moment:

• Use Mega's testing credentials. This would allow the tests to sync all the data they need and retrieve it so as to ensure everything works as intended. My work on this approach is on the branch unit-tests-with-mega-account
• Write a complete mocking system that emulates Mega. This would:
  • Make it easy for the tests to explicitly specify what answer should come from Mega.
  • Isolate the test environment from production enviroment (and therefore, removing the need of an internet connection).
  • Require an extra mechanism to redirect all HTTP traffic to the mocked system.

[plutec]

Uff, I think that the first option is better. It is required less work and is more realistic.

[drimer]

Write a complete mocking system that emulates Mega.

After some thought, it doesn't look so daunting and could be worthwhile. I'm dsigning its principles on unit-tests-mocked-server. I'll be updating these self-notes with further information if I come across any outstanding issue.