I am trying to use phantom-jasmine. I have installed phantomjs (1.9.1) on my systems ( Mountain Lion and Ubuntu) and phantom-jasmine using npm.
The problem is when I try to run phantom-jasmine examples/TestRunner.html from their example I am getting 0 specs, 0 failures although it should be 3 specs, 1 failures in the output.
If I open the TestRunner.html from a browser it is behaving as expected but phantom-jasmine cant seem to find the specs.
Another thing is when I provide the absolute path (phantom-jasmine /home/me/phantom-jasmine/examples/TestRunner.html to the TestRunner.html this happens
Not entirely sure why, but I got the examples running by omitting TestRunner.html from the call. Like this:
phantom-jasmine examples
It seems that the branch/version you get when installing using npm does not match what is described at https://github.com/jcarver989/phantom-jasmine.
Looking at the installed readme.md helped me.
I had the same problem. In the meantime, I ended up switching to a new set of scripts to run jasmine tests with phantomjs from the command line. See SenchaProSvcs/UnitTestDemo.
I faced the same issue with phantom-jasmine. In order to get this to work I relied on run_jasmine_test.coffee file from the phantom-jasmine repo. I copied this file (and the console-runner.js) in my repo and invoked the testRunner via phantomjs by running the following command in my terminal:
phantomjs lib/jasmine/run_jasmine_test.coffee testRunner.html
The output I got here was consistent with the output I got when I ran the testRunner.html directly in the browser.
Hope this helps.
Related
I tried this framework called Frontity. For the first try (run) everything was good, I had my demo page, and it worked well. I follow these instructions.
For the second compile I got these error, and a lot: There are multiple modules with names that only differ in casing.
Only change what I have done was this one (connecting my frontity to my WordPress): https://docs.frontity.org/getting-started/connecting-to-wordpress
(Again: for the first run, it was good.)
Nothing, literally nothing was changed, I do not even started any other software :)
After all this, I deleted everything, moved to another folder, started over the whole thing and for now I only get the same errors, and an Internal Server Error in my browser.
I have this issue with or without running the xampp server.
Any idea what went wrong?
Localhost WordPress (xampp), localhost:3000 Frontity (default), Windows 10, Chrome browser.
errors after compile
Your problem is here in the console output:
I'm not sure at which point those files with differing cases are
generated, but I think the following should fix your issue:
https://stackoverflow.com/a/53901224/2638310
Ensure that the path you used in your terminal has the correct
capitalization. For example if you're using git bash on Windows and
your project has the following path:
C:\MyProjects\project-X
If you access it using cd /c/myprojects/project-x (note the lack of
capital cases) and then run npm start you might face this problem.
The solution would be to consider the project path case-sensitive and
use it as follows:
cd /C/MyProjects/project-X
So i am following along a lynda tutorial video for node.js, and it was suggested to download the node.js binding for brackets so that we can have a terminal inside of brackets to run our node.
However, whenever I try to run I get the following:
/bin/sh: node: command not found
Program exited with status code of 127.
The terminal path where it is showing its attempt at running node is:
"/Users/userName/Documents/lynda_practice/nodejs/my-module.js". I am at a complete loss as to why this rather poorly documented plugin is incapable of finding node considering that I can run it just fine if i use my mac's terminal. As is seen here, while being located in the same directory:
node module-demo.js
text from module: Hello from module
These are multiple debugger are available in Bracket
top hundred packages of Bracket
I ran into the same problem, and based on your post I think I'm doing the same Lynda.com training. What I did is I uninstalled Brackets 1.8 and instead installed Brackets 1.7. In Brackets 1.7 I was able to install the Node.js Bindings with the extension manager as they do in the training video. Here is a link to the Brackets 1.7 download: https://github.com/adobe/brackets/releases/tag/release-1.7
I'm running on Windows 7 and this fixed the problem for me. Hope it helps!
From the research I did for the topic, I saw some recommendations to install tty.js with npm, but it wouldn't install as well - some sort of python exe missing from the system error.
I am able to run the program from Git CMD but it is all confusing for me because I am familiar with unix based consoles :(
The way I installed node.js and npm : All was doen with the installer provided by node.js.
Any insights? Thank you in advance!
I have installed tty.js in a linux enviroment and it works great, you should some building essentials installed, such as:
gcc
g++
make
As well as Python 2.7. When installing using npm, it will look for all the dependencies and as I understand it will compile some C code that does the magic behind the scenes. I haven't tried it on Windows, but what I have seen there is the C code designed for windows, so it probably will run.
Maybe I will be of more help if you copy what you get on the npm installation.
have you tried using Git Bash? That is what I used for the most part as well and acts more unix like. If you're on a PC, an alternative is using ConEMU as they give you a shell that is unix like. Just wanted to give you some options if you're still running into trouble, I know this is super late :)
For the better part of a day now I've been trying to get node.js to work on my computer.
Even though I get no errors during installation, whenever i try to run node or npm from the command line I only get the error "Evented I/O for V8 JavaScript has stopped working" and then nothing happens.
I really have no clue why it isn't working and what I have to do to get it to work! Has anyone else ever had the same problem and were you able to fix it somehow?
It seems the problem was with ansicon which I installed together with cucumber.
I was able to fix the problem by running "ansicon -u" in my x64 folder
Regarding plugin for Coda 2. I am having some problems making it work. I have written a small test program in CoffeeScript, but when i try to run and/or compile I get the following error message:
All settings/env. variables should be set correctly:
Do you have any idea as to what that may cause this issue? I have installed node using homebrew, and then coffee script via npm. All the shell variables have been verified, and I am able to run node from the command line and write scripts there. Also, when i go to settings and click on "About", I get the following:
Hope you can help.
Thank you and best regards,
Thomas
In Terminal, run the command:
which coffee
For me, this gave:
/usr/local/bin/coffee
So in the CoffeeScript Plug-In Settings, I set PATH to:
/usr/local/bin
Then when I went to the About box, it showed the version of CoffeeScript that I have installed and the Run & Compile options then worked fine.