Closed nidhi-m25 closed 5 years ago
Any updates team?
no, research ongoing why the precompiled thing is not working. For the first problem (npm install -g botium-cli), no idea why this is not working for you. This is more a Git or NPM problem than a Botium problem.
Are both the issues related ?
https://github.com/codeforequity-at/botium-connector-directline3/issues/27
There is a component referenced which is download from Github on installation, but the git call fails with error code 128 - there is a very broad range of things this could mean, we wrote done some of them here: https://botium.atlassian.net/wiki/spaces/BOTIUM/pages/28934174/Git+Error+128
As there are a growing number of referenced libraries depending on dynamic module resolution, we are forced to abandon the precompiled version of the Botium-CLI. There will be a docker image serving the same purpose very soon.
Botium CLI docker image available now https://hub.docker.com/r/botium/botium-cli
Unable to install botium cli Botium CLI using the below comand- npm install -g botium-cli
Error-->
pm ERR! Error while executing: npm ERR! C:\Program Files\Git\cmd\git.EXE ls-remote -h -t https://github.com/codeforequity-at/jsonpath.git npm ERR! npm ERR! undefined npm ERR! exited with error code: 128
Botium standalone is download from the
and ran the botium-cli run Botium Test-Suite
0 passing (27ms)
1 failing
1) Botium Test-Suite
1) If you want to compile the package/file into executable, please pay attention to compilation warnings and specify a literal in 'require' call. 2) If you don't want to compile the package/file into executable and want to 'require' it from filesystem (likely plugin), specify an absolute path in 'require' call using process.cwd() or process.execPath.
Note-> node module esprima is already downloaded.