Відео

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

Hey @aparnausa3619 , To avoid creating page instances in every test in a single file in JavaScript, use setup (`beforeAll` or `before`) and teardown (`afterAll` or `after`) hooks to create and close the page instance. To learn more about these hooks follow this guide : www.lambdatest.com/learning-hub/javascript-automation-testing . Hope this helps

Hey @puneetoist1987, you can try looking at the official document when dealing with parallel Mode: www.npmjs.com/package/mochawesome#parallel-mode

Great !! All the best

Thank you for your suggestion! A tutorial on handling CSV files with Playwright and TypeScript, including verifying the rows, sounds like a valuable topic. We'll consider exploring this in future videos.

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

@@LambdaTest thank you!

@prikshitverma3885 , you can watch the Jenkins video tutorial in this you have everything covered including the real-time workings of automation with CI/CD Pipeline using Jenkins. Hope this helps :)

Hello @AdlBnymn , Would be better if you have basic syntax and understanding in place.

Hi Niraj, Could you please share more details about the issues you encountered on Windows?

@@LambdaTest I had issue with setting up the Environment variables on windows. I was confused which variables to set: User variables or system variables. So, setup the same path in both user and system variables and it is working now. Thanks for your reply.

Hi Pranav, This is done basically for organizing test code into modules or components that can be reused and managed independently.

Hi Jeremy! ¿Podría especificar a qué membresía se refiere?

Glad it was helpful!

Hi Sai Sowmya, Could you please provide the specific timestamp where the code is shown?

@@LambdaTest ok Thank you

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/

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

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.

Hi Karla, Sí, puedes ejecutar pruebas de Appium en LambdaTest con Appium 2.0 también, como se muestra en el tutorial. ¡Me alegra que te haya gustado!

Glad it was helpful!

Hey @uviiifittrackstravels to get step-by-step guidance on how to install Appium you can surely refer this blog www.lambdatest.com/appium , and go the section how to install and configure Appium Hope this helped :)

Hi Anton, To calculate CPU usage in percentage using Selenium 4 with Chrome DevTools Protocol (CDP), you can leverage the Performance domain, which provides performance metrics directly from the browser.

@@LambdaTest hello ! I used your example, but there are planty of another metrics ) I need CPU usage (the same metric as you can see in Performance monitor) in %. Is it possible at all ? I suppose that % can be calculated only. But I don't know how ))

Hi Anton, If you're interested in tracking the CPU usage of the browser process itself, you might get some indirect metrics via browser performance tools, but these won't directly give you CPU usage in the traditional sense (like that shown in Windows Task Manager or other system monitors).

@@LambdaTest yes but chrome can calculate this in % anyhow, I just want to get this value =)))

Hi Anton, To directly calculate CPU usage as displayed in the Performance Monitor (typically as a percentage), you generally need to access system-level APIs or utilities that provide this information. Selenium itself doesn't have built-in capabilities for monitoring CPU usage because it's focused on browser automation rather than system monitoring.

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

Hey @gauravgulati5490 , Glad you enjoyed the video. For understanding the concept of getting XPath, you can check out this video: ua-cam.com/users/liveXx9gCdnxHeo As, we don't have any specific video by Koushik on this. You can also go through this blogs: www.lambdatest.com/blog/complete-guide-for-using-xpath-in-selenium-with-examples/

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

Hi Luiz, Could you let us know the challenge you're facing?

Glad you liked it! Do subscribe the channel for more such videos.😀

Hi, Didn't get the context. Could you please elaborate more on this?

Given the similar naming of your tests, it's possible the pattern is matching more than one test. Here’s how you can more specifically target the test "two one" in Playwright, especially when using macOS: Use the Exact Match Flag in Playwright: Playwright's test runner allows you to specify an exact name match or a pattern. Since your tests have similar names, you should use a regex pattern that matches the exact test name to avoid ambiguity. To run just the "two one" test and not any test that contains "two one", you can modify the command like this: npx playwright test --grep '^two one$' ty.spec.ts Here, ^ denotes the start of the string, and $ denotes the end of the string, ensuring that only the test exactly matching "two one" is selected. Ensure You're in the Correct Directory: Before running the command, make sure you're in the directory that contains your ty.spec.ts file, or provide the correct path to the file. Check for Typos and Syntax: Errors can also come from typos in your command or in the test name within your file. Verify that everything is spelled correctly and that you're using the right syntax for your test runner configuration. Review Error Messages: The error message you receive can give clues about what's going wrong. If it’s a syntax error or a configuration issue, adjusting your Playwright setup or command line syntax might be necessa

Thank you so much for your kind words! We're thrilled to hear that the video was helpful and clarified the importance of Jenkins for DevOps teams. It’s always great to know that the content is making a difference and helping others in their journey. If you have any more questions or need further insights on Jenkins or DevOps practices, feel free to reach out or suggest more topics you’d like to see covered in future videos. Your support and feedback are truly appreciated! ❤️

Could you please provide more details about the issue you're facing with the XPath, please reach us out support@lambdatest.com

Your current setup with a testConfig.ts for environment configurations and a LoginPage class for handling the login functionality is on the right track. Here's how you can modify your approach to handle multiple logins with different credentials running in parallel: 1. Create a New Configuration File for Credentials: Instead of modifying testConfig.ts, consider creating a separate configuration file that holds an array of credentials. This helps in managing multiple users more efficiently. 2. Modify Your LoginPage to Accept Credentials: Change your login methods to accept credentials as parameters rather than pulling from a config. This will allow you to use the same login page logic for multiple users. 3. Use Playwright's Promise.all for Parallel Execution: Utilize JavaScript's Promise.all to run login actions in parallel. This function can be used to handle multiple promises (logins in this case) simultaneously. Here’s an example approach to structuring your code: Create a Separate Credentials File: Define an array of user credentials in credentialsConfig.ts. // credentialsConfig.ts export const users = [ { emailId: "user1@example.com", password: "password1" }, { emailId: "user2@example.com", password: "password2" }, ]; Modify LoginPage Class: Update the LoginPage class to accept credentials dynamically for the login function. // LoginPage.ts import { Page, Locator } from '@playwright/test'; export class LoginPage { readonly page: Page; readonly emailId: Locator; readonly password: Locator; readonly loginButton: Locator; constructor(page: Page) { this.page = page; this.emailId = page.locator('[id="UserName"]'); this.password = page.locator('[id="Password"]'); this.loginButton = page.locator('[id="LoginButton"]'); } async loginToApplication(email: string, password: string): Promise<void> { await this.emailId.fill(email); await this.password.fill(password); await this.loginButton.click(); } } Implement Parallel Logins: Use Promise.all in your test file to run multiple logins at the same time. // login.test.ts import { test } from '@playwright/test'; import { LoginPage } from './LoginPage'; import { users } from './credentialsConfig'; test('multiple logins', async ({ browser }) => { const page = await browser.newPage(); const loginPage = new LoginPage(page); const loginPromises = users.map(user => loginPage.loginToApplication(user.emailId, user.password) ); await Promise.all(loginPromises); // Executes all logins in parallel });

Thank you Kaushik for your reply. It helped me a lot.

