I knew you would have the answer Jarad, as always! Exactly what I needed, thank you!

@CommitQuality

7 ай бұрын

Always glad I can help you :)

Exactly what I needed! Super simple explained :) Thank You :)

@CommitQuality

5 ай бұрын

You're welcome! Thank you :)

This is really helpful, thank you!

@CommitQuality

10 ай бұрын

Not a problem, glad I can help 😃

Many thanks for your wonderful Playwright tutorials.I learnt all Playwright from you !

@CommitQuality

10 ай бұрын

That's amazing to hear, it's what makes me continue wanting to post videos! Thank you very much for the super thanks, you are my first one😁

Instead of power shell if we use cmd then what command should I use to set the value. Please suggest the command.

Please let me know how to integrate with gh actions How to store the gh secrets to the variable present in the env files(present in env folder)

As always great content! Is there any plans to make a video about managing automated test cases? In my work, we find it difficult to actually keep track of our test cases in an Excel sheet to understand our total test coverage. If you made a video on that it could be potentially really helpful to a lot of people :) thank you for these tutorials!

@CommitQuality

9 ай бұрын

This is a really interesting comment. I can definitely give an example of what I do / what I would do on my test website. I will put something together for this because I really like the idea.

thanks, i'm practicing playwright automation and azure pipelines and this was very easy to follow and understand. i've set up a practice build pipeline with a custom agent that runs my playwright tests and i have created a release pipeline aswell, but i'm struggling to get my head around how it'll work with azure releases to qa, prod and then uat. im guessing its something to do with the yaml file?

@gdd546

Ай бұрын

i found it in your azure pipeline video

Thanks, bud.

hi, thanks a lot for your video. Is it suppose to work with bush instead of pwsh? I've got such error. $env:ENV="deploytest" bash: :ENV=deploytest: command not found

@7contractors

5 ай бұрын

You have probably forgotten to fix you scripts in package.json

can you set default .env that will be used when not specifying the env when running the tests?

@CommitQuality

9 ай бұрын

Yes you can do this in the playwright config file. You could set up a const that would say use whatever base env is, and if its empty, set it to something e.g. const defaultEnv = process.env.ENV || 'prod' and then use the const where you define the path of the file. So if my ENV variable is empty, it will take the base version

Thanks for the vid. Nicely explained. One question, though. I can easily use the env variables in the test block of code, as presented in the video, but I cannot use them inside the setup code (in the auth.setup.ts file). Returns undefined. Any suggestions? Thanks!

@CommitQuality

8 ай бұрын

Thank you! Where are you originally creating your variables and are you using the playwright setup approach?

@rexrexnis

8 ай бұрын

I have them stored in a .env file (just one file, as there is one environment as for now). And as i said, they do work within a test file, but i also need to use them in the authentication setup, which is taken directly from the playwright documentation. And it does work itself (the setup I mean), but at this moment I have the secrets passed as normal strings….

@rexrexnis

8 ай бұрын

​@@CommitQualityany advice?;)

Great stuff, simple and effective. Spent an hour to trying figure this out with some random StackOverFlow comments..

@CommitQuality

3 ай бұрын

I'm glad to hear I have helped :)

Thanks for this great content. Please I have a question, I'm getting this error when I ran this command $env:ENV='local'. I don't have powershell in my terminal as I'm using Mac: zsh: command not found: :ENV=local Please what can I do. Thanks

@18traspie

3 ай бұрын

for zsh use "export ENV=local"

Hi you make amazing videos which cleared my many doubts, I have question how can I use this as script in package.json file instead of running in command line I tried to use cross-env but didn't got it if you can share a script would be great thank you in advance

Beautiful content. Could you also please show us how to change the environment file on test run command. I mean is there any way to call the desired env file with 'npx playwright test' so we can avoid switching between the env files before running 'npx playwright test' command? something like-> npx playwright test --env '.env.local'

@marko96

10 ай бұрын

Try using bash instead of powershell. The command for bash would be: ENV=local npx playwright test The downside is that you have to write ENV=local/prod before executing every test but its still one step less than with using powershell in which you set the env and then run the test.

@CommitQuality

10 ай бұрын

What I typically do is run a powershell script. Inside the script I can set the env variables I want and the. Also run the npx Playwright test command. I would then execute the powershell script

@rifattaque7301

10 ай бұрын

@@marko96 sounds good, gonna try that. Thanks buddy.

Hi, is there a way to check data of file and then choose which one to use.

@CommitQuality

7 ай бұрын

When you say check data of a file, do you mean the content of any file, or a specific one? I have videos on reading from CSV files and soon to be ones from pdfs

@vaishalisoni8022

7 ай бұрын

@@CommitQuality I mean we have different env like stage, prod etc and we save json data for each env in each of these files and on the bases of req we call these files.

@vaishalisoni8022

7 ай бұрын

Also tried above approach but env variables are not populating.

Can we hide password in this file, so no other can see it in git commits.

@CommitQuality

7 ай бұрын

You may want to look into git secret

@riteshkavankar

7 ай бұрын

@@CommitQuality Done👍🏻

Hello,Please share your github url

@CommitQuality

4 ай бұрын

github.com/CommitQuality

@webtestingui7187

4 ай бұрын

Thank you @@CommitQuality

I need a little assistant. In terminal I type this: $env:ENV="prod" but when I run the basic test and log ENV variable 'console.log(process.env.ENV)' then I got "undefined" result.. I am bit lost... dotenv.config({ path: `./env/.env.prod` }) -->this works dotenv.config({ path: `./env/.env.${process.env.ENV}` }) this failed...

@CommitQuality

9 ай бұрын

What type of terminal are you using?

@kovacstibi9595

9 ай бұрын

powershell but today morning everything works.. bit confused.. maybe the restart solved... (I am new with typscript/playwright/visual code) anyway thanks! your videos are awesome!@@CommitQuality

@CommitQuality

9 ай бұрын

The classic turn it off and on again :D Thank you :) @@kovacstibi9595

@ramprasadprathapani3578

9 ай бұрын

This will help us for undefined in dotenv.config block path: './env/.env.' + process.env.ENV_Test