-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I am unable to run any of the samples #101
Comments
Please see the Troubleshooting guide in the Botium Wiki: https://github.com/codeforequity-at/botium-core/wiki/Troubleshooting |
i did try all the options. i am still not able to run any of the samples here. all i am doing is "npm install", is there any per-requisites needed? any specific version on node? |
Did you have a look on the Botium CLI ? Maybe this is more suitable for you. You don't need extra Node installation, everything is precompiled (for Windows, Linux, Mac). |
@ShamaUgale did u manage to work around this? Experiencing the exact same issues - mac, node 8.10.0 |
No. I could not fix the issue. I am still facing it. By any chance were you able to figure out any solution to it? If i find one will document it and share across the community for sure. |
Did you try the Botium-CLI ? Should work on Mac as well. |
https://stackoverflow.com/questions/53519661/how-to-run-a-simple-botium-test-against-watson This is how i ran botium and it worked |
Thanks for the link @LacikIgor |
I am doing
npm install
npm run test
for example for slack this is the error i get
npm install
npm WARN [email protected] No repository field.
npm ERR! path /Users/shamau/Downloads/testmybot-master/samples/slack/node_modules/.staging/testmybot-23018b42/node_modules/accepts
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall rename
npm ERR! enoent ENOENT: no such file or directory, rename '/Users/shamau/Downloads/testmybot-master/samples/slack/node_modules/.staging/testmybot-23018b42/node_modules/accepts' -> '/Users/shamau/Downloads/testmybot-master/samples/slack/node_modules/.staging/accepts-09f9c3ce'
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! /Users/shamau/.npm/_logs/2018-10-31T14_40_24_408Z-debug.log
The text was updated successfully, but these errors were encountered: