We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
As seen here, moving the addons-frontend config within the base docker-compose.yml file to the docker-compose.selenium.yml file would fix that issue.
addons-frontend
The secondary compose.yml should probably be renamed to docker-compose.ui-tests.yml or something like that.
The text was updated successfully, but these errors were encountered:
Note that with #5927 there now already is a tests/ui/docker-compose.selenium.yml file.
tests/ui/docker-compose.selenium.yml
Sorry, something went wrong.
Yup, what do you think about renaming it?
I really don't have a preference, we could even drop the .selenium postfix and just name it docker-compose.yml 🤷♂️
.selenium
docker-compose.yml
Well I think it should have some kinda reference, but okay good to know.
See also: #6120
@willdurand that was fixed here mozilla/addons-server#10143.
b4handjr
No branches or pull requests
As seen here, moving the
addons-frontend
config within the base docker-compose.yml file to the docker-compose.selenium.yml file would fix that issue.The secondary compose.yml should probably be renamed to docker-compose.ui-tests.yml or something like that.
The text was updated successfully, but these errors were encountered: