วีดีโอ

Great video tutorial on C# and Playwright! Super clear and helpful. For your next video, it would be awesome to see a tutorial on setting up Azure Pipelines for Playwright tests. Thanks for sharing your knowledge!

Super Helpful!, Continue the great work

Thanks for this video, its quite helpful

I am currently planning out a conversion of several large SpecFlow Projects. I am having issues with Reqnroll autogenerated the Designer code for the Feature files. Not sure what actions I can take to regenerate these in Reqnroll as they still reference TechTalk.SpecFlow.

Thank youuuuuuuuuuuuuuuuuuu sooo much

can we interact and inspect the elements of a cross domain with playwright?

Thanks, it helped to start. Real life example would be very appreciated :)

I have an existing automation suite. How can I implement artillery on some features of this suite? Do I need to create a new project, copy some of the features, and implement artillery?

Can we get reports like allure?

Hey could you make videos on integrating playwright with browserstack? Or videos on how to use github actions, docker, sonarqube for tests would be great Thanks!

Thank you so much!

Again, great series. I have a simple question, do you see a way that we could use Playwright to call an API? We have the Page object, but was wondering if you found a way to call an API? The scenario is that I might need to load some data via an API, then the user logs in and searches for the data object, then I would hit another API to have the data being changed by an external user, then in the UI the user sees the change. This is very simple flow, but we do trigger APIs to perform some interaction outside the user control. So, this might not be achievable yml, but thinking we could use playwright or axios to manage the API calls. I think what might need to happen is to have the browser passed in just like the page and test in artillery, that would require a patch to artillery, but wondering if you had any other suggestions?

Great series very helpful. Now, I have been having a play, and was wondering in the advance course, is it correct that in the yml we should only call one test function in our scenario? For example I have a login and a logout functions, so in the yml I assume that you would need to create a login-logout test function to be called rather than using a flow. I am assuming this sine the page object may or may not transition correctly. I also found that the yml does not understand namespaces. Overall, these seems to be limitation, but really awesome that I can use the same code fro e2e testing with Playwright and create load tests with artillery. Thanks again, but interested on managing larger flows, and what you recommend.

Wow, these locators are very rigid and essentially present no advantage over simply writing out the locator in Xpath or some such. This video was a little shocking. Starting to doubt the utility of playwright unless I were to also have agency over the product that I'm testing.

Are the subjects yielded sent to log function ?

Saved my life...

why can't we chain the .log directly to the invoke function ?

Thank you for the videos! They are really helpfull! Please do a video to setup the new Artillery Cloud to visualize the results!

Make sure not to log credentials! Don't create a security risk with testing and hide them away with "type(password, { log: false });" The cypress example does not follow it's own recommendations.

2:58 four hours ive spent trying to get this to work, thank you very much

Hi!! For sorting the order date for a sales order, is there any query params we can send through request url?

tysm dude ur the best

Hey! I've abstracted repeating actions into methods,which are used within all e2e tests. The problem is it fails in CLI due to reason which have something to do with cypress code reading specificity in CLI. From what've red it states that cypress works with DOM elements directly during CLI tests,so it runs faster in a way,what causes fails. At the same time,in test runner,cypress immitates real user experience which allows DOM to be rendered with accordance of each code step. I assume that cli tests fail due to abstract methods that consists of several cy commands and statement logics So the question is, how to write code which will run both in cypress test runner and cli,without changing method approach? Thank you in advance! Great content,+ 1 subscription

How would you determine that it was the app/website bailing out and not your machine ? Example, you run a script with a ramp-up of duration:10, arrivalRate:1, rampTo: 5 - and you get playwright error where it timed out after waiting for 30s .. Was it the app not responding for 30 seconds or it was your machine's RAM / CPU usage to the roof and couldn't load the page?

Thanks

awesome articulation and easy to understand. Thanks a lot

Thanks a lot for video. But i don't understand how do you start this test in handled mode. My test started in the handless mode. Where do you make these settings ?

Thanks

do you know the best practice for renew auth?

great video thanks. So it basically uses a different browser instances while loging in as the same user?

Hi, how can I add the envrioment switching on package.json? for example I want to add this on a variable called "smoke-test= npx playwright test --config=playwright.ts --reporter=list". im just new to playwright and this could help a ton. thanks! :)

Cool video, thanks!

Just finished the whole series. I feel like I know what I'm doing now. Thank you!

how to handle the situation when your state goes invalid

Well explained❤

great explanation ! thank you ! Definitely helped me !

Great explanation ! Thank you !

Does it work on a server side clock?

Hey man! great video, helped a lot! dispersed a lot of confusion in my mind! Than you very much!

Thanks Jared! What if I have to use this utility outside this class as a common reusable method which applies to all tests in suite. Should we go with some kind of wrapper class or fixtures? So that, when popup occurs at any point of time, code should be able to handle that.

In order to use cy.session(), provide a setup as the second argument: cy.session(id, setup) Because this error occurred during a before each hook we are skipping all of the remaining tests.

Thanks for the video! In future tutorials, a github gist would be more useful than posting the code in the video description. Also, having all the demo code would be even better 👌

I have been researching Fixtures for some time now and your video was the first that cracked and help me to understand. Well done - thanks!

hello quick question and if you want to delete the file how would you do it?

Thanks for this video. Very helpful! I wanted to know how can we destroy the LoginAuth.json file after the test run is completed? I believe we might have to use something like a globalTeardown, right? How does that work? Is there a video in this channel that demonstrates it? Are there any advantages of storing the LoginAuth.json file even the test run is complete? Where I am coming from is that it might risky to continue to store them even after the test run as they could contain some confidential information. Any advice in dealing with this is appreciated!

Hi there! English is not my first language so I'll try to do my best 🙃 Actually I have 2 questions. 1) On official Artillery site it says you have to use specific versions of Artillery and Playwright. They have something like a table, one column is for Artillery version, and the second column is for Playwright version. So, my question is if I have Artillery version 2.0.7 and Playwright version 1.47.1 (which is not listed in that table yet), will I get any issues with my tests ? 2) More practical question. I have a scenario like this: log in, do some interactions on my page, and then I click on each item of my sidebar on the left frame. Every single click on sidebar opens a new page (e.g. Products, Customers etc). So the issue I'm facing is - I don't see metrics such as FCP, TTFB, LCP etc for every single page of my sidebar. I can see metrics for my LOG IN page, the page I get to once I'm logged (where I do some interactions) in and the last page of my side bar. The solution I found is to call page.reload() after clicking on each side bar element. Only after that I cat capture metrics for each page. Is there a way to avoid reloading ? Thank you in advance

Brilliant!!! Thanks for sharing your knowledge.

Hi Sir I have a question This record and play does not help when we have dynamic applications..?? Upload files flow too

Great Videos . Well Explained . Can you add a tutorial to use Spec Flow with Playwright c# ? Thanks

Thanks buddy