Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Reactivate integration tests for core-web and public-web #116

Open
ursjoss opened this issue Aug 29, 2019 · 0 comments
Open

Reactivate integration tests for core-web and public-web #116

ursjoss opened this issue Aug 29, 2019 · 0 comments
Labels
chore

Comments

@ursjoss
Copy link
Owner

ursjoss commented Aug 29, 2019 •
edited
Loading

In the context of running postgresql in a docker container for jOOQ code generation and for integration tests (#88), I had to disable the integration tests for public-web (see ticket #112).

I renamed the path for the respective test-set from core/web/src/intTest to core/web/intTestDisabled.

core-web inherits the multiple datasources defined in core-sync it depends on.

Find a way to reactivate those tests.
@ursjoss ursjoss added the chore label Aug 29, 2019
@ursjoss ursjoss moved this to Backlog in SciPaMaTo - Board Jan 4, 2023
@ursjoss ursjoss changed the title Reactivate integration tests for core-web Reactivate integration tests for core-web and public-web Mar 27, 2023
@ursjoss ursjoss mentioned this issue Mar 27, 2023
Merged
@ursjoss ursjoss moved this from Backlog to Next 3 in SciPaMaTo - Board May 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
chore
Projects
SciPaMaTo - Board
Status: Next 3
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ursjoss