You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
github-actionsbot
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
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.
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.
This is the error that I get:
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
The text was updated successfully, but these errors were encountered: