Learn Playwright Java in 5 Hours⏰ | Complete Playwright Java Tutorial

Learn Playwright Java in 5 Hours⏰ | Complete Playwright Java Tutorial | LambdaTest

Рет қаралды 22,136

LambdaTest

Күн бұрын

Пікірлер: 51

@LambdaTest 11 ай бұрын

📍𝐆𝐢𝐭𝐇𝐮𝐛 𝐋𝐢𝐧𝐤: github.com/ortoniKC/LambdaTest-Playwright-Java

@bhawanakumari7248 11 ай бұрын

Fantastic tutorial! 🚀 Clear explanations and hands-on examples make learning Playwright with Java a breeze.🌟 Excited to implement these skills in my projects!

@LambdaTest 10 ай бұрын

Glad, you liked it! Please subscribe to the channel for more such videos🙂

@marcinnalborczyk8576 4 ай бұрын

Went through the whole 5hours, thank you for your time and effort into it!

@LambdaTest 4 ай бұрын

Glad it you liked it

@andrewburnip2225 8 ай бұрын

2 hours deep and bro's sporting a new haircut. Looking fresh my guy. Excellent tutorial so far.

@LambdaTest 8 ай бұрын

Glad to hear the tutorial was helpful for you! Do subscribe the channel for more such tutorials !🙂

@_VuMinhKhang-dc9tf 9 ай бұрын

Thanks for the course ♥❤

@LambdaTest 9 ай бұрын

Glad you liked it! Do subscribe the channel for more such tutorials!🙂

@andyshort8087 4 ай бұрын

You are a great teacher mate. Keep up the good work.

@LambdaTest 4 ай бұрын

Thanks, will do!

@charanteja7947 3 ай бұрын

Hi, Getting could not calculate build plan error after creating the maven project, also maven project created is not in format which you have created, do you any solution to fix this and go forward? Thanks!!

@LambdaTest 3 ай бұрын

Hey @charanteja7947 To fix the 'could not calculate build plan' error: 1. Check your pom.xml for any missing dependencies or errors. 2. Run mvn clean install to rebuild the project. 3. Ensure your project follows Maven’s structure: src/main/java and pom.xml in the root. 4. Reimport the project in your IDE to sync Maven. If it persists, clear the .m2 folder and try again. Let me know if this helped :)

@andyshort8087 4 ай бұрын

Also, love the hair style changes as the videos progresses 🙂

@MyselfSankar 11 ай бұрын

Koushik, Have you worked in Testleaf , Chennai as mentor ? Lookslike I have seen you there..

@koushikchatterjee2584 11 ай бұрын

Yes, I was 😊

@MyselfSankar 10 ай бұрын

@@koushikchatterjee2584Good 👍 ... where you are working now?

@sudeepauyanahewage8353 9 ай бұрын

Great Tutorial. Is there any specific reason to use Java 11 instead of latest Java version?

@LambdaTest 9 ай бұрын

Hey there, It's worth noting that while there are valid reasons to use Java 11, using the latest Java version can offer performance improvements, new language features, and enhanced APIs. The choice between Java 11 and the latest version should be based on the specific needs, project requirements, and environment considerations.

@rhexis007 5 ай бұрын

This is a brilliant tutorial and helped me set up my first Playwright project. May I ask if you have any recommendation on how to read a local html file and what libraries I can use to generate a PDF from it?

@LambdaTest 5 ай бұрын

Hi Alex, To read a local HTML file, these libararies can help: - playwright: For launching the browser and interacting with the web page. - fs: For reading the local HTML file. - path: For handling file paths.

@marcinnalborczyk8576 5 ай бұрын

Hi, thanks for posting that, just starting. I was wondering if you had to answer what would be the best tool for automating frontend (web browsers) currently? Playwright, Cypress, Selenium or smth else? Would love to hear your take on it.

@LambdaTest 5 ай бұрын

@marcinnalborczyk8576 Currently, Playwright and Cypress are considered the best tools for automating frontend (web browsers) due to their modern features and ease of use. Playwright offers robust cross-browser testing capabilities, while Cypress provides an excellent developer experience with fast execution and easy debugging. Selenium remains a strong choice for its extensive community support and versatility across different browsers and platforms. Hope this answered your query :)

