v1.0.6: Version 1.0.6

New feature:

- Add support for "Tests" prefix/suffix

v1.0.5: Version 1.0.5

New feature:

- Support for using file extension to find test file

v1.0.4: Version 1.0.4

Bug fixes:

- [#2](https://github.com/MoreUnit/org.moreunit.intellij.plugin/issues/2):
  IllegalArgumentException when no more editor is open

v1.0.3: Version 1.0.3

New features:

- Jump to the last opened test file (respectively to the last opened production file)

v1.0.2: Version 1.0.2

New features:

- When "jumping", if several candidate destinations are found, those with same
  extension as origin file are proposed first in the displayed list.

Bug fixes:

- When "jumping", while several candidate destinations were found and a list was
  displayed to choose one of them, the first candidate was also opened at the
  same time. This is not the case anymore.

v1.0.1: Version 1.0.1

(This is the same content as temporary v0.0.4, but version number has been increased
so that it is greater than 1.0, and thus be proposed as an update to users using
MoreUnit4AppCode, which is replaced by this new plugin. Features of MoreUnit4AppCode
are still present, with additional ones.)

Features, including those of MoreUnit4AppCode:

- Works for all IntelliJ-based IDEs (AppCode, IDEA, PhpStorm, PyCharm, RubyMine, WebStorm, etc.)
- Jump form your production code to you test code, and vice-versa. To access the command:
    - From the main menu: "Navigate" > "Jump to Test" or "Jump to Test Subject".
    - From the contextual menu: "Go To" > "Jump to Test" or "Jump to Test Subject".
    - From the "Find Action..." pop-up window: "Jump to Test / Test Subject".
- Should several candidates be found, a list is displayed for selection.
- Supported naming patterns:
    - lower/upper CamelCase or word separated with hyphens, underscores or even spaces
    - "test", "spec" or "should" suffixes (case insensitive, except for CamelCase style)
    - "test" or "spec" prefixes (case insensitive, except for CamelCase style)
- Writing tests for your Java code in Scala? Your test code does not have to be written
  in the same language as you production code!

v0.0.4: Version 0.0.4

Same as v0.0.2 and v0.0.3, but fix plugin ID to replace existing MoreUnit4AppCode plugin.

Features:

- Works for all IntelliJ-based IDEs (AppCode, IDEA, PhpStorm, PyCharm, RubyMine, WebStorm, etc.)
- Jump form your production code to you test code, and vice-versa. To access the command:
    - From the main menu: "Navigate" > "Jump to Test" or "Jump to Test Subject".
    - From the contextual menu: "Go To" > "Jump to Test" or "Jump to Test Subject".
    - From the "Find Action..." pop-up window: "Jump to Test / Test Subject".
    - (It is advised to assign it a binding!)
- Should several candidates be found, a list is displayed for selection.
- Supported naming patterns:
    - lower/upper CamelCase or word separated with hyphens, underscores or even spaces
    - "test", "spec" or "should" suffixes (case insensitive, except for CamelCase style)
    - "test" or "spec" prefixes (case insensitive, except for CamelCase style)
- Writing tests for your Java code in Scala? Your test code does not have to be written in the same
  language as you production code!

v0.0.2: Version 0.0.2

Features:

- Works for all IntelliJ-based IDEs (AppCode, IDEA, PhpStorm, PyCharm, RubyMine, WebStorm, etc.)
- Jump form your production code to you test code, and vice-versa. To access the command:
    - From the main menu: "Navigate" > "Jump to Test" or "Jump to Test Subject".
    - From the contextual menu: "Go To" > "Jump to Test" or "Jump to Test Subject".
    - From the "Find Action..." pop-up window: "Jump to Test / Test Subject".
    - (It is advised to assign it a binding!)
- Should several candidates be found, a list is displayed for selection.
- Supported naming patterns:
    - lower/upper CamelCase or word separated with hyphens, underscores or even spaces
    - "test", "spec" or "should" suffixes (case insensitive, except for CamelCase style)
    - "test" or "spec" prefixes (case insensitive, except for CamelCase style)
- Writing tests for your Java code in Scala? Your test code does not have to be written in the same
  language as you production code!

v0.0.1

Tag to test deployment with Travis CI