-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Closed
Labels
meta: staleThis issue/PR is stale and will be closed soonThis issue/PR is stale and will be closed soonteam: webappIssue belongs to the WebApp teamIssue belongs to the WebApp team
Description
Is your feature request related to a problem? Please describe
There are existing integration tests for Meta 1, 2, 3 and 4 (:trophy:), but, they may not be running with automation, therefore, they only protect us if run manually.
Describe the behaviour you'd like
The tests are scheduled to run nightly from main. Any more frequently, and it might hit API limits/quotas.
Describe alternatives you've considered
- First, setup a way to categorize / classify / differentiate between unit and integration tests for Mocha.
- Second, package the tests in a container, it'll execute the tests when run. (this might be overkill / too much)
- Third, schedule the tests run on a cadence.
Categorization options
- Move integration tests to exclusive JS files, include the word
integration
in the filename, and use the grep feature of Mocha to run integration tests in a scheduled job.
Packaging options
- Create an asset like this with Leeway, which contains our Go integration tests.
Scheduling options
- Create a new Werft job, similar to this one, which runs Go integration tests, but have it run nightly (rather than with every build).
- Setup a job another way? It depends what our long ter
Additional context
I learned about the TypeScript integration tests here.
They are also mentioned to be setup in #5367.
Metadata
Metadata
Assignees
Labels
meta: staleThis issue/PR is stale and will be closed soonThis issue/PR is stale and will be closed soonteam: webappIssue belongs to the WebApp teamIssue belongs to the WebApp team