-
Notifications
You must be signed in to change notification settings - Fork 59
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
Abao Tests Not Running #242
Comments
Didn't provide enough information for me to help.
Not there with you. Screenshots always nice. |
I have a similar problem. My environment is version v0.5.3, but the npm test fails. I’ll keep you posted. |
The Abao version is 0.5.0 In the past, when I ran my command abao ../raml/api.raml --hookfiles=tests/raml/test_machines_hooks.js --server http://localhost:5000 Found Hookfiles: tests/raml/test_machines_hooks.js However now I get: Found Hookfiles: tests/raml/test_machines_hooks.js
0 passing (6ms)
In another branch, I only get Found Hookfiles: tests/raml/test_machines_hooks.js but am not sure what may cause the rest to stop. I would like to run it as it was before. Right now it either doesn't run at all or throws the error as above. |
@jtodo, you have the exact same error, or something else? @NikhilPunwaney, BTW, shouldn't your hookfile be named "test_batches_hooks.js" (format: "test_<endpoint>_hooks.js") Can either of you provide me with a copy of something I can test locally? |
Hi @plroebuck |
Are you able to reproduce the issue? following details may help to reproduce the issue:
Console output:
0 passing (10ms)
|
Troubleshooting errors reported. See if problem caused by recent release. #242
@raj-bhagya, you sent a couple Python files but nothing that I could run myself. Unable to reproduce more than a portion of the required package, I can't do anything with what you provided. Abao-0.6.0 now builds successfully with related patches to further lockdown dependencies. |
@plroebuck , Our services are developed on Flask web application framework written in Python. |
I Installed latest development version Abao-0.6.0, but I'm encountering different error only with this version where as the previous version 0.5.0 is not throwing this error. I'm suspecting this could be because of node version compatibility, please suggest solution. 0.6.0 Installation output:
[ Error: TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received type object |
@raj-bhagya, I don't get an error on my side (displays usage) but to display the version type: $ abao --version |
Same error with abao --version also, basically getting this error with any abao command option. [~/repos/simile/simile_web_service → develop]$ abao --version TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received type object |
Line numbers don't exactly match expected, but only place Original (line 35): prog = path.basename pkg.bin For quick test, change that line to be: prog = 'abao' What OS version for my reference? |
I hardcoded value to prog = 'abao' in line 35, but still same issue. |
I'm running macOS-10.13.4 so OS-wise this code should have no problems. $ node --version
v10.3.0
$ bin/abao --version
0.6.0 What is displayed for this command? $ which abao Should be impossible to get the same error if you replaced Line 35 above with the hardcoded value! |
$ which abao |
Copy'n'paste the Also: $ npm list --depth=0 |
|
parseArgs = (argv) ->
'use strict'
allOptions = _.assign {}, abaoOptions, mochaOptions
mochaOptionNames = Object.keys mochaOptions
prog = path.basename pkg.bin <--- Thought you changed this line
return yargs(argv)
.usage("Usage:\n #{prog} </path/to/raml> [OPTIONS]" +
"\n\nExample:\n #{prog} api.raml --server http://api.example.com")
.options(allOptions)
... |
I changed that line and tried. Meantime time I tired to downgrade node version to 8.11.1 and reinstalled abao-0.6.0 (Just to see if there is compatibility problem), that's why it changed back to original state.
[~/repos/simile/simile_web_service/tests/raml → develop]$ npm list --depth=0
|
So I'm lost. If the code is changed, how are you still getting the same error referring to |
[/usr/local/lib/node_modules/abao]$ npm list --depth=0
Is there any other occurrence of basename? do I need to build anything after changing that line? |
Rerun |
$ abao --version
|
I got that fixed, there was a problem with my local setup. I was changing basename in one user's library not globally, changed it globally and working fine now. Sorry about that. $ abao --version Looks like raml tests are also running fine with |
…ge.json" Field is treated differently after installation. Originally given as a string, the install converts it to a map. Changed to use map with named field. Updated CLI to reference the named field. Fixes #242
Found the |
@plroebuck |
@raj-bhagya: How can I install Abao 0.6.0? I tried the following but still got 0.5.3 |
My Abao tests are not running: upon running the test, I get the message: Found Hookfiles: tests/raml/test_machines_hooks.js
But none of the tests run as they did before.
Nothing has changed about the hookfiles or the RAML. Please advise what could have caused this issue
The text was updated successfully, but these errors were encountered: