Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / mbolotov/intellij-playwright issues and pull requests
#33 - Not working with Intellij 2023.2.1
Issue -
State: closed - Opened by rener084 about 1 year ago
#32 - Breakpoints no longer work in Playwright
Issue -
State: open - Opened by ameuze about 1 year ago
- 2 comments
#31 - Version 1.3.2 Not Supported by Intellij 231.9255.16
Issue -
State: open - Opened by yareally over 1 year ago
- 1 comment
#30 - Issue running using pnpx
Issue -
State: open - Opened by thomasmillercf over 1 year ago
#29 - plugin breaks vitest support
Issue -
State: open - Opened by kontango-bot over 1 year ago
#28 - Cannot run tests, fails with: node not found
Issue -
State: open - Opened by kontango-bot over 1 year ago
- 2 comments
#27 - env: node: No such file or directory
Issue -
State: closed - Opened by lavcraft over 1 year ago
- 2 comments
#26 - Webstorm test runner is "stuck" using maestro
Issue -
State: open - Opened by rhysawilliams2010 over 1 year ago
- 1 comment
#25 - Pattern Matching of Test Not Working -> Error: No tests found
Issue -
State: closed - Opened by magbeat over 1 year ago
- 11 comments
#24 - "Inject selector language into string literals" breaks C# code suggestions in Rider
Issue -
State: open - Opened by DaBittna over 1 year ago
#23 - Question
Issue -
State: open - Opened by oimediaDev almost 2 years ago
#22 - Typescript support for playwright config
Issue -
State: open - Opened by fmquaglia almost 2 years ago
- 1 comment
#21 - Tests getting timed out are getting marked as "Passed" or they don't finish
Issue -
State: closed - Opened by sagrawal-code almost 2 years ago
- 1 comment
#20 - Run Configuration doesn't heed the runner configured nor the nodes environment from the IntelliJ Settings
Issue -
State: open - Opened by maddingo almost 2 years ago
- 1 comment
#19 - Test/Update Maestro to work with JetBrains Aqua
Issue -
State: closed - Opened by Doug-Bowen almost 2 years ago
- 1 comment
#18 - Unable to run tests
Issue -
State: closed - Opened by alveshelio about 2 years ago
- 5 comments
#17 - Anonymous describe is not handled by Maestro
Issue -
State: closed - Opened by yehuda-goose-miller about 2 years ago
- 2 comments
#16 - [Bug] Project base from Playwright configuration template is not using
Issue -
State: closed - Opened by alexandrchumakin about 2 years ago
- 5 comments
#15 - Reference to Cypress in right-click menu of test runner results
Issue -
State: closed - Opened by ghost about 2 years ago
- 3 comments
#14 - on change of files - maestro debugging fails - need restart ide
Issue -
State: open - Opened by xsoft7 about 2 years ago
- 9 comments
#13 - Does not work under Windows
Issue -
State: closed - Opened by vekunz about 2 years ago
- 10 comments
#12 - [Feature Request] Add support for playwright fixtures
Issue -
State: closed - Opened by zakhenry about 2 years ago
- 3 comments
#11 - Plugin breaks Playwright file linting, refactoring, etc.
Issue -
State: closed - Opened by bryantebeek over 2 years ago
- 4 comments
#10 - [Feature Request] Allow mechanism to specify how to find project root
Issue -
State: open - Opened by zakhenry over 2 years ago
- 3 comments
#9 - Webstorm 2022.2 support
Issue -
State: closed - Opened by sannysoft over 2 years ago
- 1 comment
#8 - "Test directory" generates weird path
Issue -
State: closed - Opened by ammut over 2 years ago
- 1 comment
#7 - "No tests were found", but running the command output by yarn does work
Issue -
State: closed - Opened by zakhenry over 2 years ago
- 7 comments
#6 - How can I define the --config flag?
Issue -
State: closed - Opened by zakhenry over 2 years ago
- 5 comments
#5 - [Question] Default Run Config when enabled
Issue -
State: open - Opened by bshostak over 2 years ago
- 8 comments
#4 - Test runner cannot find a valid package manager in 2022.1 version
Issue -
State: closed - Opened by mbolotov over 2 years ago
- 2 comments
#3 - Doesn't pick up the configuration automatically
Issue -
State: closed - Opened by carlosflorencio over 2 years ago
- 2 comments
#2 - 30-day evaluation not providing valid license.
Issue -
State: closed - Opened by ghost over 2 years ago
- 3 comments
#1 - Extension taking wrongly handling the action on a Jest/Puppeteer test
Issue -
State: closed - Opened by mattalxndr almost 3 years ago
- 5 comments