Glad it helped!

Yay! You're welcome.

My pleasure!

Hi, yes. What are you looking to learn?

@@automateNow Playwright using C#

@@automateNow whats the best way to connect?

@81modus Unfortunately, I'm not offering courses involving C# at the moment. You can reach me via LinkedIn or Slack. linktr.ee/automateNow

You're very welcome!

Where you doing a clean install, or you already had another version/copy of Windows?

Nice!

Great question. Based on the little research I did, liquid metal is the best way to go, but I didn't want to go through the hassle of using that. I also learned that there are some less-known/cheaper thermal paste brands that don't perform as well when compared to reputable brands. In the end, I made the choice for peace of mind.

Thanks

You're welcome. Happy to help!

Thank you, @namratabedare. Here is a detailed article which can help you export logs to a file.

Hi @gonzalojaviermolina7659, Here is a simple Java program that adds some string values by first removing the commas. Hopefully, this can give you a hit on how to solve your problem. public class StringAddition { public static void main(String[] args) { // Input strings String str1 = "1,429"; String str2 = "10"; String str3 = "0.75"; // Remove commas and convert to double double num1 = Double.parseDouble(str1.replace(",", "")); double num2 = Double.parseDouble(str2); double num3 = Double.parseDouble(str3); // Calculate the total double total = num1 + num2 + num3; // Print the result System.out.println("Total: " + total); } }

Awesome! You're very welcome, @somnathbanerjee2063.

You're welcome, @fazelamirvahedi3930.

My pleasure, @yogs3870!

You can right-click using the Actions API: // Locate the element you want to right-click on WebElement elementToRightClick = driver.findElement(By.xpath("element_locator")); // Initialize Actions class Actions actions = new Actions(driver); // Perform right-click (context click) on the element actions.contextClick(elementToRightClick).perform();

Here is an explanation of the code: TakeScreenshot screenshot = (TakeScreenshot) driver; = TakeScreenshot is an interface in Selenium that provides a method to capture a screenshot. This line of code casts the driver (which is an instance of WebDriver) to the TakeScreenshot interface. This allows you to use the getScreenshotAs method, which is not available directly through the WebDriver interface. File file = screenshot.getScreenshotAs(OutputType.FILE); = getScreenshotAs(OutputType.FILE) is a method of the TakeScreenshot interface that captures the current screenshot and stores it in a File object. OutputType.FILE specifies that the output of the screenshot should be in the form of a File. The method returns a File object that represents the screenshot captured.

Step 1: Place Fixture Files First, place your fixture files (e.g., JSON files) in the `cypress/fixtures` directory. For example, you might have a file named `data.json` with the following content: { "username": "testuser", "password": "password123" } Step 2: Load Fixtures in Your Test In your test file, you can use the `cy.fixture` command to load the fixture data. Here’s an example of how you can use the fixture data in your tests. // cypress/e2e/sample_spec.js describe('My First Test', () => { it('Loads fixture data', () => { // Load the fixture data cy.fixture('data').then((data) => { // Use the fixture data cy.visit('example.com/login'); // Assume there are input fields with id 'username' and 'password' cy.get('#username').type(data.username); cy.get('#password').type(data.password); // Submit the form cy.get('form').submit(); // Assertions can be added here }); }); }); Step 3: Import Fixtures in e2e.js (formerly index.js) In the `e2e.js` file (which replaces `index.js` in newer versions), you can configure Cypress to use your fixtures. Typically, this file is used to set global configurations and behaviors for your tests. // cypress/support/e2e.js // Import commands.js using ES2015 syntax: import './commands' // Alternatively you can use CommonJS syntax: // require('./commands') before(() => { // Load fixture data globally if needed cy.fixture('data').as('testData'); }); beforeEach(function() { // You can access the fixture data in your tests like this cy.get('@testData').then((data) => { this.data = data; }); }); Step 4: Using Global Fixture Data in Tests With the setup in `e2e.js`, you can now access the fixture data in your tests as `this.data`. // cypress/e2e/sample_spec.js describe('My First Test', function() { it('Uses global fixture data', function() { // Use the globally loaded fixture data cy.visit('example.com/login'); // Assume there are input fields with id 'username' and 'password' cy.get('#username').type(this.data.username); cy.get('#password').type(this.data.password); // Submit the form cy.get('form').submit(); // Assertions can be added here }); }); Tips: - Make sure the paths to your fixture files and other configurations are correct. - You can use different types of fixture files (e.g., JSON, CSV, etc.) as needed for your tests.

Excellent! You're very welcome.

Thanks. Happy to help! 🙂

Thanks for your feedback. Happy to help!

What Selenium version are you using?

You're welcome. Happy to help!

It sounds like a permissions issue. Are you trying to clone a public repo?

Thank you. :)

I'd recommend that if you are using Java, use try-with-resources to ensure that resources such as WebDriver instances are closed properly, even in the presence of exceptions. Example: try (WebDriver driver = new ChromeDriver()) { // your code } I'd also suggest that you add logging so that you can have a better understanding of what may be causing the unexpected behavior.

@@automateNow I am using C#, and ThreadLocal for parallel testing

It looks like there is no equivalent to Java's try-with-resources in C#. However, you may be able to use a "using" statement for resource management.

Thanks. Glad you found it helpful!

You don't need to have an "automation" folder. A repo can be cloned into any folder, including the C drive (if you're on Windows).

You're welcome! Are you referring to the fact that you must keep adding any new page object to the setup method?

@@automateNowyes what is the other solution?

When you have 100 pages this will take time because it will setup every single page before the test start

Happy to help!

That sounds like a file path issue. Double-check that you're using the correct path. You can also use some logging to print the filepath and make sure it's correct.

You're very welcome. I'm glad it worked!

Thanks for your feedback. I'll consider that.

You're most welcome!

My pleasure!

Happy to help, and welcome to the automateNow community!

Thank you. I've noted your request.

I have a question which is like this, we know how to locate elements, send data, perform actions using Locators in selenium, cypress etc, how can we develop our scripts like to use exceptional handling, conditional statements etc? @@automateNow

Thanks for the feedback!

Thanks for your feedback. Try using an explicit timeout as follows: cy.get('#myElement', { timeout: 10000 }) The timeout is in milliseconds, so use what is appropriate in your scenario.

@@automateNow my question was more around using Cy.xpath . How to specify the timeout while using Cy.xpath

You can do something similar as follows: cy.xpath('//your_xpath').should('exist', { timeout: 10000 });

Thanks for your question. It isn't easy to know without looking deeply at the framework. However, here are some general guidelines: Synchronization and Thread Safety: Ensure that shared resources accessed by multiple threads are properly synchronized to avoid race conditions. Use synchronization mechanisms like locks, semaphores, or synchronized blocks/methods to control access. Isolation of State: Make sure each test or thread operates in an isolated state. Avoid sharing state across tests or threads, as this can lead to unexpected behavior. Initialize variables within each test or thread to ensure independence. Proper Exception Handling: Enhance exception handling within your code to catch and log exceptions effectively. When an exception occurs, ensure that it is appropriately handled and does not propagate as a null pointer or undefined behavior. Logging and Debugging: Introduce extensive logging to trace the flow of execution and pinpoint where the null pointer or random issues occur. Use debugging tools to step through the code and identify problematic areas. Review Thread Safety of External Dependencies: Check if any external dependencies (e.g., libraries, frameworks) being used are thread-safe. Incompatible or non-thread-safe dependencies can cause unpredictable behavior in a multi-threaded environment. The bottom line is that you need to be able to determine where the NPEs are coming from to be able to weed out the root cause. Best wishes!