Chrome New Feature: Ask AI
3:03
14 күн бұрын
The SAST Challenge: Juice Shop
18:06
Пікірлер
@SaeedhMohd
@SaeedhMohd 8 күн бұрын
tutorial for docker tpoo
@errorfarm
@errorfarm 8 күн бұрын
I'll think about it. I can put it to my todo list. Currently I have 3 videos about Azure coming up.
@Simin-c4n
@Simin-c4n 14 күн бұрын
I got this erro sh: 1: node_modules.bincucumber-js: not found
@julesruzindana-rukundo6254
@julesruzindana-rukundo6254 15 күн бұрын
the ask ai is not available for me any idea why?
@errorfarm
@errorfarm 15 күн бұрын
It is possible. I have it on my Mac, but not mobile.
@shoryabeohar160
@shoryabeohar160 24 күн бұрын
cool
@errorfarm
@errorfarm 24 күн бұрын
Thanks! 👍
@cyberinmotion
@cyberinmotion 28 күн бұрын
thank you for the step by steps! I need some adjustment though, the SAST output does not produce any vulnerability when using Hackme source code, not sure why, but when I use other vulnerable source code (DVWA) it works like you showed.
@errorfarm
@errorfarm 28 күн бұрын
Thanks for the feedback! You can try to use different scan types. Depending on the scanner, they have code scans, infrastructure scans, dependency scans and so on. Play around a little with them.
@quangtrinhngoc3273
@quangtrinhngoc3273 28 күн бұрын
Help me I tried running serenity in gitlab with ci/cd, but so error: Could not instantiate class org.openqa.selenium.chrome.ChromeDriver I tried fixing it with a number of solutions online but it didn't work
@errorfarm
@errorfarm 28 күн бұрын
There isn't any clear fixes for that. First I'd try if Firefox or Webkit works. If one of the browsers work it's a Chrome setup issue or version issue. If none of the browsers work, it's POM issue or maybe mvn command parameter issue, like someone said that he could make it work by not using mvn clean install.
@fethizkr2970
@fethizkr2970 29 күн бұрын
thnx bro 🙏
@errorfarm
@errorfarm 29 күн бұрын
No problem
@davidarmandopalafoxbeltran4887
@davidarmandopalafoxbeltran4887 Ай бұрын
How I can see the report index.html like you ? When i want to open it, Git shows the message: "The source could not be displayed because it is stored as a job artifact. You can download it instead." I tried many things, but it keeps like that...
@errorfarm
@errorfarm Ай бұрын
It’s because your repo is private. Do you share the artifact link to someone else who possibly isn’t logged in to Gitlab?
@davidarmandopalafoxbeltran4887
@davidarmandopalafoxbeltran4887 Ай бұрын
@@errorfarm Tnx !! I didn't share it, but my Git repository is associated with a university institution... it seems that it was set to private with no way to change it. Thank you very much for the video! It was really helpful, and thank you for responding... only then I could figure out the problem.
@quang7944
@quang7944 27 күн бұрын
@@errorfarm is there anyway to view html online ? ( integrate to another tool ?
@errorfarm
@errorfarm 24 күн бұрын
@@quang7944 You could add the HTML as artifacts if it's just static HTML, but probably not. So, you can also deploy the HTML to some staging environment after the testrun, even if the tests fail. That's the first idea that comes to my mind.
@fadelkouyate1523
@fadelkouyate1523 Ай бұрын
Thanks, very helpful for me 🥰
@errorfarm
@errorfarm Ай бұрын
Thank you!
@Bla_ck_LA_Goon
@Bla_ck_LA_Goon Ай бұрын
so good❤
@errorfarm
@errorfarm Ай бұрын
Thanks for the feedback!
@AnkurBowen
@AnkurBowen Ай бұрын
¡Qué interesante ver cómo GitHub Copilot se combina con Selenium para automatizar pruebas! 🤖 Siempre me ha fascinado la automatización. ¿Alguien más ha probado esto? Estoy aprendiendo en codigо hеrое y me encanta cómo todo está en español. 😊
@JavierDíazFernández-c4b
@JavierDíazFernández-c4b Ай бұрын
Can you make the video again or help me :(, I'm having problems with the versions: [DeviceFarm] npm install npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: '@wdio/[email protected]', npm WARN EBADENGINE required: { node: '>=18.20.0' }, npm WARN EBADENGINE current: { node: 'v18.16.1', npm: '9.5.1' } npm WARN EBADENGINE } npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: '@wdio/[email protected]', npm WARN EBADENGINE required: { node: '>=18.20.0' }, npm WARN EBADENGINE current: { node: 'v18.16.1', npm: '9.5.1' } npm WARN EBADENGINE } among other errors like: Error: "ts-node/esm/transpile-only 'resolve'" did not call the next hook in its chain and did not explicitly signal a short circuit. If this is intentional, include `shortCircuit: true` in the hook's return. at new NodeError (node:internal/errors:399:5) at ESMLoader.resolve (node:internal/modules/esm/loader:846:13) at ESMLoader.getModuleJob (node:internal/modules/esm/loader:424:7) and I just follow all your steps, however the unique difference is when doing in cmd: npm install -g npm-bundle, and I see: npm warn deprecated [email protected]: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful. npm warn deprecated [email protected]: Rimraf versions prior to v4 are no longer supported npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
@errorfarm
@errorfarm Ай бұрын
Sounds like your allure reporter needs higher Node version. Can you remove allure-reporter?
@errorfarm
@errorfarm Ай бұрын
After creating this video, AWS has added support for Node version 20. Don’t use 18 anymore but use 20. So in the beginning type: nvm install 20.
@JavierDíazFernández-c4b
@JavierDíazFernández-c4b Ай бұрын
@@errorfarm THAT was the error, thank you very much!!
@errorfarm
@errorfarm Ай бұрын
@@JavierDíazFernández-c4b I’m glad you got it working. 👍🙂
@ezequielcardozo499
@ezequielcardozo499 2 ай бұрын
gracias
@errorfarm
@errorfarm 2 ай бұрын
De nada. ¡Gracias por los comentarios!
@QutaibaJaheel
@QutaibaJaheel 2 ай бұрын
Gracias
@errorfarm
@errorfarm 2 ай бұрын
De nada.
@chandankumar-wu4kq
@chandankumar-wu4kq 3 ай бұрын
I am stuck with this error: [DeviceFarm] echo "Navigate to test package directory" Navigate to test package directory [DeviceFarm] cd $DEVICEFARM_TEST_PACKAGE_PATH [DeviceFarm] echo "Starting the Appium TestNG test" Starting the Appium TestNG test [DeviceFarm] java -Dappium.screenshots.dir=$DEVICEFARM_SCREENSHOT_PATH org.testng.TestNG -testjar *-tests.jar \ -d $DEVICEFARM_LOG_DIR/test-output -verbose 10 Error: Could not find or load main class org.testng.TestNG Caused by: java.lang.ClassNotFoundException: org.testng.TestNG
@errorfarm
@errorfarm 3 ай бұрын
Did you add testng to the pom.xml?
@husnakhan7007
@husnakhan7007 3 ай бұрын
Something went wrong, please try again. We could not find the tests directory in the *root* of your test package. Please unzip your test package, verify that the tests directory is in the root of your package, and try again. I am getting this error
@errorfarm
@errorfarm 3 ай бұрын
Do you get any errors when you are going through "Create Package" part? In my video the part that starts at 5:20.
@tallurivamsi6413
@tallurivamsi6413 3 ай бұрын
why this background sound?please remove that
@errorfarm
@errorfarm 3 ай бұрын
Thanks for the feedback. I noticed later that background music is a little loud if you listen with laptops builtin speakers. I’ll tune the volume down later.
@xKomarig
@xKomarig 3 ай бұрын
How come you're referring to XPATH only in the context of browser copied generic ones? Hand written xpath is super reliable, redable and easy to lear tool.
@errorfarm
@errorfarm 3 ай бұрын
Correct. I make videos for beginners and it’s safer to teach them to use builtin locators and they can’t make mistakes. Later they can learn to distinguish what kind of XPath locator is good and what isn’t. And there’s another reason which I probably mentioned in some video that the way XPaths are resolved is browser dependent.
@lukecage9964
@lukecage9964 3 ай бұрын
nice! any way to have another video to show how to use bitbucket dynamic pipelines ? thk you for your contents!
@errorfarm
@errorfarm 3 ай бұрын
Thanks for the feedback! I'll consider that after my current project.
@lukecage9964
@lukecage9964 24 күн бұрын
@@errorfarm any news?
@errorfarm
@errorfarm 23 күн бұрын
@@lukecage9964 It’s on my list. 😊
@jamillavanveen9523
@jamillavanveen9523 4 ай бұрын
I get this error message, with exactly the same .yml file "npm error The `npm ci` command can only install with an existing package-lock.json or npm error npm-shrinkwrap.json with lockfileVersion >= 1. Run an install with npm@5 or" Can you help?
@errorfarm
@errorfarm 4 ай бұрын
Yes, of course. Check from your repo that you committed also package-lock.json. If you use npm ci, it needs that. You can also try leaving out the npm ci line, but that’s not the recommended way (by the Playwright team).
@jamillavanveen9523
@jamillavanveen9523 4 ай бұрын
@@errorfarm thanks for the Quick reply. I'm a beginner in test automation. In which folder do I need to check? In the node_modules folder I do only see a package.json and not a package-lock.json. What is the easiest way to fix this?
@errorfarm
@errorfarm 3 ай бұрын
It should be in the project folder (not in node_modules folder). Go to that folder with terminal or command prompt. Check what files are in the version control by typing 'git status'. Then add the file 'git add package-lock.json'. Commit: 'git commit -m "Added package lock file"'. Push: 'git push'.
@nutee45
@nutee45 4 ай бұрын
Good tutorial Thank you for your created.
@errorfarm
@errorfarm 4 ай бұрын
Thanks for the feedback!
@TheKer7
@TheKer7 4 ай бұрын
The name of the link relies on the name assigned to the html element, the one that pops up at mouse hovering and the one screen-readers read, correct? So for multilingual page testing the names are supposed to be "translated", Yes? Thanks for video, felt a little bit dry, maybe like AI generated, but I understand the effort needed. I got info on this topic that I am extremely moist about currently. Thanks for this, really.
@errorfarm
@errorfarm 4 ай бұрын
Yes and yes. Thanks for the feedback!
@MarkAustin-z5o
@MarkAustin-z5o 4 ай бұрын
Great. All working with my own tests. Very useful video. Thanks.
@errorfarm
@errorfarm 4 ай бұрын
Glad it helped!
@FufudJed-qv5uw
@FufudJed-qv5uw 5 ай бұрын
Hello can I connect device from aws with android studio
@errorfarm
@errorfarm 4 ай бұрын
Not that I'm aware of. I haven't thought about it though.
@milachitailo
@milachitailo 5 ай бұрын
Super helpful! Could you please also explain how to add screenshots to the report please? If it is possible of course 😊
@errorfarm
@errorfarm 5 ай бұрын
Thanks for the feedback! Saving screenshots to the reports is not supported as well as in other platforms like Playwright. I'll add that to my todo list and probably make another video about it.
@TheKer7
@TheKer7 5 ай бұрын
Thanks, I am implementing it right now. Didn't know about the /** and sharding implementation. I messed around a lot with trying to get artifacts working for snapshot storage... Have a baseline job, and then 2nd job scheduled to pass it's own artifacts around as they all have 1week expiriy... Lots of steam... Now I think I will store the snapshots with scp on a server and retrieve them everytime the test runs... That part of the management would be nice to know. our MVP for testing automation is pure visual regression testing... getting close though. Thanks for this!
@errorfarm
@errorfarm 5 ай бұрын
Thanks for the feedback!
@lukecage9964
@lukecage9964 5 ай бұрын
can you prepare a demo using playwright on bitbucket pipelines running tests with multiple workers and shards?
@errorfarm
@errorfarm 5 ай бұрын
Here's my video about test sharding: kzbin.info/www/bejne/amPNg52Zbpdmpac
@ggggg5378
@ggggg5378 5 ай бұрын
Hola, como haces para ejecutar appium en la misma terminal donde esta el emulator?
@errorfarm
@errorfarm 5 ай бұрын
Agrega un signo de ampersand después del comando.
@ggggg5378
@ggggg5378 5 ай бұрын
@@errorfarm voy a probar, gracias por responder.
@errorfarm
@errorfarm 5 ай бұрын
Por cierto en Windows usa start /B y el comando.
@ggggg5378
@ggggg5378 5 ай бұрын
Estoy iniciando en el mundo del Testing, y aprendiendo Appium y me gustaría aprender más. gracias por el aporte.
@AntharAsskoul
@AntharAsskoul 5 ай бұрын
Hola como estas? quisiera un curso me podrias pasar tu numero? o instagram
@ggggg5378
@ggggg5378 5 ай бұрын
Hola, podrías explicar como instalas Qemu y la imagen del móvil Pixel 7, gracias
@errorfarm
@errorfarm 5 ай бұрын
No he usado Qemu desde hace algún tiempo. Lo siento, no puedo ayudarte ahora.
@SQARM1
@SQARM1 6 ай бұрын
Thanks alot, please add more Playwright+Typescript tutorials
@errorfarm
@errorfarm 6 ай бұрын
Thanks for the feedback! I will try to add more Playwright content. It is my favorite framework.
@ZohrehEzatii
@ZohrehEzatii 6 ай бұрын
Thanks , very helpful 🤩
@errorfarm
@errorfarm 6 ай бұрын
Thank you for the feedback!
@frostynemz
@frostynemz 6 ай бұрын
This deserves waay more view mate, so helpful 👍🏽
@errorfarm
@errorfarm 6 ай бұрын
Much appreciated!
@KushagraDwivedi1
@KushagraDwivedi1 7 ай бұрын
What's that song
@errorfarm
@errorfarm 7 ай бұрын
There are three songs from Track Tribe: 1. Last Train North 2. As You Were 3. Now I Know
@umytumyt9773
@umytumyt9773 7 ай бұрын
Hello, first of all, I appreciate your efforts. I hope you receive ample rewards for them. How can I run a Java Selenium/Cucumber Maven test on Bitbucket Pipelines? I'd appreciate your assistance with this. When I try to run it, I encounter the following issue: 'Run 1: Failed to instantiate class stepdefinitions. Run 2: Could not start a new session. Response code 500. Message: session not created: Chrome failed to start: exited normally. (session not created: DevToolsActivePort file doesn't exist). (The process started from chrome location /opt/google/chrome/chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.)' I would be grateful for your help. Thank you. Have a productive day.
@errorfarm
@errorfarm 7 ай бұрын
Sounds like you are using a local chromedriver. My videos are not about those issues. This may help you if you want to install chromedriver yourself: www.npmjs.com/package/chromedriver
@umytumyt9773
@umytumyt9773 7 ай бұрын
@@errorfarm thanks for help. good luck for life
@umytumyt9773
@umytumyt9773 7 ай бұрын
Hi, great working
@errorfarm
@errorfarm 7 ай бұрын
Thanks!
@Sergio28290
@Sergio28290 7 ай бұрын
Great video! If it had been added how to register a gitlab runner, it would have been super
@errorfarm
@errorfarm 7 ай бұрын
Thanks for the idea!
@julios9816
@julios9816 7 ай бұрын
how to Running Tests In Parallel Using cypress-split in Bitbucket Pipelines?
@errorfarm
@errorfarm 7 ай бұрын
You can try it with parallel steps defining npx cypress split=true in multiple parallel steps. Here is how to define parallel steps: support.atlassian.com/bitbucket-cloud/docs/parallel-step-options/
@mr_possible6197
@mr_possible6197 7 ай бұрын
Can't we get the package or the apk from code pipeline artifacts once we design a build pipeline for our test automation framework ? Sorry if the question is silly, as I am new to Appium. Nice video by the way
@errorfarm
@errorfarm 7 ай бұрын
Yes we can. Here's more info about that: docs.aws.amazon.com/devicefarm/latest/developerguide/codepipeline.html
@nitinpunyani6001
@nitinpunyani6001 7 ай бұрын
I am facing issue when i run the code on aws device farm Continue... 2024-04-23T11:54:58.539Z WARN @wdio/config:ConfigParser: pattern ./test/specs/test.e2e.ts did not match any file 2024-04-23T11:54:58.539Z ERROR @wdio/cli:launcher: No specs found to run, exiting with failure 2024-04-23T11:54:58.540Z INFO @wdio/cli:launcher: Run onComplete hook Spec Files: 0 passed, 0 total (0% completed) in 00:00:04
@errorfarm
@errorfarm 7 ай бұрын
@@nitinpunyani6001 This is either wdio configuration issue or the npm bundle does not contain the test files. Check: 1. the configuration that ./test/specs/test.e2e.ts is the correct path and 2. check what is inside the npm bundle that test.e2e.ts is there.
@nitinpunyani6001
@nitinpunyani6001 7 ай бұрын
​@@errorfarm When i run the npm-bundle command after that i am facing this issue: ``````` PS D:\MobileAutomationDeviceFarm ode-device-farm> npm-bundle C:\Users\pc1\AppData\Roaming vm\v18.20.2 ode_modules pm-bundle\bin\cli.js:11 throw error ^ [Error: ENOENT: no such file or directory, open 'D:\MobileAutomationDeviceFarm ode-device-farm\.npmbundle ode_modules\device-farm\package.json'] { errno: -4058, code: 'ENOENT', syscall: 'open', path: 'D:\\MobileAutomationDeviceFarm\ ode-device-farm\\.npmbundle\ ode_modules\\device-farm\\package.json' } Node.js v18.20.2 ``````
@nitinpunyani6001
@nitinpunyani6001 7 ай бұрын
Please tell me what will be the soultion?
@MogaliPhotos
@MogaliPhotos 8 ай бұрын
Good one Martti
@errorfarm
@errorfarm 7 ай бұрын
Thank you!
@WiktorWiktorowicz
@WiktorWiktorowicz 8 ай бұрын
Hi, great tutorial. Can you help me? I don't get a artifacts. I have a tab with build only
@errorfarm
@errorfarm 8 ай бұрын
Okay. You can check with ls command if your artifact directory really exists and also that the folder contains something and it isn't empty. For example: ls -la artifact-folder/*
@MaheshJoshi_wellington
@MaheshJoshi_wellington 9 ай бұрын
Awesome
@errorfarm
@errorfarm 8 ай бұрын
Thanks!