search

mbolotov / intellij-playwright

1 stars 0 forks source link

[Question] Default Run Config when enabled #5

Open bshostak opened 2 years ago

bshostak commented 2 years ago

Hi, leaving this question here for now.

When using Maestro and having the plugin enabled, it works great so far with running playwright. However, if I switch to another project within intellij that I used a different runner for (say protractor), it starts defaulting those test runs to the playwright maestro runner instead.

Is there anyway to fix that besides disabling Maestro plugin?

mbolotov commented 2 years ago

Hi Brian, Please make sure you have this option disabled in the settings: image

bshostak commented 2 years ago

@mbolotov thank you! I believe this was off by default. I've double checked to make sure and will let you know if this happens again!

bshostak commented 2 years ago

@mbolotov So with this option still disabled, i'm seeing the same behavior. I have one window of intellij running a project with playwright and the Maestro runner works fine. I have another intellij window open running a project with protractor. If I run a test in the framework with protractor, it wants to default to the playwright runner and will not let me change runner to what I previously used. If I disable Maestro, restart intellij, then that behavior doesn't happen and it runs via the protractor runner as expected.

rickirunge commented 2 years ago

Any updates on this? Seems like the "Supress other suggested Run Config..." is always enabled - no matter if the checkbox i marked or not.

Only way to get other run configs (Jest, Cypress) back is by disabling Maestro plugin and restart IntelliJ.

rickirunge commented 2 years ago

This looks to be related to https://github.com/mbolotov/intellij-playwright/issues/1 which I just tried out, but still not ala to get it to wook, without diasabling Maesto plugin.

mbolotov commented 2 years ago

I'm sorry, I missed that this ticket was reopened. Could anyone provide a sample project to reproduce the problem? I tried those two:

  1. https://github.com/mbolotov/playwright-example (contains PW, Cypress and Protractor cases)
  2. https://github.com/qualityshepherd/protractor-example.git

Neither in separate projects, nor in single project, I see no problems. IDE suggests PW configurations only for PW cases, the same for Cypress (with the appropriate plugin installed). And it suggests both Jest and Mocha for a Protactor case.

rickirunge commented 2 years ago

Just found that the problem might only be related to the run icon on the top level describe() in a Jest file. Seems like I get the multiple choise of runners on test() (or alias id() ) and nested describe()

vekunz commented 1 year ago

I have the same problem with Vitest. We have some projects with Playwright and some others with Vitest. If I use the run icon on the top-level describe(), Maestro starts Playwright. If I right-click in the editor or the file tree and click the 'Run' context menu option, Maestro wants to run Playwright also.

I can reproduce it with the basic example of Vitest https://github.com/vitest-dev/vitest/tree/main/examples/basic