@marcinnalborczyk8576 5 ай бұрын

@@LambdaTest Thanks alot for quick and extensive reply. Yes it answered my question and brought more understanding. In terms of programming languages is there any difference whether I use Java or JS with Playwright or Cypress?

@LambdaTest 5 ай бұрын

@marcinnalborczyk8576 , Yes, there are differences: Playwright: 1. Java: Playwright has official support for Java, allowing full use of its features. 2. JavaScript/TypeScript: Full support, with more examples and community resources available. Cypress: 1. Java: Not supported. Cypress is primarily built for JavaScript/TypeScript. 2. JavaScript/TypeScript: Full support, with rich documentation and community support. For Playwright, you can choose either Java or JavaScript, but for Cypress, you must use JavaScript. I hope this helps. : )

@marcinnalborczyk8576 5 ай бұрын

@@LambdaTest yes it does, thanks for taking the time to answer

@MaxZhurkin 6 ай бұрын

Hello, what extention do you use to see all the selectors in the browser?

@LambdaTest 6 ай бұрын

The extension used to get all the selectors is "LetXPath", you can get it from the chrome web store.

@MaxZhurkin 6 ай бұрын

@@LambdaTest thank you!

@JagadeshwaranArumugam 3 ай бұрын

Hii.. Can you clarify my doubts regarding that page.screenshot() is an older version right why because now, I have did that same thing it was displaying only the screenshotOptions().

@LambdaTest 3 ай бұрын

Hi Jagadeshwaran, It seems like you're using an updated version of Playwright where the method page.screenshot() has been replaced or updated to screenshotOptions() for handling screenshot functionality. In Playwright, page.screenshot() is still valid in most cases, but updates to the API may have introduced screenshotOptions() as a more configurable or structured way to manage screenshot options.

@usamaismail2654 4 ай бұрын

HI, Can I know the name of the chrome plugin you are using to inspect?

@LambdaTest 4 ай бұрын

Hey @usamaismail2654 : The plugin used is LetXPath, an inspector tool that helps generate XPath expressions for web elements. Alternatively, you can use Chrome DevTools, built into Google Chrome. To access Chrome DevTools, right-click on any element on a webpage and select "Inspect," or press `Ctrl+Shift+I` (Windows/Linux) or `Cmd+Opt+I` (Mac). Hope i was able to address your query. :)

@usamaismail2654 4 ай бұрын

@@LambdaTest Thank You 😊

@Tej-ds1zc 10 ай бұрын

Can you please help me how to generate the report in playwright java?

@LambdaTest 10 ай бұрын

Thank you for reaching out! We'll review your query and get back to you soon with a response. Appreciate your patience!🙂

@erompanhale24 5 ай бұрын

Can u plz provide ppt that u have used in the video

@LambdaTest 5 ай бұрын

Thank you so much for your interest! Unfortunately, we can't share the entire PPT, but we're happy to answer any questions or provide additional information you might need.🙂

@saisowmya3320 6 ай бұрын

How to copy from inspect content to the code

@LambdaTest 6 ай бұрын

Hey @saisowmya3320 , You can follow the below steps to copy content or an web element from inspect 1. Right-click on the element in the webpage and select "Inspect". 2. In the Developer Tools, find the HTML code for the element. 3. Right-click on the code and select "Copy". 4. Paste the copied code into your code editor. 5. Make any necessary adjustments and test your code. To get guidance on how to inspect elements irrespective of Mac or Android Devices or Web browsers, you can follow this guide. The initial inspect remains the same. www.lambdatest.com/blog/how-to-inspect-elements-on-android-devices/

@saisowmya3320 6 ай бұрын

Copy as what element or outerHtml, selector, js path, styles, XPath, full XPath.

@LambdaTest 6 ай бұрын

Hi Sai Sowmya, It depends on your needs: use "Copy as HTML" for the element's code, "Copy selector" for CSS targeting, "Copy JS path" for JavaScript access, "Copy styles" for inline styles, "Copy XPath" for XPath queries, and "Copy full XPath" for XPath targeting.