Merge pull request #33 from matepek/development

Development

.gitattributes

@@ -0,0 +1,2 @@
+* text=auto
+CHANGELOG.md -diff

.github/ISSUE_TEMPLATE/bug_report.md

@@ -29,7 +29,7 @@ If applicable, add screenshots to help explain your problem.
 
 **Log**
 Attach log. (optional, Set: `catch2TestExplorer.logfile` and reproduce the bug.)
-_Warning_: Log probably contains file and test names too. Consider security conserns before attach!
+_Warning_: Log probably contains file and test names too. Consider security concerns before you attach it!
 
 **Additional context**
 Add any other context about the problem here.

CHANGELOG.md

@@ -7,6 +7,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [2.2.6]
+
+Stability improvements.
+
 ## [2.2.5] - 2018-12-04
 
 ### Fixed
@@ -58,10 +62,10 @@ Performance and stability improvements. Improved logging.
 ### Added
 
 - `catch2TestExplorer.debugBreakOnFailure` option. It is true by default.
-- 🤩 Change of test file (ex.:recompilation) triggers "**autorun**" feature.
+- Change of test file (ex.:recompilation) triggers "**autorun**" feature.
   (Right click on test/suite in text explorer -> Enable to enable autorun for the selected test/suite.)
   This basically means that the selected test/suite will run in case of any filesystem event related to the `executables` variable.
-  It can be really useful if one would like to run a test (or suite) automatically after recompiliation. 💙
+  It can be really useful if one would like to run a test (or suite) automatically after recompiliation.
 
 ### Fixed
 

README.md

@@ -107,17 +107,18 @@ See [here](https://code.visualstudio.com/docs/editor/debugging#_launch-configura
 
 Usable variables:
 
-| Variable name | Value meaning                                       | Type                    |
-| ------------- | --------------------------------------------------- | ----------------------- |
-| `${label}`    | The name of the test. Same as in the Test Explorer. | string                  |
-| `${exec}`     | The path of the executable.                         | string                  |
-| `${args}`     | The arguments for the executable.                   | string[]                |
-| `${cwd}`      | The current working directory for execution.        | string                  |
-| `${envObj}`   | The environment variables as object properties.     | { [prop: string]: any } |
+| Variable name   | Value meaning                                                | Type                    |
+| --------------- | ------------------------------------------------------------ | ----------------------- |
+| `${label}`      | The name of the test. Same as in the Test Explorer.          | string                  |
+| `${suitelabel}` | The name of parent suite test. Same as in the Test Explorer. | string                  |
+| `${exec}`       | The path of the executable.                                  | string                  |
+| `${args}`       | The arguments for the executable.                            | string[]                |
+| `${cwd}`        | The current working directory for execution.                 | string                  |
+| `${envObj}`     | The environment variables as object properties.              | { [prop: string]: any } |
 
 These variables will be substituted when a DebugConfiguration is created.
 
-Note that `name` and `request` are prefilled, so it is not necessary to set them.
+Note that `name` and `request` are filled, if they are undefined, so it is not necessary to set them.
 
 Example: