TestCafe Integration Tests

[slowr]

Description of PR

Introduce TestCafe integration tests on CI.

What component(s) does this PR affect?

• Back-End (Database, Microservices, Containers, etc)
• Front-End (Flask, API, etc)
• Docs
• Build System

Does the PR require changes on other components? If yes, please mark the components:

• Back-End (Database, Microservices, Containers, etc)
• Front-End (Flask, API, etc)
• Docs
• Build System

Related Issue

Resolves #

Solution

Type

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Docs update
• None of the above

Checklist:

• I have read the contributing guide and my code conforms to the guidelines.
• This change requires a change in the documentation.
• I have updated the documentation accordingly.

[slowr]

To run these test you can run with:

docker run -v ${PWD}/testcafe:/tests --net=host -it testcafe/testcafe chromium:headless /tests/**/*.js

Planing to integrate it with SemaphoreCI. We should run the whole platform in test mode and then run these tests. @vkotronis Do you think we should have a global test docker compose instead of seperate like we have in backed?

[vkotronis]

To run these test you can run with:

docker run -v ${PWD}/testcafe:/tests --net=host -it testcafe/testcafe chromium:headless /tests/**/*.js

Planing to integrate it with SemaphoreCI. We should run the whole platform in test mode and then run these tests. @vkotronis Do you think we should have a global test docker compose instead of seperate like we have in backed?

@slowr let's have separate for now (as with backend). We can test the frontend and the backend separately that way (if it makes sense).

[vkotronis]

Just update the changelog, ready to merge on my side.

[slowr]

🏃 Benchmark Results 🏃

• BGP Updates (updates/sec): 1285
• Hijacks Detected (hijacks/sec): 92