Run NodeJS Tests in AWS Device Farm (Appium, Android)

[@MarkAustin-z5o]

Great. All working with my own tests. Very useful video. Thanks.

[@errorfarm]

Glad it helped!

[@mr_possible6197]

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]

Yes we can. Here's more info about that: docs.aws.amazon.com/devicefarm/latest/developerguide/codepipeline.html

[@nitinpunyani6001]

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]

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

​@@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]

Please tell me what will be the soultion?

[@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/allure-reporter@9.1.3', 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/reporter@9.1.3', 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 inflight@1.0.6: 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 rimraf@2.7.1: Rimraf versions prior to v4 are no longer supported npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported npm warn deprecated glob@6.0.4: Glob versions prior to v9 are no longer supported

[@errorfarm]

Sounds like your allure reporter needs higher Node version. Can you remove allure-reporter?

[@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]

@@errorfarm THAT was the error, thank you very much!!

[@errorfarm]

@@JavierDíazFernández-c4b I’m glad you got it working. 👍🙂