I have kept locator objects in page file. This is as per Playwright best practice.

https://playwright.dev/docs/pom

Hi akshap7,

How can I use the test explorer in VS Code to have it recognize individual tests and also be able to use an environment from your boilerplate? If I use your boilerplate I can run tests in the command line, but I cannot pick a specific test with the "npx cross-env ENV=qa npm run test:single" command. But then, if I use the basic playwright template that comes with when you install playwright, I can select different tests I want to run but I cannot select an environment.

I am after same situation haven't been successful with a solution yet.

Hi , I am thinking of a way where we can remove this cross-env dependency and try to provide ENV variables. After that I think it might solve the issue just a guess. I am also looking for solution. It might take some time but thank you for brining this up

Hi I have made changes in code instead of using cross-env now I am using process-env. Can you please check this issue once and let me know if it's fixed

@akshayp7 The changes you made allows to use trace viewer not Test explorer. I find test explorer more useful as it had debugging step by step along with breakpoints which is nicely integrated with IDE. I think trace viewer is useful when you are more after performance and network analysis. It would be great if we can use Test Explorer in your framework.

Let me look into it. Please let me know if you find something as well

I am not sure the need of passing env from command line?

It's dynamic sometimes you need to pass qa or dev environment for example if you are running on ci/cd. What if you want to run same set of test cases on dev and qa. Commiting the changes and pushing code everytime would be cumbersome so we can pass qa or dev from command line while executing tests

Right, might also depends on the project needs unless if you need to run the tests every time on other environments.