{"id":25871,"date":"2017-07-26T07:57:22","date_gmt":"2017-07-26T07:57:22","guid":{"rendered":"https:\/\/blog.jetbrains.com\/idea\/?p=15576"},"modified":"2017-08-01T13:12:47","modified_gmt":"2017-08-01T13:12:47","slug":"support-for-junit-5-in-intellij-idea-2017-2","status":"publish","type":"idea","link":"https:\/\/blog.jetbrains.com\/pt-br\/idea\/2017\/07\/support-for-junit-5-in-intellij-idea-2017-2","title":{"rendered":"Support for JUnit 5 M4 in IntelliJ IDEA 2017.2"},"content":{"rendered":"

IntelliJ IDEA provides support for the upcoming JUnit 5<\/a> release. JUnit has pretty much been the standard for Java unit testing for years, and the latest version brings the library right up to date, making use of Java 8 features and bringing in ways of testing that are familiar if you’ve been using other frameworks like Spock.\u00a0 IntelliJ IDEA 2017.2 adds support for some of these features, to make the experience of testing code as painless and quick as possible.<\/p>\n

JUnit 5 supports parameterized tests<\/a>. These tests let you use the same basic structure of a test with a number of different inputs. This reduces duplication in your test code and also lets you easily add new cases without having to create entire new tests.<\/p>\n

IntelliJ IDEA helps you with parameterized tests in a number of different ways,\u00a0 Firstly, it reports “suspicious” use of both @Test<\/code> and @ParameterizedTest<\/code> annotations – you only need one of these in order to declare the method is a test.<\/p>\n

\"Suspicious<\/p>\n

If you press Alt + Enter on the highlighted @Test<\/code> annotation, IntelliJ IDEA suggests removing this unnecessary annotation.<\/p>\n

\"Remove<\/a><\/p>\n

If you’re using the @ParameterizedTest<\/code> annotation, you need to supply a source for the parameters, otherwise there are no tests to run.\u00a0 IntelliJ IDEA warns you if you use the @ParameterizedTest<\/code> annotation without an associated source (annotations like @MethodSource<\/code>, @ValueSource<\/code> etc.)<\/p>\n

\"No<\/a><\/p>\n

If you’re using a source annotation, but it doesn\u2019t match the expectations set by the\u00a0 test method, you’ll also get a warning about this.\u00a0 For example, if you use a @ValueSource<\/code> that defines a series of ints as the input, but your test method takes a String parameter, IntelliJ IDEA will warn you that these types don’t match<\/p>\n

\"Incorrect<\/a><\/p>\n

Using a @MethodSource<\/code>\u00a0lets you choose a method that returns a Stream<\/code> of values to use for parameters, and\u00a0IntelliJ IDEA offers suggestions of suitable methods<\/p>\n

\"Code<\/a><\/p>\n

If you select a method that does not provide the right values for the test method’s arguments, you’ll get a warning about this as well. Here, we\u2019ve given @MethodSource<\/code> a method that returns a Stream<\/code> of Strings<\/code>, but because our test takes more than one argument we should have chosen a method that returns a Stream<\/code> of Argument<\/code>s.<\/p>\n

\"Incorrect<\/a><\/p>\n

You’ll notice as well that when you provide a method to @MethodValue<\/code>, this method is not marked as unused because\u00a0IntelliJ IDEA recognises it’s used in the annotation.<\/p>\n

\"No<\/a><\/p>\n

In addition to this support for parameterized tests, you also get warnings for using the @Test<\/code> annotation with @RepeatedTest<\/code>.<\/p>\n

\"Help<\/a><\/p>\n

IntelliJ IDEA 2017.2 makes it simple to use all the features in JUnit 5, so that it’s easier and quicker to write effective tests.<\/p>\n","protected":false},"author":360,"featured_media":0,"comment_status":"open","ping_status":"open","template":"","categories":[808],"tags":[673,3014,207],"cross-post-tag":[],"acf":[],"_links":{"self":[{"href":"https:\/\/blog.jetbrains.com\/pt-br\/wp-json\/wp\/v2\/idea\/25871"}],"collection":[{"href":"https:\/\/blog.jetbrains.com\/pt-br\/wp-json\/wp\/v2\/idea"}],"about":[{"href":"https:\/\/blog.jetbrains.com\/pt-br\/wp-json\/wp\/v2\/types\/idea"}],"author":[{"embeddable":true,"href":"https:\/\/blog.jetbrains.com\/pt-br\/wp-json\/wp\/v2\/users\/360"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.jetbrains.com\/pt-br\/wp-json\/wp\/v2\/comments?post=25871"}],"version-history":[{"count":0,"href":"https:\/\/blog.jetbrains.com\/pt-br\/wp-json\/wp\/v2\/idea\/25871\/revisions"}],"wp:attachment":[{"href":"https:\/\/blog.jetbrains.com\/pt-br\/wp-json\/wp\/v2\/media?parent=25871"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.jetbrains.com\/pt-br\/wp-json\/wp\/v2\/categories?post=25871"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.jetbrains.com\/pt-br\/wp-json\/wp\/v2\/tags?post=25871"},{"taxonomy":"cross-post-tag","embeddable":true,"href":"https:\/\/blog.jetbrains.com\/pt-br\/wp-json\/wp\/v2\/cross-post-tag?post=25871"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}