-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
[Bug]: Various Project Configurations for different browsers do not show in UI mode when tests are located in sub directory. #34050
Comments
What is "various Project browser configuration"? Please follow the issue template and file something we can reproduce locally. |
I have shared the config in the link above. |
It is unclear what your expectations are and what the actual behavior is. Could you be more specific? The archive you attach is an empty folder with the git index files. |
Thank you for the support. For your clarification, this is what I get when the tests are moved to a subdirectory: This is what I get when the tests are moved to the project root directory: I want the different browsers to show even when the tests are in subdirectory. Please suggest. |
When you run it in subdirectory it does not see your config file. Run it in the outer directory. |
Can you please tell how to run in outer directory? |
That's the right way of running. Sadly I can't help much without a clear minimal repro. |
I am sharing the repo again. |
Version
1.49.1
Steps to reproduce
Initialize default playwright project typescript
Open UI mode
Tests show up in UI mode with various Project browser configuration.
Move the tests to a subdirectory
Open UI mode
Tests show up in UI mode without the various Project browser configuration.
Expected behavior
Tests show up in UI mode with various Project browser configuration.
Actual behavior
Tests show up in UI mode without the various Project browser configuration.
Additional context
Test path:
src/tests/form_page.ts
PW Config: https://paste.ubuntu.com/p/zhGvv5Zw5W/
Environment
The text was updated successfully, but these errors were encountered: