Since version 3.7, PHPUnit allows us to install the test runner and optional dependencies using Composer. With PhpStorm 6, this workflow is now supported from the IDE. Using both the bundled Composer support and PhpStorm’s unit testing support, we can install PHPUnit via Composer without any hassle. Let’s find out how. (more…)

CakePHP2 comes with unit testing support powered by PHPUnit. In addition to the features offered by PHPUnit, CakePHP offers some additional features to make testing easier. Unit tests in CakePHP rely on a custom test runner which can be run in the browser or using the CakePHP console. More information on unit testing with CakePHP can be found on their website. One issue with CakePHP unit tests is that they rely on the CakePHP test runner. This means that running them directly from PhpStorm is not supported out of the box. Which does not mean it’s impossible! Let’s see if we can get CakePHP

If you have multiple team members, you should be doing Continuous Integration (CI). By building the desired output artifacts on a frequent basis and analyzing their quality using unit tests and code coverage, you will find that there are fewer integration problems in working on a software project. In this blog post, we’ll be using the open-source PHP project PHPExcel as a sample project to set up Continuous Integration using TeamCity. This project features a large amount of code, PHPUnit tests and uses Phing to create build artifacts. We’ll use TeamCity to get this process completely automa

Recently, we received a question on Twitter asking about how PhpStorm handles type inference when working with mocking frameworks. Imagine having the following two classes: When writing a unit test for ClassA, it’s very easy to mock ClassB using PHPUnit’s mocking capabilities. By mocking ClassB, you can mold an instance of ClassB and add additional validations on it without having to modify the code for ClassB. For example, you might want to validate that there’s only one call being made to ClassB’s bar() method. (more…)

Measuring JavaScript code coverage naturally complements unit testing. It provides a clear picture of which parts of your code remain untested, and helps you focus additional tests on the uncovered code. From now on, users of JsTestDriver can measure code coverage visually, right in the editor. (more…)

Hello everybody, As you know Node.js support has been already presented in WebStorm 3.0. Now we would like to introduce integration with nodeunit -- unit testing framework for Node.js. To start you should have nodeunit module installed. Make sure NODE_PATH environment variable points to the parent directory of nodeunit module. To run tests first you need to create Nodeunit Run Configuration: Open Run/Debug Configurations dialog (Main menu | Run | Edit Configurations) Press icon and select Nodeunit Next fill Node path and Working Directory as you usually do in NodeJS Run Con

If you're a JavaScript developer, you probably know that the quality and correctness of your application are crucial. Well, consistency and regression testing just got a little less painful. Meet JsTestDriver plugin - an open-source project that was originally started at Google and is now contributed to by the JetBrains team. WebStorm 3.0 bundles it. Users of other JetBrains IDE - PhpStorm, IntelliJ IDEA, PyCharm, RubyMine, and AppCode - can install it from the plugin repository following these instructions. It allows you to enjoy all the benefits of JsTestDriver right from the com