Video

Thanks Rakesh.. keep learning

Welcome back

Anitha Becoming a Software Development Engineer in Test (SDET) can be a great career move especially for senior-level professionals. Let's explore what SDET entails and why it might be a good fit for you: 1. What is SDET? - SDET stands for Software Development Engineer in Test. It's a role that bridges the gap between software development and testing - SDETs are skilled in both coding and software testing, making them valuable contributors to the software development lifecycle 2. Why SDET? - Organizations seek SDETs because they can handle both automation and testing - SDETs have deep knowledge of software engineering, SDLC, and STLC processes - They're in high demand due to their ability to ensure quality while automating processes 3. When Is SDET Needed? - Consider SDET when: - The software system is robust and challenging to manage manually - Data-driven testing with complex scenarios and large datasets is required - Continuous monitoring of the entire process is essential 4. SDET vs. Other Roles: - SDET vs. QA: - QA focuses on test execution, while SDETs participate in project planning, code review, and automation - SDET vs. Developer: - SDETs have knowledge of software architecture but aren't directly involved in development - They ensure better quality standards and less defective software - SDET vs. Automation Engineer: - SDETs and automation engineers are often treated as the same - SDETs review code, write unit tests, and analyze test coverage 5. Career Path: - Junior SDET (0-3 years): - Create automation test scripts, write test cases, and learn new tools. - Senior SDET (3-7 years): - Verify acceptance criteria, analyze root causes, review code, and create/update automation scripts 6. Skills Needed: - Hands-on experience with multiple test automation tools and frameworks - Proficiency in both white-box and black-box testing - Understanding of software development principles In summary, learning SDET can enhance your career, especially if you're interested in both coding and testing. It's a valuable skill set for senior-level professionals like yourself -

Glad to hear that Gabriel.. all the best

Most welcome Eva

Ayanloye Have not created specific to BDD. can check all lectures here - automationstepbystep.com/

Glad to know .. keep learning

Prisha check online and on freelancing portals.. create your profile and also update on your social media like linkedin

You're welcome

Abhijeet It seems you're encountering two issues while running TestCafe: 1. 'powershell' Not Recognized: - The error message indicates that the 'powershell' command is not recognized. - To resolve this, you can try the following: - Add the PowerShell executable path to your system's PATH environment variable. - Alternatively, adjust your script to explicitly use the full path to PowerShell: ``` %SYSTEMROOT%System32WindowsPowerShellv1.0powershell.exe -Command "your command" ``` - Make sure PowerShell is installed and accessible. 2. Localhost Refused to Connect: - The "localhost refused to connect" error suggests that the application you're testing is not running or not accessible. - Ensure that your application server (e.g., a web server or API) is up and running. - Check the URL you're trying to connect to (e.g., `localhost:8080`) and verify that it's correct. Remember to address both issues to successfully run your TestCafe tests -

I do not recall now.. The compatibility between Selenium and ChromeDriver versions is crucial for successful automation. Here's how you can ensure compatibility: 1. Selenium 4 and Chrome Compatibility: - By default, Selenium 4 is compatible with Chrome versions 75 and greater - Ensure that the major version of your Chrome browser matches the major version of ChromeDriver you're using. 2. Finding ChromeDriver Version: - To find the ChromeDriver version: - Run `chromedriver.exe -v` directly on the node where you're executing your tests - This command will report the installed ChromeDriver version 3. Automatic Management (Selenium 4): - With the latest Selenium version, if you don't specify a location for the `chromedriver.exe` file, Selenium will manage it automatically - For example: ```python from selenium import webdriver driver = webdriver.Chrome() driver.get("www.google.com") driver.quit() ``` Remember to keep your ChromeDriver up-to-date and aligned with your Chrome browser version -

Victor To execute Gatling without using a shell script or batch file, you can follow these steps: 1. Download Gatling: - Visit the official Gatling installation page docs.gatling.io/reference/install/oss/ and download the project ZIP file for your preferred configuration (e.g., Maven-Java or Gradle-Java). - Unzip the downloaded folder to your desired location. 2. Open in IDE: - Open the unzipped Gatling folder in your preferred Integrated Development Environment (IDE) such as IntelliJ IDEA or Visual Studio Code. 3. Run Your Tests: - You can now create and run your Gatling performance tests directly from the IDE without relying on shell scripts or batch files. Remember to ensure you have the necessary prerequisites (such as Java and Scala) installed on your system -

Most welcome Dominica.. keep learning

Most welcome Pallabi.. keep learning

Most welcome Rashmi.. keep learning

Anam The "Error: EPERM: operation not permitted, rmdir" message typically occurs when Playwright encounters permission issues related to directory operations. Let's troubleshoot and find a solution: 1. Run as Administrator: - First, ensure that you're running your terminal or command prompt as an administrator. - Right-click on your terminal icon and select "Run as administrator." - Then try running your Playwright project again. 2. Check Permissions: - Verify that you have the necessary permissions to create or modify directories in the specified location. - If you're working in a system directory (e.g., `C:\\Program Files`), you might need elevated permissions. - Consider creating your project in a user-specific directory (e.g., `C:\\Users\\<YourUsername>\\my-playwright-project`) 3. Clean Cache: - Sometimes cached data can cause issues. Try cleaning the npm cache: ```bash npm cache clean --force ``` 4. Install Packages Globally: - If you're installing global packages (e.g., Playwright), use the `-g` flag: ```bash npm install -g playwright ``` 5. Check Path Length: - Long file paths can lead to permission errors. Ensure that your project path isn't too lengthy. - Consider moving your project to a shorter directory path 6. Antivirus or Security Software: - Some security software might interfere with file operations. Temporarily disable any antivirus or security tools and try again. Remember to adapt these steps based on your specific environment and project setup -

@@RaghavPal I did all the steps thoroughly, but still no luck. I've been noticing that my project runs the first time and a folder named "test-results" gets created and after the first run, that's when it complains with not having permission to access the "test-results" folder.

Daniel If you send the exact error message you are getting, I can help with specific solution. In general ..when you encounter a rejection while pushing to GitHub from Eclipse, it's usually due to a non-fast-forward update. Let's troubleshoot and find a solution: 1. Non-Fast-Forward Update: The error message "non-fast-forward updates were rejected" means that your local branch is out of sync with the upstream repository. To resolve this, follow these steps: - First, ensure that you've fetched the latest changes from the upstream repository. Use: ```bash git fetch origin ``` - Next, rebase your local branch on top of the updated upstream branch: ```bash git pull --rebase origin master ``` - Finally, attempt the push again: ```bash git push origin master ``` This sequence ensures that your local changes are applied on top of the latest commits from the remote repository. 2. Avoid Using `--force`: While you can force a push using `git push -f`, it's not recommended unless you're certain about the consequences. It can delete references on the remote repository. Stick to the non-forceful approach unless you have a specific reason to force the push -

@@RaghavPal I found my problem, I need to uncheck some setting in email, It’s fine now

Ankita Try to give single forward slashes / in your path in the command e.g. npx playwright test ./tests/first.spec.js If this does not work check other things as follows: 1. Check Test File Path: Ensure that your test files are located in the correct directory. By default, Playwright looks for test files in the `tests` folder. Make sure your test file is in the right place 2. Test File Naming Convention: Your test files should be suffixed with either `.spec.js` or `.test.js`. For example, if your file is named `first.js`, rename it to `first.spec.js` or `first.test.js`. Playwright expects this naming convention for test files 3. Run Tests with Correct Path: When running tests, specify the correct path to your test file. Use the relative path from the root of your project. For example: ```bash npx playwright test ./tests/first.spec.js ``` 4. Escape Characters: If your test file path contains special characters like spaces, make sure to escape them properly. Enclose the path in quotes if needed: ```bash npx playwright test "./tests/my test file.spec.js" ``` 5. Configuration Check: Double-check your Playwright configuration (e.g., `playwright.config.js`). Ensure that the `testDir` property points to the correct folder where your test files reside. -

Glad to hear that Helen.. keep learning

Thanks a lot

@@RaghavPal sir can we learn within 1 hour full XML language

You can get the basics and foundation.. and it's a great way to learn anything. Devote 1 hr with full focus and you will learn a lot and will also create foundation and motivation for learning more.. all the best..

Aarti Let's address the deprecated URL constructors issue in your Selenium Java code. The deprecated constructors you're encountering are related to the `java.net.URL` class. In Java 20, all public constructors of `URL` have been deprecated¹. To resolve this, you can use the `URI::toURL` alternative for constructing URLs Here's how you can update your code snippet: ```java import org.openqa.selenium.WebDriver; import org.openqa.selenium.chrome.ChromeDriver; import org.openqa.selenium.chrome.ChromeOptions; import org.openqa.selenium.remote.RemoteWebDriver; import io.github.bonigarcia.wdm.WebDriverManager; import java.net.MalformedURLException; import java.net.URI; import java.net.URL; import java.util.HashMap; import java.util.Map; public class SeleniumExample { public static void main(String[] args) throws MalformedURLException { WebDriverManager.chromedriver().setup(); ChromeOptions options = new ChromeOptions(); options.setPlatformName("Windows-10"); options.setBrowserVersion("latest"); WebDriver driver = new ChromeDriver(options); Map<String, Object> sauceOptions = new HashMap<>(); sauceOptions.put("username", System.getenv("oauth-aartiriat88-ba9ce")); sauceOptions.put("accessKey", System.getenv("8728a94a-3897-4a5d-b40f-63516cd3e932")); // Set sauce:options capability options.setCapability("sauce:options", sauceOptions); String urlString = "ondemand.us-west-1.saucelabs.com/wd/hub/"; URL url = URI.create(urlString).toURL(); // Use URI::toURL System.out.println("URL created: " + url.toString()); driver = new RemoteWebDriver(url, options); driver.get("www.google.com/"); driver.findElement(By.id("APjFqb")).sendKeys("abcd"); driver.findElement(By.cssSelector("div.FPdoLc.lJ9FBc > center > input[name=\"btnK\"]")).sendKeys(Keys.RETURN); driver.close(); } } ``` By using `URI::toURL`, you'll avoid the deprecated constructors and ensure compatibility with Java 20 -

Shanna If IntelliJ IDEA isn't displaying the Maven tool window, follow these steps: 1. Check Maven Plugin: First, ensure that the Maven plugin is enabled. Go to `File → Settings → Plugins → Maven Integration` and make sure it's active 2. Add as Maven Project: Right-click on your `pom.xml` file (usually located in the root directory of your project) and select "Add as Maven Project" from the context menu. This action associates your project with Maven and should reveal the Maven tool window 3. Restore Default Layout: If the issue persists, try resetting the IDE windows. Go to `Window → Restore Default Layout`. These steps should help you access the Maven tool window in IntelliJ IDEA -

Aarti If you're using AutoIt and encountering issues with the deprecated `Runtime.getRuntime().exec()` method, let's explore some alternatives: 1. Invoke AutoIt Script from Selenium: - In your Selenium Java code, you can invoke a compiled AutoIt script using the `Runtime.getRuntime().exec()` method - For example: ```java WebElement uploadButton = driver.findElement(By.id("uploadButton")); uploadButton.click(); // Execute the AutoIt script here ``` 2. Consider Other Approaches: - If you're looking for a replacement for `Execute()`, you might explore other methods or libraries. - One alternative is twinBASIC, which doesn't have a runtime dependency and produces lightweight executables Remember to adapt the solution based on your specific use case -

Aarti If you're using AutoIt and encountering issues with the deprecated `Runtime.getRuntime().exec()` method, let's explore some alternatives: 1. Invoke AutoIt Script from Selenium: - In your Selenium Java code, you can invoke a compiled AutoIt script using the `Runtime.getRuntime().exec()` method - For example: ```java WebElement uploadButton = driver.findElement(By.id("uploadButton")); uploadButton.click(); // Execute the AutoIt script here ``` 2. Consider Other Approaches: - If you're looking for a replacement for `Execute()`, you might explore other methods or libraries. - One alternative is twinBASIC, which doesn't have a runtime dependency and produces lightweight executables Remember to adapt the solution based on your specific use case -

@@RaghavPal : when you say to execute AutoIt script here, you mean this: WebElement uploadButton = driver.findElement(By.id("uploadButton")); uploadButton.click(); ControlFocus("Open","","Edit1") Sleep(3000) ControlSetText("Open","","Edit1","C:\Users\OPTIPLEX 3040\Desktop\Sample.txt") Sleep(3000) ControlClick("Open","","Button1"). I didnt get your point. Can you please elaborate?

Aarti I apologize for any confusion. Let me clarify how to execute the AutoIt script within your Selenium Java code When I mentioned "Execute the AutoIt script here," I meant that you should call the AutoIt script using the `Runtime.getRuntime().exec()` method after clicking the upload button in your Selenium code. Let's break it down step by step: 1. Find the Upload Button: First, locate the upload button using Selenium. You've already done this with the following line: ```java WebElement uploadButton = driver.findElement(By.id("uploadButton")); ``` 2. Click the Upload Button: Next, simulate a click on the upload button: ```java uploadButton.click(); ``` 3. Execute the AutoIt Script: After clicking the button, you'll want to execute your AutoIt script. Use the `Runtime.getRuntime().exec()` method to run the AutoIt executable. Here's an example of how you can do this: ```java try { // Replace "path/to/your/autoit.exe" with the actual path to your AutoIt executable String autoItScriptPath = "path/to/your/autoit.exe"; String command = autoItScriptPath + " \"C:\\Users\\OPTIPLEX 3040\\Desktop\\Sample.txt\""; Process process = Runtime.getRuntime().exec(command); process.waitFor(); // Wait for the AutoIt script to finish } catch (IOException | InterruptedException e) { e.printStackTrace(); } ``` In the above code: - `autoItScriptPath` should point to the location of your compiled AutoIt script (the `.exe` file). - `"C:\\Users\\OPTIPLEX 3040\\Desktop\\Sample.txt"` is the path to the file you want to upload. Adjust this path according to your specific use case. 4. Adapt to Your Use Case: Remember to customize the solution based on your specific requirements. Replace the placeholders with actual paths and filenames relevant to your application. I hope this clarifies how to integrate the AutoIt script into your Selenium code. If you have any further questions or need additional assistance, feel free to ask -

Akhila The relationship between Android API levels and Java versions isn't fixed. While certain features may be accessible with specific Java versions, there's no direct mapping (e.g., Android 35 = Java 35). Different fields, methods, and classes may be added or changed over time, but they don't always align perfectly with Java version numbers However, it's essential to consider the following points: 1. Android SDK Platform and Java SDK Compatibility: - Android API levels (e.g., API 35) define the features and capabilities available to your app. - The Java version you use affects the language features and libraries available during development. - Here are some historical associations: - N (24) - O (26): Requires JDK 8u45 or newer. - L (21) - M (23): Requires JDK 7u71. - G (9) - K (20): Requires JDK 6. - C (3) - F (8): Requires JDK 5 2. Gradle and Android Plugin Compatibility: - Ensure that your Gradle build files and Android Gradle Plugin versions are compatible with your chosen API level. - Sometimes, upgrading the Android Gradle Plugin may be necessary to handle breaking changes Remember that while there's no strict correlation, understanding the compatibility requirements helps ensure a smooth development experience -

Thanks Carlos

Joe The error message indicates that the AVD (Android Virtual Device) you're trying to run has an 'arm64' CPU architecture, but it's not supported by the QEMU2 emulator on an x86_64 host. Here are some insights and potential solutions: 1. Emulator Limitations: - ARM64 emulation on an x86_64 host is currently only possible up to API level 27 (Oreo). - If your AVD is using a higher API level (e.g., Android 33), it won't work on an x86_64 host due to the architecture mismatch 2. Possible Solutions: - Use a Hardware Device: - Consider using a physical ARM64 device (if available) for testing. Hardware devices provide more reliable results and support the latest APIs. - Install Android SDK Directly from Android Studio: - Uninstall any existing Android SDK installations (e.g., via Homebrew). - Download and install Android Studio directly from the official homepage. - Set up your AVD using Android Studio, which should handle the correct system images and configurations 3. Note on Custom Emulators: - While custom emulators might be tempting, they won't necessarily solve the issue. The QEMU2 emulator has specific limitations and reasons for not supporting certain architectures on x86_64 hosts Remember that running an AVD with ARM64 architecture on an x86_64 host can be challenging due to these limitations. If possible, consider using a physical ARM64 device or adjusting your AVD configuration accordingly -

Mahfoud It looks like you're encountering an issue with Playwright when using the "context" and "page" fixtures in the "afterAll" hook. Let's address this The error message you're seeing indicates that the "context" and "page" fixtures are not supported in the "afterAll" hook because they are created on a per-test basis. Here are a couple of ways to resolve this: 1. Use beforeEach Instead of beforeAll: Since Playwright Test has context isolation by default, each test runs in a new page and context. Therefore, you cannot directly use a page instance in the "beforeAll" hook. Instead, consider using the "beforeEach" hook to set up your page before each test. This way, your page configuration will be applied consistently for all tests 2. Reuse a Single Page Between Tests: If you want to reuse a single page between tests, you can create a context manually using `browser.newContext()`. Then, keep track of the context and use the same page instance across your tests. You can find more information about reusing pages in the Playwright documentation Here's an example of how you can use the "beforeEach" hook to set up your page: ```javascript test.describe('Output Edit', () => { test.beforeEach(async ({ page }) => { await page.goto('/test'); // Set up your page here }); test('Simulations page', async ({ page }) => { await page.click(SimResults.SimResultPage.simPage(2)); // Your test logic goes here }); }); ``` -

Glad it helped Kateryna

You're very welcome Rashmi

Ahmed When using Playwright for testing, you can explore test reports in a few ways: 1. HTML Reporter: - After your test completes, an HTML report is generated. It shows a full breakdown of your tests, including browsers used, test durations, and individual steps. - You can filter the report by browsers, passed tests, failed tests, skipped tests, and flaky tests. - Clicking on each test allows you to explore errors and view each step of the test 2. Command Line Report: - You can see a concise report directly in the terminal using the `list` reporter. It prints a line for each test being run. - To enable step rendering, you can pass the `printSteps: true` configuration option¹. - Example usage: ```bash npx playwright test --reporter=list ``` 3. Browser Window Report (Debbie Codes): - Run the following command to open a browser window with a detailed report of your tests: ```bash npx playwright show-report ``` - This report includes information about browsers used, test durations, and individual steps Remember that Playwright's built-in reporters provide different levels of detail, so choose the one that best suits your needs. If you're interested in creating a Page Object Model (POM) in combination with the recording function -

I will plan Hamza

Glad to hear that Zainul

Prem If you've set the Android SDK path in Android Studio but can't find the `sdkmanager` or `adb` commands in your terminal, here's how to resolve it: 1. Android Studio Method: - Open Android Studio. - Go to File ➡️ Settings ➡️ Appearance & Behavior ➡️ System Settings ➡️ Android SDK. - In the SDK Tools tab, make sure you have the Android SDK Command-line Tools (latest) installed. If not, install or update them. - Click Apply and restart Android Studio 2. Alternative Method (Without Android Studio): - Open a terminal. - Run the following commands: ```bash sdkmanager --update sdkmanager --install "cmdline-tools;latest" flutter doctor --android-licenses ``` - This should resolve the issue even if you're not using Android Studio directly Remember to adjust the paths and commands according to your system configuration -

Most welcome

Marcos To convert a date type and include it in a request using Postman, you can follow these steps: 1. Pre-request Script: - In the "Pre-request Script" tab of your request, write JavaScript code to get the current date and save it into a variable. For example: ```javascript const dateNow = new Date(); pm.environment.set('currentDate', dateNow.toISOString()); ``` - This will set the `currentDate` environment variable with the current date in ISO format (YYYY-MM-DD). 2. Use the Variable in Your Request: - In your request body, use the `currentDate` variable like this: ```json { "currentDate": "{{currentDate}}" } ``` - This will include the formatted date in your request payload. Remember to adjust the format or variable names as needed for your specific use case -

@@RaghavPal thaaannnkss

Sanmati In Postman, the "Tests" tab allows you to write JavaScript code to validate your API responses. If you don't see it, here's how to access it: 1. Open a request in Postman. 2. Look for the "Scripts" section. By default, it opens on the "post-response" sub-tab. 3. Click on the "post-response" sub-tab, and if you had test code there, it should be displayed. 4. Alternatively, you can select the "All Tests" tab to view all requests and their associated tests¹. Remember that the "Tests" tab is where you can write custom validation logic for your API responses -

@@RaghavPal Thank you for your reply, i got it ,i am going through your videos, those are great

Sure.. i will do Vidhya

@@RaghavPal Sir, Is there a provision to ask you questions via email.

The best way is to ask here.. you will get faster replies

Sorry to hear that..I believe in the initial parts the video explains on the setup imports etc.. believe that will be useful for beginners

thanks

Raghu To become a penetration tester (or "pentester"), having programming knowledge is essential. Here are the key skills you'll need: 1. Analytical Skills: - Pentesters analyze systems, networks, and applications for vulnerabilities. Strong analytical abilities are crucial to identify security weaknesses 2. Thinking Like an Attacker: - Pentesters must adopt the mindset of a malicious actor. Understanding how attackers think helps uncover vulnerabilities effectively 3. Scripting Languages: - Knowledge of scripting languages is vital. Python and Perl are commonly used for writing custom tools and automating tasks in penetration testing². - Proficiency in Bash, Ruby, and Java can also be beneficial 4. Web Application Technologies: - Familiarity with web technologies like HTML, JavaScript, and SQL is essential - Web applications are common targets for pentesting, so understanding their architecture and security flaws is crucial Remember that while formal education or certifications can help, practical experience and continuous learning are equally important -

I will need to check with more details.. steps, logs etc.. try with some online help Tanay

Thanks for the kind words.. Here are some steps to help you create a folder in your Users directory: 1. Check Filesystem Permissions: - Right-click on the folder where you want to create a new folder (e.g., your Users directory). - Choose "Properties." - Go to the "Security" tab. - Click "Edit" and ensure your username has "Full control" permissions. If not, add your username and grant the necessary permissions. - Confirm the changes. 2. Reset Permissions Using Command Prompt: - Open Command Prompt as an administrator (search for "cmd" and choose "Run as administrator"). - Navigate to the folder where you want to create the new folder using the `cd` command (e.g., `cd C:\Users\YourUsername`). - Run the following commands: ```bash takeown /R /F * icacls * /t /q /c /reset ``` - These commands will reset permissions for all subfolders and files in the specified directory. 3. Restart Your Computer: - Sometimes changes take effect after a restart. Give it a try! Remember to replace `YourUsername` with your actual Windows username -

Most welcome

Glad it was helpful Kumar.. I will plan to add more on this

Oloja I keep all notes in the description below the video.. pls check

Thanks and most welcome..