​ @LambdaTest Thanks a ton for helping me in my scripting journey. I have added the code in my script as you have suggested above, And when I have executed that script it is passing all the given email address in EmailId field onetime only like: ********Email : test1@test.com test2@test.com test3@test.com test4@test.com test5@test.com*************** It didn't enter the email address one by one to the field and complete the process I suspect something wrong happened in loginTesting.test.ts file code(which is as shown below only gave the name Loadtesting to the page) import test from '@lib/BaseTest'; import { LoadTestingPage } from 'pageRepo/LoadTestingPage'; import { users } from 'credentialsConfig'; test(`Test multiple Logins to ICC through playwright`, async ({ loadTestingPage, browser }) => { await test.step(`Navigate to URL`, async () => { await loadTestingPage.navigateToURL(); }); await test.step('Login to the applicaiton', async() =>{ const loginPromises = users.map (user => loadTestingPage.loginToApplication1(user.emailId, user.Password) ); await Promise.all(loginPromises); }); }); ------------------------------------ And below is my LoadTestingPage.ts file import { Page, BrowserContext, Locator, expect } from '@playwright/test'; import { testConfig } from 'testConfig'; export class LoadTestingPage { readonly page: Page; readonly context: BrowserContext; readonly emailId: Locator; readonly password: Locator; readonly loginButton: Locator; constructor(page: Page, context: BrowserContext) { this.page = page; this.context = context; this.emailId = page.locator('[id="UserName"]'); this.password = page.locator('[id="MainText_authentication_LoginUser_Password"]'); this.loginButton = page.locator('[id="MainText_authentication_LoginUser_LoginButton"]'); } async navigateToURL(): Promise<void> { //const baseURL = testConfig.baseURL; await this.page.goto(testConfig.baseURL);} async loginToApplication1(email: string, password: string): Promise<void> { await this.emailId.fill(email); await this.password.fill(password); await this.loginButton.click(); } } I tried to explore 'Promise.all' on internet but couldn't find the way to correct my error. Can you please help me to understand what I'm doing wrong here ? and how can I edit my script to pass credentials one by one in fields. Thanks again :)

Hi Shweta, The issue with your code seems to be related to how the email addresses are being entered into the emailId field. When you use Promise.all, all the promises are executed concurrently. If the browser context or the page is shared, this could lead to unexpected behavior where multiple email addresses are entered into the field at the same time or in a mixed-up manner.

Thank you for sharing your feedback! We understand your concern about identifying the exact test that failed when using commands in your test scripts. To pinpoint test failures more easily, consider using descriptive comments or names in your test scripts. This helps you quickly identify the problematic test. You can also use some testing tools that offer features like stack traces or highlighting failing commands for a better error-reporting system and debugging process.

Thank you for taking the time to share your feedback. We're sorry to hear that you found the material unengaging. We always strive to improve and provide content that is both informative and engaging. Your feedback is valuable, and we will take it into consideration for future content. If you have any specific suggestions on how we can make the material more engaging, we would love to hear them. Thank you again for your feedback!

Hey, As of now, we don't offer support for creating new test cases. Our features are geared towards executing and managing test automation, which requires an account.

Hey Daniel, We recommend you check the configuration of your test runner or test framework to ensure it's set up correctly to handle test execution and reporting. There might be configuration options related to test statuses and handling of asynchronous operations.

Hey Daniel, Sometimes, network connectivity issues can cause tests to be cancelled. Check your network connection to ensure it's stable and that there are no firewalls or other network restrictions interfering with the test execution.

Hi there, We're glad to hear from you, and it's wonderful that you're finding the videos helpful! Running a test case with multiple different logins simultaneously in Playwright with TypeScript can indeed simulate a form of load testing and is great for testing how your application handles concurrent sessions. Here’s a basic outline of how you can achieve this: Use Test Parameterization: Playwright Test allows you to run parameterized tests. You can define multiple test scenarios with different login credentials. Here’s a simple example: // Define multiple credentials const credentials = [ { username: 'user1', password: 'pass1' }, { username: 'user2', password: 'pass2' }, // Add more credentials as needed ]; // Parameterized test credentials.forEach(cred => { test(`Login test for ${cred.username}`, async ({ page }) => { await page.goto('your-app.com/login'); await page.fill('input#username', cred.username); await page.fill('input#password', cred.password); await page.click('text=Login'); // Add assertions and further actions here }); });

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

Glad to hear that

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

Glad the video was helpful! Please subscribe the channel for more such videos🙂

Glad the video was helpful! Please subscribe the channel for more such videos🙂

Thank You 🙂