A free suggestion, never ever save user credentials in a file. For any reason (even for teaching someone on UA-cam) whatsoever. I dropped as soon as I saw that. Sorry
Thank you for the suggestion Akash, this is just a dummy website that is just for teaching purpose created by lambdatest, in company projects are more secure in git or cloud and in runtime we get credentials from cloud, depend upon companies policy, even we can create environment variable and store in file to use the credentials thank you I hope you will like it another series is also coming on Playwright BDD where I will show case to secure credentials thank you for your suggestion buddy
@@Test-Rover-Automation Cool. I have been following Playwright community closely. Even the devs who created it and the best practices. I will not(ideally no one would) recommend to use it with BDD(if you meant Cucumber). Using Playwright with any other framework will diminish its effectiveness and ability to inject fixtures, object. Also, you will write redundant configs or code to retry, prepare reports, sharding and even for CI. Playwright has been designed to do all these and much more in-house. Playwright Runner is why Playwright is so catching up recently. BDD is like using Ferrari with its breaks on all the time.
@@lifeofakashh Hi Akash I know playwright community haven't created this but I am using BDD approach explained in this video hope you will like it, sorry but this was done previous your comments but next video I will show to hide credentials logic hope you will like it thank you for your feedback ua-cam.com/video/7neceStpHp4/v-deo.html
@@lifeofakashh Just for your info akash I am still using playwright test runner here, so I am not killing any feature of the playwright hope you will like it, please give some feedback thank you
Your demonstration of data-driven techniques and framework usage is highly informative.
Thank you
A free suggestion, never ever save user credentials in a file. For any reason (even for teaching someone on UA-cam) whatsoever. I dropped as soon as I saw that. Sorry
Thank you for the suggestion Akash, this is just a dummy website that is just for teaching purpose created by lambdatest, in company projects are more secure in git or cloud and in runtime we get credentials from cloud, depend upon companies policy, even we can create environment variable and store in file to use the credentials thank you I hope you will like it another series is also coming on Playwright BDD where I will show case to secure credentials thank you for your suggestion buddy
@@Test-Rover-Automation Cool. I have been following Playwright community closely. Even the devs who created it and the best practices. I will not(ideally no one would) recommend to use it with BDD(if you meant Cucumber). Using Playwright with any other framework will diminish its effectiveness and ability to inject fixtures, object. Also, you will write redundant configs or code to retry, prepare reports, sharding and even for CI. Playwright has been designed to do all these and much more in-house. Playwright Runner is why Playwright is so catching up recently. BDD is like using Ferrari with its breaks on all the time.
@@lifeofakashh Hi Akash I know playwright community haven't created this but I am using BDD approach explained in this video hope you will like it, sorry but this was done previous your comments but next video I will show to hide credentials logic hope you will like it thank you for your feedback ua-cam.com/video/7neceStpHp4/v-deo.html
@@lifeofakashh Just for your info akash I am still using playwright test runner here, so I am not killing any feature of the playwright hope you will like it, please give some feedback thank you
Hi Akash I hope you like this video using playwright fixture and playwright test with BDD ua-cam.com/video/j6nmcxdGCy8/v-deo.htmlsi=8HoujLi0vVupCuIN