Re-enable integration tests

[martin-helmich]

No description provided.

[martin-helmich]

@mfal As announced, this is something that I had difficulties with. In the current setup (Jest + ts-jest), oclif seems to have issues importing the concrete command files (which just hangs indefinitely, with the tests eventually timing out). I also tried other setups (like using Babel¹), but ran into other problems with those (for example, not processing the TSX files or difficulties with ESM imports).

Any thoughts?

Footnotes

1. https://jestjs.io/docs/getting-started#via-babel ↩

[gandie]

@martin-helmich brought this one back to life ( to make it a draft then 😆 ).
Would love to see such tests running again, as they would greatly increase my confidence in changes. First step was to rebase on top of current master and creating a plan how integration tests might look like in the future ( see plan document i've added ).

tl;dr : Use mockoon ( or something else ) plus already prepared environment variable switch to alter mittwald API base URL. This would allow real HTTP requests to run during tests, no mocking for that needed. By altering and specializing the mockoon schema we could provide HTTP responses matching our test cases ( if an example response does not fit already ).

[gandie]

Getting somewhere:

[run-all] execution complete: 185 commands
[run-all] statistics: successful=100, failed=85, total=185

Failed commands mostly come from missing arguments, the command discovery misses some.
Yet, at least two errors from current error log caught my eye already, will analyze them when fog has lifted.