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.

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

Configure MockServer to allow parallel execution of integration tests #193

Open
mcollovati opened this issue Mar 27, 2023 · 0 comments
Open
Labels

Comments

@mcollovati
Copy link
Contributor

Currently, every integration test that collects traces starts an instance of MockServer and some of them fails because the server port is already bound.

To allow parallel execution, we should start the server only once per test suite, either by setting @MockServerExtension.perTestSuite=true on every test or by configuring the MockServer maven plugin.
In addition, we also need to make sure that tests only assert on traces produces by their own interaction, for example by filtering spans by vaadin.sessionId or vaadin.frontend.id attributes.

Note: the example MockServer maven plugin configuration binds the start goal to the process-test-classes, probably because it wants to use it also for unit tests. We can instead use the pre-intergration-test phase.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant