Testacular (now Karma) - JavaScript Test Runner

Vojta J · 539K views · 2012 · 14:52

Open on YouTube

Testing, debugging & developer toolsWeb developmenttutorialdated

Why Stack Overflow recommends it

Stack Overflow users link it as the original getting-started walkthrough for Karma, including its WebStorm setup and debugging steps.

Recommended by 2 people across 2 different months, 2009 to 2014.

What it is

A 15-minute screencast by Vojta Jina, the author of the tool, showing how to install and use the Testacular (later renamed Karma) JavaScript test runner. It covers command-line use, WebStorm integration and debugging, using the AngularJS tutorial and source as example code.

What people said

Recommends karl li · 2013-02 · Stack Overflow · on “How to use testacular with play framework”

You can see video [this video] which tells you how to automatize testacular through your Project. And this [LINK] give you more information

Recommends Linial · 2014-11 · Stack Overflow · on “Angular JS unit testing tutorials with examples”

First of all, and most IMPORTANT: Unit-testing is similar in all other languages. You have to keep in mind the main features of writing testable code. Note: There is a good Pluralsight video ( Which cost money ) by Misko Hevery on Writing Testable Code). First: Watch this youtube by Vojta Jina - Installing and Starting Karma [this video] , the person who wrote karma. Second: Watch this 1 Hour tutorial which I highly recommand : Introduction to AngularJS Unit Testing By Jim Levin [LINK] After you complete those you should be able to test every piece of code in your Angular Project. Good Luck.

Cites gregers · 2009-03 · Stack Overflow · on “JavaScript unit test tools for TDD”

Karma [LINK] or Protractor [LINK] Karma is a JavaScript test-runner built with Node.js and meant for unit testing. The Protractor is for end-to-end testing and uses Selenium Web Driver to drive tests. Both have been made by the Angular team. You can use any assertion-library you want with either. Screencast: Karma Getting started [this video] related : Should I be using Protractor or Karma for my end-to-end testing? [LINK] Can Protractor and Karma be used together? [LINK] pros : Uses Node.js, so compatible with Win/OS X/Linux Run tests from a browser or headless with PhantomJS Run on multiple clients at once Option to launch, capture, and automatically shut down browsers Option to run server/clie

Cites Joel Pearson · 2013-01 · Stack Overflow · on “Webstorm Chrome Extension doesn't stay installed”

I followed Vojta's video about how to do debug angularjs in Webstorm. [this video] However, every time I stop the testacular server in webstorm. I have to reinstall the webstorm debug extension for chrome. Am I doing something wrong? Do I need to install it into some Chrome profile or something?

Cites Scott Silvi · 2013-05 · Stack Overflow · on “Logging/dumping data in JavaScript using AngularJS, Karma and Jasmine?”

So normally when I need to log data in JavaScript, I simply log it to the console via console.log("What I ate yesterday"); Today, I was watching a video [this video] on Karma/Jasmine unit testing for AngularJS, and Vojta Jína, the host, logged data using window.dump [this video] . What value does this form of logging provide over simply using console.log ? This article [LINK] , from MDN, talks about a dump function on window , but this is actually logging directly in my terminal window, where my tests are running. I also found an article in the docs on AngularJS [LINK] about how to dump , but I'm still not clear this is the kind of logging that Vojta Jina used in the initial video. I'm hoping somebody

Cites newz2000 · 2013-08 · Stack Overflow · on “When running a command in Intellij, how do I make filenames clickable in the output?”

I have a grunt task that I've configured in IntelliJ 11 (sadly can't upgrade to 12 yet). The output of the command contains filenames when there is a problem. I've basically followed the configuration example I saw in the Karma setup video at [this video] (instructions start at 7:39 but the feature is demonstrated at 10:40). I've created a new Node.js run configuration, put in the correct path to node, changed the path to the file to be grunt and then listed the Application parameters to be what they should. It runs fine. The output of my grunt task spits out filenames with absolute paths followed by a colon and a line number, just like in that example. I'm curious why my files aren't clickable t