Release notes
*Sourced from [junit's releases](https://github.com/junit-team/junit/releases).*
> ## JUnit 4.12
> Please refer to the [release notes](https://github.com/junit-team/junit/blob/master/doc/ReleaseNotes4.12.md) for details.
>
> ## JUnit 4.12 Beta 3
> Please refer to the [release notes](https://github.com/junit-team/junit/blob/master/doc/ReleaseNotes4.12.md) for details.
>
> ## JUnit 4.12 Beta 2
> No release notes provided.
>
> ## JUnit 4.12 Beta 1
> No release notes provided.
>
> ## JUnit 4.11
> No release notes provided.
Changelog
*Sourced from [junit's changelog](https://github.com/junit-team/junit4/blob/master/doc/ReleaseNotes4.12.md).*
> ## Summary of changes in version 4.12
>
> # Assertions
>
> ### [Pull request [#611](https://github-redirect.dependabot.com/junit-team/junit/issues/611):](https://github-redirect.dependabot.com/junit-team/junit4/pull/611) Assert.assertNotEquals() for `float` parameters
>
> Version 4.11 added `Assert.assertEquals()` for `float` parameters with a delta, and `Assert.assertNotEquals()`. This is the combination of those two features.
>
>
> ### [Pull request [#632](https://github-redirect.dependabot.com/junit-team/junit/issues/632):](https://github-redirect.dependabot.com/junit-team/junit4/pull/632) Assert.assertArrayEquals() for `boolean[]` parameters.
>
> `Assert.assertArrayEquals()` previously existed for all primitive array types, except `boolean[]`. This has now been added for `boolean[]`.
>
>
> ### [Pull request [#918](https://github-redirect.dependabot.com/junit-team/junit/issues/918):](https://github-redirect.dependabot.com/junit-team/junit4/pull/918) Avoid potentially expensive reflection-based loop in Assert.assertArrayEquals()
>
> In the usual case, where the array elements are in fact exactly equal, the potentially expensive reflection-based loop to compare them is avoided by using `Arrays.deepEquals()` first. The exact comparison is only executed when `deepEquals()` returns `false`.
>
>
> # Command-line options
> ### [Pull request [#647](https://github-redirect.dependabot.com/junit-team/junit/issues/647):](https://github-redirect.dependabot.com/junit-team/junit4/pull/647) Support command-line `--filter` param.
>
> When running JUnit from the command line, a command-line parameter can be supplied using `--filter`, which supplies a filter that will restrict which tests and subtests from the rest of the command will be run. For example, this will run only the tests in ExampleTestSuite that are in categories Cat1 or Cat2:
>
> ```
> java org.junit.runner.JUnitCore \
> --filter=org.junit.experimental.categories.IncludeCategories=pkg.of.Cat1,pkg.of.Cat2 \
> com.example.ExampleTestSuite
> ```
>
> In general, the argument to `--filter` should be `ClassName=param`, where `ClassName` names an implementation of `FilterFactory`, whose `createFilter` method will be called with an instance of `FilterFactoryParams` that contains `"param"`, in order to return the filter to be applied.
>
> # Test Runners
>
>
> ### [Pull request [#763](https://github-redirect.dependabot.com/junit-team/junit/issues/763):](https://github-redirect.dependabot.com/junit-team/junit4/pull/763) Allow custom test runners to create their own TestClasses and customize the scanning of annotations.
>
> This introduces some extension points to `ParentRunner` to allow subclasses to control creation
> of the `TestClass` instance and to scan for annotations.
>
> ### [Pull request [#817](https://github-redirect.dependabot.com/junit-team/junit/issues/817):](https://github-redirect.dependabot.com/junit-team/junit4/pull/817) Support for context hierarchies
>
> The `AnnotatedBuilder` is a strategy for constructing runners for test classes that have been annotated with the `[@RunWith](https://github.com/RunWith)` annotation. All tests within such a class will be executed using the runner that was specified within the annotation.
>
> Prior to JUnit 4.12, this covered only the tests within the annotated test class. With 4.12, the `AnnotationBuilder` will also support inner member classes. If a custom test runner supports inner member classes (which JUnit does not support out-of-the-box), the member classes will inherit the runner from the enclosing class, e.g.:
>
> ```java
> [@RunWith](https://github.com/RunWith)(MyRunner.class)
> public class MyTest {
> // some tests might go here
> ... (truncated)
Commits
- See full diff in [compare view](https://github.com/junit-team/junit/commits/r4.12)
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Note: This repo was added to Dependabot recently, so you'll receive a maximum of 5 PRs for your first few update runs. Once an update run creates fewer than 5 PRs we'll remove that limit.
You can always request more updates by clicking Bump now in your Dependabot dashboard.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot ignore this [patch|minor|major] version` will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
- `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language
- `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language
- `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language
- `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language
- `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme
Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com):
- Update frequency (including time of day and day of week)
- Automerge options (never/patch/minor, and dev/runtime dependencies)
- Pull request limits (per update run and/or open at any time)
- Out-of-range updates (receive only lockfile updates, if desired)
- Security updates (receive only security updates, if desired)
Finally, you can contact us by mentioning @dependabot.
Bumps junit from 3.8.1 to 4.12.
Release notes
*Sourced from [junit's releases](https://github.com/junit-team/junit/releases).* > ## JUnit 4.12 > Please refer to the [release notes](https://github.com/junit-team/junit/blob/master/doc/ReleaseNotes4.12.md) for details. > > ## JUnit 4.12 Beta 3 > Please refer to the [release notes](https://github.com/junit-team/junit/blob/master/doc/ReleaseNotes4.12.md) for details. > > ## JUnit 4.12 Beta 2 > No release notes provided. > > ## JUnit 4.12 Beta 1 > No release notes provided. > > ## JUnit 4.11 > No release notes provided.Changelog
*Sourced from [junit's changelog](https://github.com/junit-team/junit4/blob/master/doc/ReleaseNotes4.12.md).* > ## Summary of changes in version 4.12 > > # Assertions > > ### [Pull request [#611](https://github-redirect.dependabot.com/junit-team/junit/issues/611):](https://github-redirect.dependabot.com/junit-team/junit4/pull/611) Assert.assertNotEquals() for `float` parameters > > Version 4.11 added `Assert.assertEquals()` for `float` parameters with a delta, and `Assert.assertNotEquals()`. This is the combination of those two features. > > > ### [Pull request [#632](https://github-redirect.dependabot.com/junit-team/junit/issues/632):](https://github-redirect.dependabot.com/junit-team/junit4/pull/632) Assert.assertArrayEquals() for `boolean[]` parameters. > > `Assert.assertArrayEquals()` previously existed for all primitive array types, except `boolean[]`. This has now been added for `boolean[]`. > > > ### [Pull request [#918](https://github-redirect.dependabot.com/junit-team/junit/issues/918):](https://github-redirect.dependabot.com/junit-team/junit4/pull/918) Avoid potentially expensive reflection-based loop in Assert.assertArrayEquals() > > In the usual case, where the array elements are in fact exactly equal, the potentially expensive reflection-based loop to compare them is avoided by using `Arrays.deepEquals()` first. The exact comparison is only executed when `deepEquals()` returns `false`. > > > # Command-line options > ### [Pull request [#647](https://github-redirect.dependabot.com/junit-team/junit/issues/647):](https://github-redirect.dependabot.com/junit-team/junit4/pull/647) Support command-line `--filter` param. > > When running JUnit from the command line, a command-line parameter can be supplied using `--filter`, which supplies a filter that will restrict which tests and subtests from the rest of the command will be run. For example, this will run only the tests in ExampleTestSuite that are in categories Cat1 or Cat2: > > ``` > java org.junit.runner.JUnitCore \ > --filter=org.junit.experimental.categories.IncludeCategories=pkg.of.Cat1,pkg.of.Cat2 \ > com.example.ExampleTestSuite > ``` > > In general, the argument to `--filter` should be `ClassName=param`, where `ClassName` names an implementation of `FilterFactory`, whose `createFilter` method will be called with an instance of `FilterFactoryParams` that contains `"param"`, in order to return the filter to be applied. > > # Test Runners > > > ### [Pull request [#763](https://github-redirect.dependabot.com/junit-team/junit/issues/763):](https://github-redirect.dependabot.com/junit-team/junit4/pull/763) Allow custom test runners to create their own TestClasses and customize the scanning of annotations. > > This introduces some extension points to `ParentRunner` to allow subclasses to control creation > of the `TestClass` instance and to scan for annotations. > > ### [Pull request [#817](https://github-redirect.dependabot.com/junit-team/junit/issues/817):](https://github-redirect.dependabot.com/junit-team/junit4/pull/817) Support for context hierarchies > > The `AnnotatedBuilder` is a strategy for constructing runners for test classes that have been annotated with the `[@RunWith](https://github.com/RunWith)` annotation. All tests within such a class will be executed using the runner that was specified within the annotation. > > Prior to JUnit 4.12, this covered only the tests within the annotated test class. With 4.12, the `AnnotationBuilder` will also support inner member classes. If a custom test runner supports inner member classes (which JUnit does not support out-of-the-box), the member classes will inherit the runner from the enclosing class, e.g.: > > ```java > [@RunWith](https://github.com/RunWith)(MyRunner.class) > public class MyTest { > // some tests might go here > ... (truncated)Commits
- See full diff in [compare view](https://github.com/junit-team/junit/commits/r4.12)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Note: This repo was added to Dependabot recently, so you'll receive a maximum of 5 PRs for your first few update runs. Once an update run creates fewer than 5 PRs we'll remove that limit.
You can always request more updates by clicking
Bump nowin your Dependabot dashboard.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot ignore this [patch|minor|major] version` will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Automerge options (never/patch/minor, and dev/runtime dependencies) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired) Finally, you can contact us by mentioning @dependabot.