@@Nachiappans-v2f To securely use a variable like SALT in your GitHub Actions workflow, you should store it as a secret in your GitHub repository. GitHub Actions provides a way to manage secrets securely, preventing them from being exposed in logs. Here’s how you can store and use the SALT value in your workflow: Step 1: Add the SALT as a Secret in GitHub 1. Go to your GitHub repository. 2. Click on the Settings tab. 3. In the left sidebar, click on Secrets and variables, then click Actions. 4. Click the New repository secret button. 5. In the Name field, enter SALT. 6. In the Value field, enter your salt value. 7. Click Add secret. Step 2: Use the SALT in GitHub Actions Workflow Once the secret is set, you can access it in your GitHub Actions workflow as an environment variable. Here’s an example of how you might use the SALT in your workflow to encrypt passwords: name: Password Encryption Workflow on: push: branches: - main jobs: encrypt-passwords: runs-on: ubuntu-latest steps: - name: Checkout code uses: actions/checkout@v3 - name: Encrypt passwords run: | echo "Encrypting password with SALT" encrypted_password=$(echo "$PASSWORD" | openssl enc -aes-256-cbc -salt -pass pass:$SALT) echo "Encrypted password: $encrypted_password" env: PASSWORD: ${{ secrets.PASSWORD }} SALT: ${{ secrets.SALT }} Key Points: • Secrets: SALT and PASSWORD are retrieved securely using ${{ secrets.SALT }} and ${{ secrets.PASSWORD }}. • Environment Variables: The secrets are passed as environment variables and accessed in the script. • Encryption: This example uses openssl to encrypt a password with the provided salt. By using GitHub secrets, the SALT value will remain secure throughout your GitHub Actions workflow, ensuring it is not exposed in logs or as plain text.

Check out the error line, remove any special characters such as brackets

@@Talaria.School sure, thanks for the suggestion

Yes

Thanks for question. You may try this Mastering API Response Validation with Pydantic: A Game Changer for QA Automation! kzbin.info/www/bejne/mIicZoqPjs6lfpY

@@ShubhendraSingh-b2t thanks

Clone or download the repo

Thanks for your question **Use Trusted IP Ranges**: By adding your network's IP range to Salesforce's trusted IP ranges, users logging in from those IPs won't be prompted for verification codes. This is done under the **Network Access** settings in Salesforce.

@@QaAutomationAlchemist Thank you, will try that one

​@@QaAutomationAlchemist I have tried by adding my IP Address , but still facing that verification code I thought that its happening due to incognito and tried with normal browser instance , but its still asking OTP

Playwright is not actually for csv compare. You can try pandas from python. WinMerge, Beyond compare apps too. Or Excel addins

Currently it is removed

@@QaAutomationAlchemist Thanks for your response

@@AatishShegal thanks for question. While returning page, logical check on fields which are required or which fields decide the type of next page. Based on if those fields has value, then return page. Even you use flags for different pages/flow.

Thanks, will try to do that

Awesome, thank you!

@QaAutomationAlchemist please let me know if you are planning to do BDD cucumber based framework for UI. Alot of content I saw on the youtube is half cooked. I love how you articulate it into live scenario.

- `mkdir`: This command stands for "make directory." - `-p`: This option stands for "parents." It instructs `mkdir` to create the parent directories as needed. If any of the directories in the path don't exist, they will be created. - `src/tests`: This is the directory path to be created. When you run `mkdir -p src/tests`, the system will create the directory `src` if it doesn't already exist, and inside `src`, it will create the `tests` directory. If both directories already exist, the command will do nothing and will not produce an error. This is useful for ensuring that a specific directory structure is present without having to manually check and create each directory level one by one.

@@QaAutomationAlchemist thank you for explaining it thoroughly

As of now No, but strongly suggest typescript to have more advantages Using TypeScript in Playwright offers type safety, reducing runtime errors through compile-time checks. It enhances IDE support with features like autocompletion and real-time type checking, boosting productivity. Additionally, TypeScript's strong typing and object-oriented features improve code maintainability and clarity.

@@QaAutomationAlchemist thank you for explaining why typescript is prefferred over javascript , that really helped to understand

It is in description

git checkout branchName git switch branchName Both are same, latter one is recent way

Need to plan and some of us overwhelmed by seeing all in single video. Idea is learn one thing and do practical then proceed. Thanks for sharing your thoughts

We could use plugins to find multiple locators as of now. Thanks for your idea.

There is a library which can be utilised to fetch properties during execution.

​@@learnshare5265could you suggest any please?

Glad it was helpful!

Custom fixtures are ideal for complex, reusable setup logic across multiple test files, ensuring isolated environments and efficient resource management. beforeEach is suitable for simpler, localized setups within a single test file. By leveraging both appropriately, you can create robust, maintainable, and efficient test suites.