integration tests

[tomas-kulhanek]

Add integration tests

[tomas-kulhanek]

@ollie
please check only last commit Because this is based on #54

[ollie]

Is this #54 a prerequisite for this PR to run properly? I'm getting same unautohrized errors in both unit tests and integration tests in this branch.

[tomas-kulhanek]

@ollie
This is how I did it:

• composer install (if you've done this before, run composer update, because there are new dependencies)
• cp .env.example .env
• fill in the correct data in .env
• composer test:phpunit

If you look at Github action, the unit tests are fine and the integration tests fail because there is no data in secrets, see yesterday's email.

[ollie]

Ah, we may have misunderstood what integration tests are. In our world they don't connect to external service, so you still have to mock things, but you just test more interconnected steps. I don't think we'd want to do this against production DB, but we have staging server which could be used for that, just need some input from Eda if he'd like that or not.

[tomas-kulhanek]

Sure, that would be great. We could call it acceptance testing. But in libraries, technically, I think they are integration tests.
Running against production will definitely not be the best option.

We could make it so that they don't run automatically, but leave them for manual execution. At that point, they wouldn't run in GHA, but the developer would run them themselves on their machine.

[ollie]

Makes sense. It would require to override the main URL endpoint. I'd still wait for Eda before hacking things further.