blocks|key|227737|text|这并不完全是您想要的，但是您可以提供对任何assert方法的描述。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|227738|类似于：|227739|@Test
public+void+testTrue()+{
++++assertTrue("Testing+if+true+holds",+true);
}|code-block|syntax|javascript|227740|entityMap^0|L|6|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|R|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|S|8|@]|D|@]|E|$K|L]]|$1|M|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|N|$]]

Not exactly what you are looking for, but you can provide a description on any <code>assert</code> methods.

Something like:

<pre><code>@Test
public void testTrue() {
 assertTrue("Testing if true holds", true);
}
</code></pre>

blocks|key|445828|text|您可以根据测试来命名测试方法：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|445829|public+void+testThatOnePlusOneEqualsTwo()+{
++assertEquals(2,+1+%2B+1);
}|code-block|syntax|javascript|445830|这将在Eclipse、Surefire和大多数其他runners中显示出来。|445831|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

You can name the test method after the test:

<pre><code>public void testThatOnePlusOneEqualsTwo() {
 assertEquals(2, 1 + 1);
}
</code></pre>

This will show up in Eclipse, Surefire, and most other runners.

blocks|key|445859|text|TestNG是这样做的，对我来说这是最好的解决方案：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|445860|@Test(description="My+funky+test")++
public+void+testFunk()+{++
++++...++
}++|code-block|syntax|javascript|445861|有关详细信息，请参阅http://testng.org/javadocs/org/testng/annotations/Test.html。|offset|length|445862|entityMap|0|LINK|mutability|MUTABLE|url|http://testng.org/javadocs/org/testng/annotations/Test.html^0|0|0|A|1N|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@$I|V|J|W|1|X]]|A|$]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]]]

TestNG does it like this, which to me is the neatest solution:

<pre><code>@Test(description="My funky test") 
public void testFunk() { 
 ... 
} 
</code></pre>

See <a href="http://testng.org/javadocs/org/testng/annotations/Test.html" rel="noreferrer">http://testng.org/javadocs/org/testng/annotations/Test.html</a> for more information.

blocks|key|227856|text|在JUnit中测试时，我更喜欢遵循标准格式。测试的名称将是|type|unstyled|depth|inlineStyleRanges|entityRanges|data|227857|test[method+name]_[condition]_[outcome]|code-block|syntax|javascript|227858|例如：|227859|+@Test
+public+void+testCreateObject_nullField_errorMessage(){}

+@Test
+public+void+testCreateObject_validObject_objectCreated(){}|227860|我认为这种方法在进行TDD时很有帮助，因为您可以开始编写所有的测试名称，这样您就知道需要测试/开发什么。|227861|尽管如此，我还是欢迎来自JUnit的测试描述功能。|227862|这肯定比我过去见过的其他测试更好，比如：|227863|@Test+public+void+testCreateObject1(){}
@Test+public+void+testCreateObject2(){}
@Test+public+void+testCreateObject3(){}|227864|或|227865|@Test+public+void+testCreateObjectWithNullFirstNameAndSecondNameTooLong(){}|227866|entityMap^0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|10|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|12|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|13|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|14|8|@]|9|@]|A|$]]|$1|Q|3|R|5|D|7|15|8|@]|9|@]|A|$E|F]]|$1|S|3|T|5|6|7|16|8|@]|9|@]|A|$]]|$1|U|3|V|5|D|7|17|8|@]|9|@]|A|$E|F]]|$1|W|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|X|$]]

I prefer to follow a standard format when testing in JUnit. The name of the test would be

<pre><code>test[method name]_[condition]_[outcome]
</code></pre>

for Example:

<pre><code> @Test
 public void testCreateObject_nullField_errorMessage(){}

 @Test
 public void testCreateObject_validObject_objectCreated(){}
</code></pre>

I think this approach is helpful when doing TDD, because you can just start writing all the test names, so you know what you need to test / develop.

Still I would welcome a test description functionality from JUnit.

And this is certainly better than other tests I have seen in the past like:

<pre><code>@Test public void testCreateObject1(){}
@Test public void testCreateObject2(){}
@Test public void testCreateObject3(){}
</code></pre>

or 

<pre><code>@Test public void testCreateObjectWithNullFirstNameAndSecondNameTooLong(){}
</code></pre>

Is it possible in JUnit to add a brief description of the test for the future reader (e.g. what's being tested, some short explanation, expected result, ...)? I mean something like in ScalaTest, where I can write:

<pre><code>test("Testing if true holds") {
 assert(true)
}
</code></pre>

Ideal approach would be using some annotation, e.g.

<pre><code>@Test
@TestDescription("Testing if true holds")
public void testTrue() {
 assert(true);
}
</code></pre>

Therefore, if I run such annotated tests using Maven (or some similar tool), I could have similar output to the one I have in SBT when using ScalaTest:

<pre><code>- Testing if entity gets saved correctly
- Testing if saving fails when field Name is not specified
- ...
</code></pre>

Currently I can either use terribly long method names or write javadoc comments, which are 
not present in the build output.

Thank you.

JUnit test description

Eclipse

是否可以在JUnit中为将来的读者添加测试的简要描述(例如，正在测试的内容，一些简短的解释，预期的结果，等等)？我的意思是在ScalaTest中，我可以这样写：test("Testing if true holds") {  assert(true)}理想的方法是使用一些注释，例如@Test@TestDescripti...

问JUnit测试描述
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问JUnit测试描述EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问JUnit测试描述
EN