Skip to content

@jiripudil jiripudil released this Jun 28, 2017

  • The Create Test dialog does not autoupdate the target namespace and directory if invoked from the directory context (#26)
  • Added some handy inspections that make sure all your tests are actually executed (#3, #32)
  • You can right-click a single test case file to run it (#23)
  • Added support for nette/tester@dev-master for the time being (#30)
  • Fixed: bootstrap relative path resolves correctly if the target directory does not exist (#25)
  • Fixed: comparison failure reporting was broken on Unix systems
Assets 3

@jiripudil jiripudil released this May 30, 2017 · 9 commits to master since this release

I know I said this release branch would be feature-frozen, but... well... not just yet. I'm far too excited about bringing the new features to be able to postpone them. Semver doesn't play well with the plugin's distribution channel anyway. Here they come:

  • In the project settings, you can configure the path to your bootstrap file; it is then automatically required in the created test files (see #20 for instructions if it does not work right away)
  • You can now right-click a single test method to run or debug it in isolation (#9)
  • Fixed: OutputHandler now recognizes and correctly parses the diff command generated on Windows (#21)
  • Fixed: OutputHandler no longer reports unsuccessful builds as "terminated" (#22)
Assets 3

@jiripudil jiripudil released this May 21, 2017 · 16 commits to master since this release

After tens of hours of work, here comes a total rework of the plugin. This beta.1 release marks the feature freeze, now I'd like to focus on fixing bugs and releasing a stable version soon.

  • Most importantly, the plugin no longer relies on a specific fork of nette/tester. As of 2.0.0, the plugin supports all 1.x versions of Nette Tester. Hooray!
  • You can navigate between the class and its test, or create a test case for a class easily. The navigation is based on convention (class name + Test suffix), the creation assumes your tests reside in the same namespace as the code; if you use a different scheme, you can configure source to test namespace mapping in the project settings under PHP > Nette Tester.
  • The plugin ships with a run configuration producer for directories, so you can right-click a directory and run the tests within it. For this to be truly one-click action, you should configure the Tester executable in the Nette Tester default run configuration template.
  • You can view the diff of comparison failures (Assert::same() and alike) right in the test results window.
  • Output stack traces are decorated with links to files, provided you set Tester\Dumper::$maxPathSegments to a high enough value in your test environment.

To support a wide range of Tester versions, I had to drop a few features. However, they should, in some form or another, be back once nette/tester#345 is resolved.

  • The plugin no longer groups TestCase methods in the test results window.
  • The plugin no longer lets you navigate to the tests from the test results window, nor run or debug them directly.

Please test this release and report any bugs in the issue tracker.

Assets 3
Pre-release
Pre-release

@jiripudil jiripudil released this Nov 29, 2016 · 31 commits to master since this release

Fixed compatibility with PhpStorm 2016.3 (thx @Komanc, #15)

Assets 3
Pre-release
Pre-release

@jiripudil jiripudil released this Oct 14, 2016 · 34 commits to master since this release

Fixed compatibility with PhpStorm 2016.3.

Assets 3
Pre-release
Pre-release

@jiripudil jiripudil released this Apr 20, 2016 · 38 commits to master since this release

Compatible with 2016.1

Assets 3
Pre-release
Pre-release

@jiripudil jiripudil released this Feb 28, 2016 · 40 commits to master since this release

Initial alpha version with basic capabilities:

  • Tester run configuration type and editor.
  • Displays results in the Test Runner window.
Assets 3
You can’t perform that action at this time.