Just trying to start Angular Testing with Karma. I did install and create my karma.config. On CMD when I start my karma, it runs without any problems and opens both of my browsers (Chrome Canary and Firefox)
However it doesn't show Tests on browser. And I don't get any error from karma or anything written on my console.
My File structure and file part of karma.conf.js:
And in my .spec.js file when I write a basic test just to see if it is running properly, in WebStorm it gets underlined. Here is a screenshot for this:
None of the other similar topics on StackOverflow helped me. I am stuck with this error.
What can be the reason for that?
It looks and sounds like WebStorm is trying to run your tests in a Node.js environment as opposed to a Karma environment.
Try making a Karma run configuration for your karma.conf.js file.
More details about making a run configuration can be found here: https://www.jetbrains.com/help/webstorm/2016.3/running-unit-tests-on-karma.html#runConfigurationKarma
I'm building an AngularJs web application in WebStorm. I use browserify as a bundling package, and gulp as a task runner.
I tried setting breakpoint on the individual Javascript file in Webstorm and run Debug. But, I'm not unable to hit the breakpoint.
Also, I tried debug a angularjs application without browserify and gulp. I was able to debug in Webstorm.
Is it possible to run debug in a bundled javascript file? How would we make that work?
If not, what could be the reasons?
Found a solution to this problem. We will need to upgrade to Webstorm 10. Webstorm 9 doesn't support source map in debugging mode.
I have set up an angular application using Yeoman generator. It works fine, builds fine and unit tests work. I have also added Protractor for e2e tests.
I've set up Webstorm to run the unit tests as a Node.js run configuration, which executes grunt-cli\bin\grunt with the test build task. It runs fine from the IDE.
However when I'm trying to debug, the execution never stops on breakpoints.
The console output is of little help. The tests simply succeed/fail as expected and that's it.
What could be wrong?
it doesn't seem to be possible to debug protractor tests in webstorm right now. Please vote for protractor support: WEB-9236
I want to use Chutzpah to run JavaScript unit tests in Visual Studio 2013.
As long as I don't reference angular.js the tests will run.
Using angular.js those tests won't run and the VS Output gives me the following message:
Error: Error: Instrumentation error, you cannot redefine the 'window' variable in file:///e:/.../scripts/angular/angular.js:1529
in file:///C:/USERS/.../APPDATA/LOCAL/MICROSOFT/VISUALSTUDIO/12.0/EXTENSIONS/MWY50QF4.VGS/TestFiles/Coverage/blanket_jasmine_v2.js.**
Does anyone know about this problem?
This is only an issue if you are running code coverage. This is an issue with Blanket.js (the library Chutzpah uses for code coverage) and Angualr.js conflicting. See this issue for more details: https://github.com/alex-seville/blanket/issues/311
In short, a simple workaround is to use the minified version of Angular.js
I am trying to figure out a simple way to run tests on angularjs application.
I am new to the testing world, so it's a little hard to understand all the options and the difference between them.
My goal: to be able to run the tests simply from within my IDE - Eclipse.
And to tests the code on google chrome browser.
I found jasmine to be the obvious choice for writing js unit tests. The problem is choosing a runner both for the jasmine tests and for e2e tests.
Trying to keep it simple, I've come up with the following idea for a setup:
Write the unit tests in jasmine, and the e2e tests in phantomjs and syn.js.
Then configure eclipse to run phantomjs as an external tool, so that the output will go to the console in eclipse.
I also plan to have a CI job in Jenkins, and to my understanding Jenkins can also run phantom, so theoretically this solution will work the same for CI.
Alternatively, there are test running tools like Karma and Protractor. On one hand, they seem to be recommended, but on the other hand they seem to me like overkill in some cases. They require a lot of different tools/services/processes to be running in order to work, and it seems like a pain maintain all that setup if it breaks.
To my understanding: protractor runs on webdriverjs which runs on nodejs, and it requires a selenium server to be running in the background, and on top of all that the selenium opens real browser windows which seems a little pointless as opposed to headless browser testing.
Then there is Karma, that I did not yet fully understand what it's supposed to do. From what I've read it monitors the files in my project and whenever a file is changed it runs the tests. I'm not sure how it runs the tests - is it also using selenium?
And lastly, there are grunt and yeoman, which I did not understand at all what they do and how they interact or fit together with the other tools I've listed.
I would appreciate if someone could clarify what these different tools do, and how they fit together. Also, how would they fit with Jenkins as a CI server?
Also if you could comment on my "simpler setup" - does it make sense? Am I missing something?
Karma is for unit testing your JS, regardless of whether it is using Angular or not. The ins and outs of unit testing with Karma are covered very well here: http://www.yearofmoo.com/2013/01/full-spectrum-testing-with-angularjs-and-karma.html. Yes, Karma opens and closes browser windows as needed and specified in the configuration file. If you don't want any browser windows opened, you can use PhantomJS. You can run Karma from within most any IDE that is capable of running an external script, or run it via the command line.
Protractor is for end-to-end (or E2E) testing of your project as a whole. It will open a browser window and click through the pages as though it were a user, entering data where you tell it to and looking for the specified results. Protractor is a bit more complicated than just writing some Jasmine, but the results are worth it. Like Karma, you can run Protractor from within most any IDE that is capable of running external scripts or via the command line.
Yeoman is a process management system that incorporates dependency management via Bower, task automation via Grunt, and project management via Yo. It will run your tests in Karma and Protractor, minify your JS, CSS, and HTML, compile everything into appropriate files (internal JS, external libraries, and CSS) and provide you with a complete package that can be deployed. The beauty of Yeoman is that it is not specific to any one IDE. Everything it does can be done by scripting in your IDE or via the command line.
Now, having said all of this about Yeoman, you do still have to write the tests (it won't magically come up with them for you) and learn to integrate it into your development routine, but it is definitely the way to go for JS development. Eclipse is fine for JS development, but you'll get better performance and ease of use (IMHO) from WebStorm.
As for how these all fit into CI like Jenkins, I believe that both Karma and Protractor output test results in a format that Jenkins can read and display. With the scripting possibilities in Jenkins you can configure it to run the build process each time your source control repository (you are using some sort of source control, aren't you?) changes and show those results on the Jenkins page. My office has a very similar setup and we use it daily. I'm not the guy that has to do the Jenkins configuration, but I do work with Yeoman (and thus Karma and Protractor) via WebStorm on a regular basis and have had very good results.
I would say the clear choice here is Karma and Protractor. While it is true that they rely on a bunch of other stuff, they do so pretty antiseptically: protractor starts up the selenium server and then shuts it off when it's done. Once you have node installed, the other installations are all super simple. I would also install httpster, which will serve up your public director on port 3333.
Frankly, having come from a decade of doing TDD in the Java world, when I first looked at Javascript a few years ago (again), the testing picture was a complete joke. But now, I think the combination of Karma and Protractor is pretty fantastic. Inside IntelliJ, you can run the Karma tests and they are stupid fast and the results are presented in a runner that's as good as anything I've seen in the Java world (Xcode 5 has the best test integration). You can also install the ddescribe plugin in IntelliJ and have a ui for running individual tests or excluding tests.
On the protractor side, I found this post because I am at the point now where I am going to run my karma, protractor and then JUnit tests on a continuous integration server (either Jenkins or TeamCity). I was kind of surprised at the paucity of info on that leg of the trip, but the clear direction I see there is Grunt, because it will run your protractor tests then generate the JUnit-style output Jenkins wants. Grunt is also a pretty impressive addition to the JS world.
I know this sounds like a bunch of opinions, but I think that as happened in the Java world, the Javascript world has now reached that level of maturity where you are just going to have to expect things to drag other things in with them. Frankly, looks like node and npm do a pretty nice job of making that pretty seamless (vs. a decade down the drain on Maven in the Java world).
Updated: Sorry I did not read your question properly.
karma is a test runner, which is best suited for jasmine. For setting up is very very easy. Please download node, and install npm install karma. Follow the angular seed sandbox project it contains all the basic config set up for unit testing and end to end testing (in config folder).all you need is nodejs plugin installed in eclipse
Yeoman can be used for javascript minification, sass compilation e.t.c.
Install node eclipse and you can set all up in eclipse.
http://www.nodeclipse.org/