sauce-archives/js-mocha-webdriverio-selenium

js-mocha-webdriverio-selenium's Issues

does this repo need updating?

This repo seems out-of-date.

I managed to get things going by following saucelabs/extended-debugging-JS-examples

ERROR: Couldn’t load “wdio-mocha-framework” framework. You need to install it with `$ npm install wdio-mocha-framework`!

I followed the steps in the readme.
When I go to run the tests using $ ./node_modules/.bin/wdio wdio.conf.js
I get the following error:
ERROR: Couldn’t load “wdio-mocha-framework” framework. You need to install it with $ npm install wdio-mocha-framework!

When I got to install mocha using: npm install wdio-mocha-framework
I get the following output:

2 warnings and 9 errors generated.
make: *** [Release/obj.target/fibers/src/fibers.o] Error 1
gyp ERR! build error 
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:262:23)
gyp ERR! stack     at ChildProcess.emit (events.js:182:13)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:240:12)
gyp ERR! System Darwin 18.2.0
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--release"
gyp ERR! cwd /Users/nikolayadvolodkin/Documents/Source/JavaScript/JS-Mocha-WebdriverIO-Selenium/node_modules/wdio-sync/node_modules/fibers
gyp ERR! node -v v10.14.2
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok 
node-gyp exited with code: 1
Please make sure you are using a supported platform and node version. If you
would like to compile fibers on this machine please make sure you have setup your
build environment--
Windows + OS X instructions here: https://github.com/nodejs/node-gyp
Ubuntu users please run: `sudo apt-get install g++ build-essential`
Alpine users please run: `sudo apk add python make g++`
sh: nodejs: command not found
npm WARN [email protected] No license field.

npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! [email protected] install: `node build.js || nodejs build.js`
npm ERR! spawn ENOENT
npm ERR! 
npm ERR! Failed at the [email protected] install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/nikolayadvolodkin/.npm/_logs/2019-03-19T19_30_45_012Z-debug.log

get an instance of driver in my tests?

How do I get an instance of driver in my tests?

  basicAuth(user, pass){
    return driver.switchTo().alert().authenticateUsing(new UsernamePasswordCredentials(user, pass));
  }

Move all tests to sample-app-web repo to remove redundancy?

So, I know that we want to have sample repos. However, I can see that we have redundancy between this repository and this one: https://github.com/saucelabs/sample-app-web/tree/master/test/e2e/specs

I was thinking that we can move all the best practices code to this repo instead https://github.com/saucelabs/sample-app-web/tree/master/test/e2e/specs:

• It will reduce maintenance and duplication
• I think that sample-app-web is more official and a better framework example than this repository because it actually contains a web app to play with.
• The tests in that repository are crappy and need to be rewritten.

Do you agree? If so, I can add text to the Readme.md saying that this repo has moved here https://github.com/saucelabs/sample-app-web/tree/master/test/e2e/specs . And move over the code there and make sure that it works there.

Does not update test/job status via Sauce REST API

Need to update status as pass/fail. Currently Sauce dashboard shows 'complete'.