ixmeza / wdio.conduit

Automated tests for Conduit web page using webdriverio, mocha, chai, faker.js and azure pipelines
2 stars 1 forks source link

[HELP] webdriverIO on DevOps azure pipeline #1

Open RollerIn opened 2 years ago

RollerIn commented 2 years ago

Hello, it seems you have played with azure pipeline, please do let me know what steps I need to take to implement for wdio am using webdriverIO+appium+allure reports I tried as follows

# Node.js
# Build a general Node.js project with npm.
# Add steps that analyze code, save build artifacts, deploy, and more:
# https://docs.microsoft.com/azure/devops/pipelines/languages/javascript

trigger:

pool: vmImage: ubuntu-latest

steps:

when I trigged getting the following error

Generating script.
========================== Starting Command Output ===========================
/usr/bin/bash --noprofile --norc /home/vsts/work/_temp/eed6a011-1484-4440-a3cc-58bb3d57f80e.sh
npm WARN saveError ENOENT: no such file or directory, open ‘/home/vsts/work/package.json’
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN enoent ENOENT: no such file or directory, open ‘/home/vsts/work/package.json’
npm WARN work No description
npm WARN work No repository field.
npm WARN work No README data
npm WARN work No license field.
audited 15 packages in 0.33s
found 4 high severity vulnerabilities
  run `npm audit fix` to fix them, or `npm audit` for details
npm ERR! code ENOENT
npm ERR! syscall open
npm ERR! path /home/vsts/work/package.json
npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, open ‘/home/vsts/work/package.json’
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/vsts/.npm/_logs/2021-12-09T10_58_39_570Z-debug.log
##[error]Bash exited with code ‘254’.
Finishing: npm install and build
4:47
npm ERR! path /home/vsts/work/package.json
ixmeza commented 2 years ago

Hi @RollerIn , my pipeline is also failing now and my guess is that I have outdated dependencies. In your case it looks like it has issues finding the package.json, do you have it on your repo and at the top?