Automation Step by Step
Automation Step by Step
  • 1 186
  • 72 463 776
Terraform complete course | Step by Step for Beginners
Timestamps ▬▬▬
00:00 Introduction
03:14 What is IaC
07:56 What is Terraform
11:31 Install Terraform
12:01 How to install Terraform on Windows
20:49 How to install Terraform on Mac OS
39:21 How to install Terraform on Linux
43:25 Create Terraform project
52:16 Create Configuration file e.g. main.tf
52:49 Decide a provider & mention in config file
1:06:41 Run commands terraform init terraform validate
1:13:02 Add infrastructure details in config file, Run terraform fmt
1:22:44 Run terraform init
1:23:34 Run terraform plan
1:28:26 Run terraform apply
1:33:41 Verify terraform show
1:35:50 terraform.tfstate file
1:37:17 Delete terraform destroy
1:41:01 Summary for Terraform basics
1:41:41 Intro to next steps
1:43:04 Terraform Variables variables.tf terraform.tfvars
1:56:39 Terraform Output outputs.tf
2:03:02 Terraform Modules
2:19:26 Manage Environments using folders
2:22:11 Manage Environments using Workspaces
2:35:55 Terraform Project Structure
2:38:31 Summary
Notes - docs.google.com/document/d/e/2PACX-1vRw6zcMfrLtyZAeGqmPofQUM2XmsHS2w0BG84WDO5fCZD_AU9C77V-GkYAHMJ2o-Hr3qkm2DKkpfABN/pub
Quiz - forms.gle/qE5HSSckE4WcyuGP9
Terraform Demo Project 1 - github.com/Raghav-Pal/TerraformDemo1
Terraform Demo Project 2 (workspaces) - github.com/Raghav-Pal/Terraform-workspace-demo
All Free Tutorials 🟢 AutomationStepByStep.com/
▬▬▬▬▬▬▬
Share with all who may need this
If my work has helped you, consider helping any animal near you, in any way you can
Never Stop Learning
Raghav
▬▬▬
zhlédnutí: 7 896

Video

8 | Appium Step by Step | Complete iOS Testing setup
zhlédnutí 2,5KPřed měsícem
00:00 Introduction 01:38 Topics 04:17 Check Requirements 06:11 Install Xcode & Xcode command-line tools 12:30 Check iOS simulators 16:32 Install Appium & appium doctor 24:18 Check what is missing on your system appium-doctor ios 26:08 Install Appium ios Driver (XCUITEST) 32:31 Get the app file (.app or .ipa) or bundleId 39:34 Run a session with Appium Inspector 42:16 Get Desired Capabilities Ad...
7 | Appium Step by Step | Complete Hands On DEMO and Recording with Appium Inspector
zhlédnutí 2,6KPřed měsícem
00:00 Introduction 01:27 Start Appium 03:17 Start Appium Inspector 04:52 Add appium session details in Session Builder 07:04 Get desired capabilities for real mobile device 18:54 Get desired capabilities for virtual device (Emulator) 23:31 Add desired capabilities and start session of Appium Inspector 24:28 Appium Inspector home screen - Session Inspector 29:10 Screenshot Panel 34:10 Source Tab...
6 | Appium Step by Step | How to setup and use Appium Inspector
zhlédnutí 3,9KPřed měsícem
Setup and Start Appium Inspector 00:00 Intro 00:47 What we will learn 02:05 Download and install Appium Inspector github.com/appium/appium-inspector OR Use web version: inspector.appiumpro.com/ 08:45 : Start Appium Inspector As we have not yet started appium server you will get error message 09:14 Start appium server by running command appium If you are using the web version of Appium Inspector...
5 | Appium Step by Step | Android Real Device Setup for Automation
zhlédnutí 2,4KPřed měsícem
00:00 Intro 00:54 Step 1 : Open mobile device 01:20 Step 2 : Goto settings > About phone Tap on Build No or Software version 7 time to become a developer 03:30 Settings > Developer Options > Enable USB Debugging 04:38 Step 3 : Attach phone to the system (laptop/desktop) with cable 05:03 Step 4 : If you get prompt to enable USB Debugging, allow it 05:12 Step 5 : Run command adb devices 07:40 Get...
4 | Appium Step by Step | How to create Android Virtual Device
zhlédnutí 2,8KPřed měsícem
Android Virtual Device (AVD) Setup for Automation 00:00 Intro 00:56 How to create and start AVD (emulator) with Android Studio GUI App 02:17 On Android Studio goto Virtual Device Manager > Create new virtual device 03:18 Select device configuration and hardware (name, RAM, storage etc.) 13:31 Check the emulator is available in Device Manager (Device manager will show all connected devices, virt...
3 | Appium Step by Step | Complete Setup for Android Mobile Testing using Android Studio
zhlédnutí 3,2KPřed měsícem
00:00 Intro 00:29 What we covered in the last session 02:39 Download and setup Android Studio on windows and mac os developer.android.com/studio 10:23 Download and setup SDK Tools using Android Studio SDK Manager SDK Platforms: Select the desired Android API levels you want to target for your tests. You can choose multiple versions SDK Tools: Choose the platform-tools, build-tools, emulators et...
2 | Appium Step by Step | Complete Setup for Android Mobile Testing without using Android Studio
zhlédnutí 4,9KPřed 2 měsíci
Topics: 00:00 Intro 01:12 What we will learn 03:23 Check missing dependencies on the system 08:59 Setup Java JDK 13:21 Windows - Set Java env variables 17:18 Mac OS - Set Java env variables 24:58 Install Appium android drivers 30:04 Setting up Android SDK Tools 30:48 Option 1 : Download and setup only the required tools without using Android Studio 32:49 Windows - Download cmdline-tools and set...
1 | Appium Step by Step | Basic Setup on Windows and Mac OS
zhlédnutí 9KPřed 2 měsíci
All Free Tutorials 🟢 AutomationStepByStep.com/ All Parts - czcams.com/play/PLhW3qG5bs-L8BQaqLpjt5792e8om6IR3k.html APPIUM 2 Changes From appium 2.x onwards, the communication will happen over w3c protocol Appium drivers are maintained separately, so need to install on a need basis Introduced appium plugins, so different communities or individuals can create code blocks to add/alter certain appi...
Create unlimited free apis for testing or mocking
zhlédnutí 2,2KPřed 2 měsíci
Use this tool to create unlimited number of APIs with your own data This can be used for mocking, testing or development purposes It is free faux-api.com/ All Free Tutorials 🟢 AutomationStepByStep.com/ Create free apis for testing api mocking free and open-source create unlimited apis for testing create and host your own apis create your own api server ▬▬▬▬▬▬▬ Share with all who may need this I...
Testim Beginner Tutorial 3 | Top Features of Testim with DEMO
zhlédnutí 2,7KPřed 3 měsíci
Testim - shorturl.at/kT245 What will we learn today: GUI tour Features of Testim platform with DEMO - Insights: view the project’s dashboard and reports - Editor: create new tests and edit existing tests in the visual editor - Test List: see all the tests, suites, labels, and shared steps - Runs: view results of recent runs, see scheduled runs and run configurations - Auto-grouping: can combine...
Gatling Maven Project Setup Demo | Command Line Runs
zhlédnutí 1,3KPřed 3 měsíci
All Free Tutorials 🟢 AutomationStepByStep.com/ How to setup maven project (java & scala) How to run maven commands How to run specific test simulation How to run multiple test simulation Gatling Maven Project Setup Step 1 - Check Prerequisites java -version mvn -version Step 2 - On IntelliJ IDE Go to File > New > Project from Version Control Paste the repository URL Java - github.com/gatling/ga...
Gatling Step by Step Masterclass | Part 5
zhlédnutí 822Před 3 měsíci
00:00 Intro 00:56 What is Correlation (Chaining) 02:38 Demo of Correlation in Gatling 10:52 How to use Correlation in Gatling Scripts 14:32 How to use Regular Expression 28:20 How to run maven commands 32:30 How to run specific test simulation 34:39 How to run multiple test simulation 37:04 Assertions 40:58 Assertions scope 47:37 Gatling with VCS and CI Tools 49:28 Gatling Enterprise 01:11:11 B...
Gatling Step by Step Masterclass | Part 4
zhlédnutí 885Před 3 měsíci
00:00 Intro 00:40 Add new class for API Testing 05:45 3 basic parts of Gatling simulation script 07:51 GET API scenario setup 19:59 POST API scenario setup 29:24 Refer POST API body from a file 35:18 PUT API scenario setup 38:41 DELETE API scenario setup 41:20 Feeders (Parameterization) 41:51 Feeders demo 48:15 Feeders strategy 58:18 Running actual request with Feeders 01:07:04 Summary and next...
Gatling Step by Step Masterclass | Part 3
zhlédnutí 845Před 3 měsíci
All Free Tutorials 🟢 AutomationStepByStep.com/ 00:00 Intro 01:24 Simulation Script 02:48 Parts of Simulation Script 10:18 How to create isolated resuable modules 16:55 Divide scenario into smaller modules 23:37 Define scenario using reusable modules 32:56 Virtual users setup 42:34 Next steps What is Simulation in Gatling Simulation is the description of the load test written in script Can be wr...
Gatling Step by Step Masterclass | Part 2
zhlédnutí 1,2KPřed 4 měsíci
Gatling Step by Step Masterclass | Part 2
Gatling Step by Step Masterclass | Part 1
zhlédnutí 2,7KPřed 4 měsíci
Gatling Step by Step Masterclass | Part 1
Gatling Beginners Tutorial | Correlation | Dynamic Referencing
zhlédnutí 1KPřed 4 měsíci
Gatling Beginners Tutorial | Correlation | Dynamic Referencing
What are environment variables How do they work
zhlédnutí 3KPřed 4 měsíci
What are environment variables How do they work
HOW TO SWITCH JAVA VERSION and SET JAVA_HOME PATH ON MAC OS M1 M2
zhlédnutí 11KPřed 5 měsíci
HOW TO SWITCH JAVA VERSION and SET JAVA_HOME PATH ON MAC OS M1 M2
#AskRaghav | Selenium Roadmap for Beginners
zhlédnutí 7KPřed 6 měsíci
#AskRaghav | Selenium Roadmap for Beginners
#AskRaghav | 4 Scenario based Mobile Testing Interview Ques
zhlédnutí 2,6KPřed 6 měsíci
#AskRaghav | 4 Scenario based Mobile Testing Interview Ques
TestCafe | 4 | VS Code Extensions
zhlédnutí 1,7KPřed 7 měsíci
TestCafe | 4 | VS Code Extensions
#AskRaghav | 4 Scenario based Selenium Interview Ques
zhlédnutí 2,8KPřed 7 měsíci
#AskRaghav | 4 Scenario based Selenium Interview Ques
#AskRaghav | 4 Scenario based interview Ques | Performance Testing
zhlédnutí 2,1KPřed 7 měsíci
#AskRaghav | 4 Scenario based interview Ques | Performance Testing
#AskRaghav | 4 Scenario based interview Ques
zhlédnutí 1,7KPřed 7 měsíci
#AskRaghav | 4 Scenario based interview Ques
#AskRaghav | Template for ROI Calculation for Automation Testing
zhlédnutí 2,1KPřed 7 měsíci
#AskRaghav | Template for ROI Calculation for Automation Testing
TestCafe | 3 | Actions - Part 2 | Step-by-Step for Beginners
zhlédnutí 2,4KPřed 8 měsíci
TestCafe | 3 | Actions - Part 2 | Step-by-Step for Beginners
TestCafe | 2 | Actions - Part 1 | Step-by-Step for Beginners
zhlédnutí 2,6KPřed 8 měsíci
TestCafe | 2 | Actions - Part 1 | Step-by-Step for Beginners
TestCafe | 1 | Getting Started | Step-by-Step for Beginners
zhlédnutí 7KPřed 8 měsíci
TestCafe | 1 | Getting Started | Step-by-Step for Beginners

Komentáře

  • @najwasakina5733
    @najwasakina5733 Před 14 hodinami

    great tutorial easy to understand and thank you so much bro!!

  • @emmanuelwhite7272
    @emmanuelwhite7272 Před 15 hodinami

    wow! thanks man

  • @padminikalburagi1783
    @padminikalburagi1783 Před 15 hodinami

    Thank you.

  • @rakeshr2678
    @rakeshr2678 Před 16 hodinami

    Again U rocks

    • @RaghavPal
      @RaghavPal Před 16 hodinami

      Thanks Rakesh.. keep learning

  • @xXMrThomasXx
    @xXMrThomasXx Před 16 hodinami

    Quiz 10/10 nice :) Better than Quiz1 :) This is nice check my knowledge :) And I am back to the video but for now thx for your time and your hard work :)

  • @anithachimbili6073
    @anithachimbili6073 Před 20 hodinami

    Hi Sir, I am currently in testing with webdriverio and typescript and cucumber framework, now I am interested in learning SDET as a pack , what do you suggest? Is it good to learn for senior levels ?

    • @RaghavPal
      @RaghavPal Před 16 hodinami

      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 -

  • @GabrielSoares-mt5il

    Thanks for helping me in my career as a graduating Computer Science student. Your playlist will well be a lot to comprehend all about XML.

    • @RaghavPal
      @RaghavPal Před 16 hodinami

      Glad to hear that Gabriel.. all the best

  • @Eva-kt3tu
    @Eva-kt3tu Před dnem

    thank you so much for saving my time of reading very loooong slides of the university course

  • @AyanloyeSegun-cn8kk

    Hi RaghavPal, i love yout videos, i can't find BDD for cypress. please can you help with that

    • @RaghavPal
      @RaghavPal Před 16 hodinami

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

  • @mayureshwar
    @mayureshwar Před dnem

    Very helpful video Sir

    • @RaghavPal
      @RaghavPal Před 16 hodinami

      Glad to know .. keep learning

  • @engineer_poonam6055

    I need freelancing project

    • @RaghavPal
      @RaghavPal Před 16 hodinami

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

  • @xXMrThomasXx
    @xXMrThomasXx Před dnem

    Great tutorial. Thx for that :)

  • @user-lc9nv8es8d
    @user-lc9nv8es8d Před dnem

    hello sir Geeting below error while run the testcafe Error: Command failed with exit code 1: powershell (Get-CimInstance -ClassName Win32_OperatingSystem).caption 'powershell' is not recognized as an internal or external command, operable program or batch file. at makeError (C:\Users\abhij\OneDrive\Documents\Abhi\testcafe\test ode_modules\windows-release ode_modules\execa\lib\error.js:60:11) at Function.module.exports.sync (C:\Users\abhij\OneDrive\Documents\Abhi\testcafe\test ode_modules\windows-release ode_modules\execa\index.js:194:17) at windowsRelease (file:///C:/Users/abhij/OneDrive/Documents/Abhi/testcafe/test/node_modules/windows-release/index.js:42:19) at C:\Users\abhij\OneDrive\Documents\Abhi\testcafe\test ode_modules\get-os-info\lib\utils\get-windows-info.js:15:28 at Generator.next (<anonymous>) at fulfilled (C:\Users\abhij\OneDrive\Documents\Abhi\testcafe\test ode_modules\get-os-info\lib\utils\get-windows-info.js:5:58) also it shows localhost refused to connect.

    • @RaghavPal
      @RaghavPal Před dnem

      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 -

  • @swapnilpisal15
    @swapnilpisal15 Před dnem

    Chrome driver version???

    • @RaghavPal
      @RaghavPal Před dnem

      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 -

  • @victorfiamon
    @victorfiamon Před dnem

    The /bin folder in not appearing on new bundle version 3.11.4. How can I execute without a sh/bat script? Thanks

    • @RaghavPal
      @RaghavPal Před dnem

      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 -

  • @dominicaleung7329
    @dominicaleung7329 Před 2 dny

    Thank you very much. Your video is very helpful and your speaking pace is good also.

    • @RaghavPal
      @RaghavPal Před dnem

      Most welcome Dominica.. keep learning

  • @pallabisaha5310
    @pallabisaha5310 Před 2 dny

    Thank you so much Raghav. I like your way of teaching.

    • @RaghavPal
      @RaghavPal Před dnem

      Most welcome Pallabi.. keep learning

  • @rash1977
    @rash1977 Před 2 dny

    Thanks again Raghav! These tutorials with step by step hands on training are awesome!!

    • @RaghavPal
      @RaghavPal Před dnem

      Most welcome Rashmi.. keep learning

  • @AnamPhilisani
    @AnamPhilisani Před 2 dny

    Hi Raghav, I am getting this error whenever I try to run the project. "Error: EPERM: operation not permitted, rmdir"

    • @RaghavPal
      @RaghavPal Před dnem

      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 -

    • @AnamPhilisani
      @AnamPhilisani Před dnem

      @@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.

  • @danieltambunan9717
    @danieltambunan9717 Před 2 dny

    my commit and push get rejected, why is that?

    • @RaghavPal
      @RaghavPal Před dnem

      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 -

    • @danieltambunan9717
      @danieltambunan9717 Před dnem

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

  • @ankitanag6753
    @ankitanag6753 Před 2 dny

    Getting this error Error: No tests found. Make sure that arguments are regular expressions matching test files. You may need to escape symbols like "$" or "*" and quote the arguments. I tried in new terminal as well, Please help.

    • @RaghavPal
      @RaghavPal Před dnem

      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. -

  • @HelenMunny
    @HelenMunny Před 2 dny

    I tried several intructors in CZcams for QA. But you and Pavan are the only two for me... Thanks a ton for your support.

    • @RaghavPal
      @RaghavPal Před dnem

      Glad to hear that Helen.. keep learning

  • @e.a.k.r5048
    @e.a.k.r5048 Před 2 dny

    Too good explanation

    • @RaghavPal
      @RaghavPal Před 2 dny

      Thanks a lot

    • @e.a.k.r5048
      @e.a.k.r5048 Před 2 dny

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

    • @RaghavPal
      @RaghavPal Před dnem

      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..

  • @aartiriat7590
    @aartiriat7590 Před 2 dny

    Hi @raghav: I am not able to resolve the URL deprecated issue, Can you please help? This is my code: 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")); //sauceOptions.put("name", testInfo.getDisplayName()); options.setCapability("sauce:options", sauceOptions); String urlString = "ondemand.us-west-1.saucelabs.com/wd/hub/"; URL url = new URI.create(urlString).toString(); 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();

    • @RaghavPal
      @RaghavPal Před 2 dny

      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 -

  • @ShannaWeimann
    @ShannaWeimann Před 2 dny

    My IntelliJ IDEA doesn't show the new projects option Maven and I have installed Maven in my software but doesn't show it yet. I just can select Maven arquetype. Can you help me please?

    • @RaghavPal
      @RaghavPal Před 2 dny

      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 -

  • @aartiriat7590
    @aartiriat7590 Před 2 dny

    Hi @raghav, I am trying to run using Runtime.exec method but it says the method is deprecated. Can you please suggest a workaround? Thanks in advance.

    • @RaghavPal
      @RaghavPal Před 2 dny

      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
      @RaghavPal Před 2 dny

      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 -

    • @aartiriat7590
      @aartiriat7590 Před 2 dny

      @@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?

    • @RaghavPal
      @RaghavPal Před dnem

      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 -

  • @akhilagopinath5210
    @akhilagopinath5210 Před 3 dny

    Hi, I have a doubt, For android emulator I choose Android API 35, is that depends on java version

    • @RaghavPal
      @RaghavPal Před 2 dny

      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 -

  • @CarlosNSantos
    @CarlosNSantos Před 3 dny

    great video :-)

  • @JSeydl1788
    @JSeydl1788 Před 3 dny

    Hi, I'm having an issue in my command prompt hoping you can help me. I attached the message. I am particularly concerned about the PANIC message. C:\android\cmdline-tools\lastest\bin>emulator -avd myAVD_2 INFO | Storing crashdata in: C:\Users\12017\AppData\Local\Temp\\AndroidEmulator\emu-crash-34.2.15.db, detection is enabled for process: 29596 INFO | Android emulator version 34.2.15.0 (build_id 11906825) (CL:N/A) INFO | Found systemPath C:\SDKTools\system-images\android-VanillaIceCream\google_apis_ps16k\arm64-v8a\ PANIC: Avd's CPU Architecture 'arm64' is not supported by the QEMU2 emulator on x86_64 host. Thanks in advance for your help, and for your videos. They are great!

    • @RaghavPal
      @RaghavPal Před 2 dny

      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 -

  • @mahfoudhani1252
    @mahfoudhani1252 Před 3 dny

    Hello raghav, I work with the same method lik you but I get this error : Error: "context" and "page" fixtures are not supported in "afterAll" since they are created on a per-test basis. If you would like to reuse a single page between tests, create context manually with browser.newContext(). See aka.ms/playwright/reuse-page for details. If you would like to configure your page before each test, do that in beforeEach hook instead. Can help mes please for resolve it , I'm blocqued . Think you for this vidéo.

    • @RaghavPal
      @RaghavPal Před 2 dny

      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 }); }); ``` -

  • @user-nl6mi9dp4l
    @user-nl6mi9dp4l Před 3 dny

    Thanks for the super clear video. Now I start to believe I can nail it and start to automate

  • @rash1977
    @rash1977 Před 3 dny

    Very helpful video and it really helped me move forward by doing a Maven project and adding dependencies than a Java project initially. I like the step by step explanations. Thank you so much Raghav!

  • @user-xv9kj3my5r
    @user-xv9kj3my5r Před 3 dny

    Hi Raghav, i cant see the details from code in the test report. This cannot be opened any further. I only see the main fields with the text and steps. Is there another way to show us how to make a POM and especially in combination with the recording function?

    • @RaghavPal
      @RaghavPal Před 2 dny

      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 -

  • @hamzaakbar7984
    @hamzaakbar7984 Před 3 dny

    Great Series 👌 Can you Please make a series for Appium with Python?

  • @zainulkhan8381
    @zainulkhan8381 Před 3 dny

    Very clearly explained sir !!!

  • @premps6272
    @premps6272 Před 3 dny

    I have set the path for android from studio, however, when I'm trying to connect a real device abd and sdk manager were unfindable in terminal. this is the path which was set in zsh from studio"/Users/premtheetla/Library/Android/sdk". can u pls help me on this.

    • @RaghavPal
      @RaghavPal Před 2 dny

      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 -

  • @Kalapud1
    @Kalapud1 Před 3 dny

    Thank u

  • @marcosmarcal7200
    @marcosmarcal7200 Před 3 dny

    Hi, how can i convert a date type to send a request in flow?

    • @RaghavPal
      @RaghavPal Před 2 dny

      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 -

    • @marcosmarcal7200
      @marcosmarcal7200 Před 2 dny

      @@RaghavPal thaaannnkss

  • @SanmatiMangaonkar
    @SanmatiMangaonkar Před 3 dny

    test tab is not enabled for me? can you tell how to get the test tab

    • @RaghavPal
      @RaghavPal Před 2 dny

      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 -

    • @SanmatiMangaonkar
      @SanmatiMangaonkar Před 2 dny

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

  • @vidhyat.p2694
    @vidhyat.p2694 Před 3 dny

    Hi Sir, Hope you are doing good. Could you make a video on Puppet tooling please

    • @RaghavPal
      @RaghavPal Před 2 dny

      Sure.. i will do Vidhya

    • @vidhyat.p2694
      @vidhyat.p2694 Před 2 dny

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

    • @RaghavPal
      @RaghavPal Před dnem

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

  • @UwU-pl5jt
    @UwU-pl5jt Před 3 dny

    14 minutes into the video and you still dont talk about how to write a test, you are just talking basic node.js

    • @RaghavPal
      @RaghavPal Před 2 dny

      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

  • @Dexchur
    @Dexchur Před 3 dny

    6:22 sidha 😂😂😂😂😂 good explanation ❤

  • @Raghuahs
    @Raghuahs Před 3 dny

    Do we need programming knowledge to be PEN tester ?

    • @RaghavPal
      @RaghavPal Před 2 dny

      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 -

  • @tanayvijay4556
    @tanayvijay4556 Před 3 dny

    My cmd is not showing anything after all these processes

    • @RaghavPal
      @RaghavPal Před 2 dny

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

  • @ChatGPTtest-tp3vi
    @ChatGPTtest-tp3vi Před 3 dny

    This is an amazing tutorial for docker, the only problem I am facing here is to create a folder in my Users directory in my windows 11 system. as it says permission denied. Can you please guide me with this? How can I solve the permission issue in windows? Thank you so much Binita

    • @RaghavPal
      @RaghavPal Před 2 dny

      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 -

  • @SunShinepkg
    @SunShinepkg Před 3 dny

    Thank you. you are a great teacher.

  • @khatwanik
    @khatwanik Před 3 dny

    Thank you Raghav!! This is very good tutorial with examples covering key topics including how to organize code and manage environments. This helped me brushing up my Terraform knowledge. It would be great if you can add a couple more chapters on how we can create a private module registry and how those modules can be referenced by multiple teams in their Project. And a tutorial on CICD with popular tools like Azure DevOps and GitHub Actions.

    • @RaghavPal
      @RaghavPal Před 3 dny

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

  • @rebekahoj
    @rebekahoj Před 4 dny

    i tried to find the link of the notes, could not

    • @RaghavPal
      @RaghavPal Před 2 dny

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

  • @intrig4
    @intrig4 Před 4 dny

    The best dockers tutorials I've ever see, thank you.