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

UI tests with Elasticsearch failing, if there are multiple of them (OSOE-977) #431

Closed
DemeSzabolcs opened this issue Jan 23, 2025 · 2 comments
Labels
bug Something isn't working

Comments

@DemeSzabolcs
Copy link
Member

DemeSzabolcs commented Jan 23, 2025

This is the error that I get:

Image

This can be reproduced locally too. It happens when you clear the AppData folder but you don't recreate the Elasticsearch container in the docker. The same happens on GitHub when multiple tests are present. That's why if one test is running it's okay, but if we have multiple tests, it re-setups the site but doesn't recreate the Elasticsearch container.

Jira issue

@DemeSzabolcs DemeSzabolcs added the bug Something isn't working label Jan 23, 2025
@github-actions github-actions bot changed the title UI tests with Elasticsearch failing, if there are multiple of them UI tests with Elasticsearch failing, if there are multiple of them (OSOE-977) Jan 23, 2025
@Piedone
Copy link
Member

Piedone commented Jan 23, 2025

The tests can just use indexes with different names. Either the index name itself can be different, or you can create different tenants (CreateAndSwitchToTenantAsync()) so their prefixes are different.

@DemeSzabolcs
Copy link
Member Author

DemeSzabolcs commented Jan 23, 2025

I think it's actually simpler than I thought. You are right, we can just modify the index name as you said, and that could be done from the Elasticsearch recipe. No need to modify the workflow or do anything in the UI Testing Toolbox.

So the problem was, that we used the main tenant for the tests with two different setup recipes (both using ES), but with the same index name in the ES recipe.

So it's basically not a bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants