Do you know this way to Run WebdriverIO tests from Jenkins using GitHub project

No video

Do you know this way to Run WebdriverIO tests from Jenkins using GitHub project

Рет қаралды 3,694

Күн бұрын

Free Courses - AutomationStep...
Prerequisites
Project is uploaded on GitHub (or any Repository)
Jenkins is setup
Step 1 - Create a job on Jenkins
Step 2 - Add repository url in Source Code Management section along with credentials
Step 3 - In Build section add the commands to install libraries and run tests npm install
npx wdio
(node js must be setup on the system where jenkins is running)
Step 4 - Run Job and check results
Ref - Jenkins Masterclass - • Jenkins Complete Cours...
Jenkins Hindi Tutorials - • Jenkins Day 1 | Step b...
▬▬▬▬▬▬▬
Every Like & Subscription gives me great motivation to keep working for you
You can support my mission for education by sharing this knowledge and helping as many people as you can
If my work has helped you, consider helping any animal near you, in any way you can
Never Stop Learning
Raghav Pal
▬▬▬▬▬▬▬▬ USEFUL LINKS ▬▬▬▬▬▬▬▬▬
Ask Raghav - bit.ly/2CoJGWf
GitHub Repositories - github.com/Rag...
Udemy Discounts - automationstep...
Stories - automationstep...
▬▬ CI | CD | DEVOPS ▬
Jenkins Beginner - bit.ly/2MIn8EC
Jenkins Tips & Trick - bit.ly/2LRt6xC
Docker - bit.ly/2MInnzx
Jenkinsfile - bit.ly/3JSMSZ7
Kubernetes - bit.ly/2MJIlMK
▬▬ UI TESTING ▬
Selenium Beginners - bit.ly/2MGRS8K
Selenium Java Framework from Scratch - bit.ly/2N9xvR6
Selenium Python - bit.ly/2oyMp5x
Selenium 4 - bit.ly/3AiJOlP
Selenium Tips - bit.ly/2owxc50
Selenium Builder - bit.ly/2MKNtlq
Katalon Studio - bit.ly/2wARFdi
Robot Framework with RIDE- bit.ly/2Px6Ue9
Robot Framework with Eclipse - bit.ly/2N8DZxb
Protractor - bit.ly/2KtqVkU
AccelQ - bit.ly/3PlsAsh
Test Project - bit.ly/2DRNJYE
Cucumber BDD - bit.ly/3Cnno4z
Cypress - bit.ly/3PpEukM
Playwright - bit.ly/3iuPByJ
WebdriverIO - bit.ly/3IJyofA
XPath & Web Locators - bit.ly/3PpEvoQ
▬▬ API TESTING ▬
Web Services (API) - bit.ly/2MGafL7
SoapUI - bit.ly/2MGahmd
Postman - bit.ly/2wz8LrW
Postman 2022 - bit.ly/3JWm4qX
Rest Assured - bit.ly/3zUdhRD
Karate API Testing - bit.ly/3w3H5Ku
General - bit.ly/2PYdwmV
JMeter API Testing - bit.ly/3AgVPar
Katalon Studio API Testing - bit.ly/2BwuCTN
API Mocking - bit.ly/3bYPsjS
▬▬ MOBILE TESTING ▬
Appium - bit.ly/2ZHFSGX
Mobile Playlist - bit.ly/2PxpeUv
▬▬ PERFORMANCE TESTING ▬
JMeter Beginner - bit.ly/2oBbtIU
JMeter Intermediate - bit.ly/2oziNVB
JMeter Advanced - bit.ly/2Q22Y6a
JMeter Tips & Tricks - bit.ly/2NOfWD2
Gatling - bit.ly/3QrWfkV
Performance Testing - bit.ly/2wEXbLS
▬▬ SOURCE CODE MANAGEMENT ▬
Git & GitHub - bit.ly/2Q1pagY
GITLAB - bit.ly/2kQPGyQ
▬▬ IDE ▬
Eclipse - bit.ly/3AnRhQP
IntelliJ IDEA - bit.ly/3AnyDZ8
Visual Studio Code - bit.ly/2V15yvt
▬▬ PROGRAMMING ▬
Java Beginners - bit.ly/2PVUcXs
Java Tips & Tricks - bit.ly/2CdcDnJ
Groovy - bit.ly/2FvWV5C
JavaScript - bit.ly/2KJDZ8o
TypeScript - bit.ly/3dvJBmz
Python - bit.ly/2Z4iRye
Ruby - bit.ly/3JRRmzf
▬▬ BUILD TOOLS ▬
Maven - bit.ly/2NJdDRS
Gradle - bit.ly/30l3h1B
▬▬ CLOUD SERVICES ▬
Browserstack - bit.ly/3w7kxZn
Saucelabs - bit.ly/3w7kAo1
LambdaTest - bit.ly/3C6TBwM
▬▬ DATA FORMATS ▬
JSON - bit.ly/3w450tq
XML - bit.ly/3PqRneH
▬▬ OTHERS ▬
Virtualization on Windows - bit.ly/2SItIL9
Mock Interviews - bit.ly/3QGwwVJ
Redis - bit.ly/2N9jyCG
Misc - bit.ly/2Q2q5xQ
Tools & Tips - bit.ly/2oBfwoR
QnA Friday - bit.ly/2NgwGpw
Sunday Special - bit.ly/2wB23BO
-

Пікірлер: 18

@xXMrThomasXx Ай бұрын

Thanks for show me where I must write comment for run wdio. I know git and added simply but I don`t know next step to run. Good day :)

@RaghavPal Ай бұрын

Glad it helped

@kianaparsi8223 7 ай бұрын

Fantastiskt 🙏🙏🙏🙏

@RaghavPal 7 ай бұрын

Thanks

@TheSuperkreeper 9 ай бұрын

Good afternoon. There is such an error when I click the build now button. ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job. Finished: FAILURE

@RaghavPal 9 ай бұрын

The error message "ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job. Finished: FAILURE" indicates that WebdriverIO is unable to identify any changes to the codebase to build. This could be due to several reasons, such as: 1. **No Changes:** There are no actual changes in the codebase since the last build. WebdriverIO only builds when it detects changes in the code. 2. **Incorrect Repository Configuration:** The repository URL or branch configuration specified in the build job is incorrect. Verify that the provided repository URL points to the correct codebase and that the branch name is valid. 3. **Access Issues:** WebdriverIO may not have access to the repository. Check if the credentials used for accessing the repository are correct and that there are no access restrictions. 4. **Git Configuration:** Ensure that Git is properly configured on the system where the build job is running. Verify that the Git executable is accessible and that the system user has the necessary permissions to access the repository. 5. **Cache Issues:** If WebdriverIO has cached a previous version of the repository, it may not detect the latest changes. Try clearing the cache or forcing a full repository fetch. 6. **WebdriverIO Version:** Ensure you're using a compatible version of WebdriverIO. Older versions may have compatibility issues or bugs that have been fixed in newer releases. To resolve this issue, follow these steps: 1. **Verify Code Changes:** Check if there are any actual changes in the codebase that need to be built. If there are no changes, the build job will not trigger. 2. **Validate Repository Configuration:** Double-check the repository URL and branch configuration in the build job. Ensure the URL is correct and the branch name is valid. 3. **Check Access Permissions:** Verify that the credentials used for accessing the repository are correct and that there are no access restrictions preventing WebdriverIO from fetching the code. 4. **Review Git Configuration:** Confirm that Git is properly installed and configured on the system. Check the Git executable path and ensure the system user has the necessary permissions to access the repository. 5. **Clear Cache:** If the issue persists, try clearing the WebdriverIO cache or forcing a full repository fetch to ensure that the latest changes are detected. 6. **Update WebdriverIO:** Consider updating to the latest stable version of WebdriverIO. Older versions may have bugs or compatibility issues that have been addressed in newer releases.

@sq1237 Жыл бұрын

Hello my friend, I enjoy ur videos very much. I do have a very specific question regarding Appium's behaviour on different networks in regards of performance. Is there any way I can steal some of your time to ask my question? Thanks in advance!

@RaghavPal Жыл бұрын

Hi, pls let me know in detail. Also if possible, ask your ques in the comments of relevant video

@maksudahmedgalagali8349 Жыл бұрын

Hello sir, In my job it's shows running in chrome and after some time it shows failed in chrome . Ut doesn't open Google chrome .. what may be the possible reasons? Could you help me resolve it?

@RaghavPal Жыл бұрын

Hi Maksud, When your WebdriverIO job shows "running in chrome" but then fails without opening Google Chrome, there could be several possible reasons for this issue. Here are a few potential causes and their solutions: 1. Chrome Driver version compatibility: 2. Chrome binary path configuration: 3. Chrome installation issue: Ensure that Google Chrome is correctly installed on your machine. Sometimes, incomplete or corrupt installations can cause issues with launching Chrome. Try reinstalling Chrome to see if it resolves the problem.

@travel_with_christybijil Жыл бұрын

Hi, in my project we need to download edge driver from jenkins however its not there in nexus repository. So is there a way to copy the manually downloaded edge driver into the node module folder after performing ‘npm install’ command?? Is there a way to incorporate it???

@RaghavPal Жыл бұрын

In order to use the manually downloaded Edge driver with WebdriverIO, you can set the path to the driver executable using the path property of the edgeOptions object in the capabilities configuration. Here's an example configuration: exports.config = { // ... capabilities: [ { browserName: 'MicrosoftEdge', 'ms:edgeOptions': { binary: './drivers/msedgedriver.exe', args: ['--start-maximized'], path: './drivers/msedgedriver.exe' } } ], // ... }; Here, the binary property specifies the path to the driver executable for WebDriverIO's internal use, while the path property specifies the path to the driver executable for the Edge driver itself. Make sure to adjust the paths to the correct location of the driver executable on your system. Also, be sure to include the --start-maximized argument in the args array if you want the browser to start maximized. After setting the capabilities configuration, you can launch the Edge browser by running a test or a command in your WebDriverIO project. The test or command should automatically launch the Edge browser using the specified driver.

@travel_with_christybijil Жыл бұрын

@@RaghavPal Thank you so much for such detail explanation!!

@user-fy3hb5cx6u Жыл бұрын

Hi Sir Raghav i hope you are doing well...!! I really like your tutorials of everything.. I have learned a lot of things from you and continue learning it... sir I have facing some issue with my localhost, I don't know what is the issue whenever I search localhost8080, it always says "This site can't be reached " please help me to resolved this issue. It was work fine at first but after refreshing page this error occurs. And still continue

@RaghavPal Жыл бұрын

Hi Wajeeha I assume this is the issue you are facing while accessing jenkins on the url localhost:8080 When you start Jenkins on cmd prompt, pls check if you see the message "Jenkins is fully up and running" If not, it may be possible that jenkins is not started. May be port 8080 is not available. In that case, you can try starting jenkins on a diff port using command: java -jar jenkins.war --httpPort=9090 If you still face issue, pls check if jenkins is installed properly, Can try reinstalling Also check jenkins and java version compatibility: www.jenkins.io/doc/administration/requirements/java/

@user-fy3hb5cx6u Жыл бұрын

Jenkins is opened now on localhost8080... thank you sir for help:-)

@surajsurya1414 6 ай бұрын

Hi Raghav, Hi Raghav, I am generating a html file (reportFilename: "[status]_[datetime]-[name]-report",) in the this path /Users/Suraj/.jenkins/workspace/CypressGitProject/cypress and have added Post Build action to generate HTML Reports. HTML Directory is set to cypress/reports/ and index page as *.html. But after running the build, when i view the report, it is giving me an option to download zip file instead of showing mochawesome report. Could you please help me on this. Thank You

@RaghavPal 6 ай бұрын

Suraj Here are consolidated steps and insights to address the problem: 1. Verify HTML Publisher Plugin Configuration: - HTML Directory: - Double-check that the HTML Directory path in your Post Build Action for "Generate HTML Reports" matches the exact location where your HTML report file (`[status]_[datetime]-[name]-report.html`) is being generated. It should be `/Users/Suraj/.jenkins/workspace/CypressGitProject/cypress/reports/` in your case. - Consider using relative paths within the workspace if you prefer more maintainable configurations. - Index page: - Ensure that the "Index page" field is set to `*.html` to capture your specific report file, including the dynamic timestamp portion. This enables Jenkins to identify the report for display. - Advanced Settings: - If you're using advanced options, ensure they align with your expectations. Consider disabling compression or archiving if they might be interfering with direct HTML display. 2. Explore Mochawesome Configuration: - Report Generation Path: - If you're using a custom Mochawesome configuration, verify that the report generation path points to the `cypress/reports/` directory within your workspace. - Direct Display Options: - Check if your configuration has settings that control whether to display the report directly or create a ZIP file. Look for options like `reportDir` or `html` and adjust them accordingly. 3. Check Plugin Compatibility and Updates: - HTML Publisher Plugin Version: - Ensure you're using a compatible version of the HTML Publisher Plugin with your Jenkins version and Mochawesome reports. Consult plugin documentation and release notes for version requirements. - Plugin Updates: - Keep both the HTML Publisher Plugin and Jenkins updated to benefit from bug fixes and compatibility improvements. 4. Troubleshoot and Debug: - Jenkins Logs: - Examine Jenkins logs (Manage Jenkins -> System Log) for any error messages related to the HTML Publisher Plugin or report generation. This might provide clues about potential issues. - Test Locally: - Try running your Cypress tests locally and generating the report independently to isolate the problem to Jenkins specifically. Additional Tips: - Mochawesome Configuration File: - If you're using a custom Mochawesome configuration file, double-check its syntax and ensure it's valid and well-formed. - Browser Compatibility: - While unlikely, confirm that your browser supports displaying HTML reports directly. Try different browsers if necessary. - Jenkins Restart: - Occasionally, restarting Jenkins can resolve temporary glitches or configuration issues. ..