blocks|key|1412090|text|后缀的另一个论点-至少在英语中是这样的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1412091|一个类通常代表一个名词，它是一个概念的模型。其中一个测试的实例将是“MyClass测试”。相反，一个方法会对某种动作进行建模，比如“测试计算方法”。|1412092|正因为如此，我总是对测试类使用‘后缀’，对测试方法使用前缀：|1412093|the+MyClass+test++++++++++-->+MyClassTest
test+the+calculate+method+-->+testCalculate()|code-block|syntax|javascript|1412094|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|O|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|P|8|@]|9|@]|A|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

Another argument for suffix - at least in english language:

A class usually represents a noun, it is a model of a concept. An instance of one of your tests would be a 'MyClass test'. In contrast, a method would model some kind of action, like 'test [the] calculate [method]'.

Because of this, I'd always use the 'suffix' for test classes and the prefix for test methods:

<pre><code>the MyClass test --&gt; MyClassTest
test the calculate method --&gt; testCalculate()
</code></pre>

blocks|key|669348|text|我更喜欢使用后缀-这意味着查找目录中的文件列表更简单:您不必在头脑中忽略前四个字母来获得有意义的内容。(我假设您已经将测试放在与生产代码不同的目录中。)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|669349|这也意味着当您在Eclipse中使用Open+Type+(Ctrl-T)时，您最终会同时看到产品代码及其测试……如果您看不到测试类，这也是一个提醒:)|669350|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I prefer to use the suffix - it means that looking down the list of files in a directory is simpler: you don't have to mentally ignore the first four letters to get to something meaningful. (I'm assuming you have the tests in a different directory to the production code already.)

It also means that when you use Open Type (Ctrl-T) in Eclipse, you end up seeing both the production code and its test at the same time... which is also a reminder if you don't see a test class :)

blocks|key|1416248|text|在JUnit+4之前，通常将测试类命名为SomethingTest，然后对所有匹配*Test.java的类运行JUnit。如今，注释驱动的JUnit+4，你只需要用@Test注释你的测试方法就可以了。您的测试类可能会位于与实际源代码(test/中的src/测试类中的源代码)不同的目录结构中，所以现在前缀/后缀在很大程度上是无关紧要的。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1416249|entityMap^0|15|A|2A|5|39|5|3G|4|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]|$9|O|A|P|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|G|$]]

Prior to JUnit 4 it was common to name your test classes SomethingTest and then run JUnit across all classes matching <code>*Test.java</code>. These days annotation driven JUnit 4, you just need to annotate your test methods with <code>@Test</code> and be done with it. Your test classes are probably going to be under a different directory structure than your actual source (source in <code>src/</code> test classes in <code>test/</code>) so these days prefixes/suffixes are largely irrelevant.

blocks|key|3708846|text|无意冒犯任何人，但我认为公平地说，"moreunit“比JUnit少得多，它几乎无处不在，并建立了为测试类添加后缀"+test”的约定。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3708847|尽管JUnit4取消了同时遵循类和方法命名约定的必要性(resp。“后缀测试”和“前缀测试”)，我认为为了清晰起见，这两种测试仍然有用。|3708848|想象一下由src/main/java/.../MyClass.myMethod()测试src/test/java/.../MyClass.myMethod()是多么恐怖……|3708849|有时，背离JUnit3约定是很有用的--我发现以设置方法的功能命名它们("createTestFactory()")并将其注释为"@Before“要比泛型的"+setup+()”清晰得多。|3708850|当需要执行几个不相关的设置操作时，这特别有用-它们可以在不同的方法中，每个方法都标记为@Before。这很好地传达了动作的独立性。|3708851|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

Not to offend anybody, but I think it is fair to say that "moreunit" is much less known than JUnit, which is pretty much ubiquitous, and established the convention of suffixing test classes "Test".

Although JUnit4 did away with the necessity of following both class and method naming conventions (resp. "postfix Test" and "prefix test"), I think both are still useful for clarity.

Imagine the horror of having src/test/java/.../MyClass.myMethod() tested by src/main/java/.../MyClass.myMethod()...

Sometimes, it is useful to diverge from the JUnit3 conventions - I find that naming setup methods after what they do ("createTestFactory()") and annotating them "@Before" is much clearer than the generic "setUp()".

This is particularly useful when several unrelated setup actions need to be performed - they can be in separate methods, each tagged @Before. This communicates the independence of the actions very nicely.

blocks|key|2301552|text|我更喜欢使用TestClassName语法。在使用另一种语法时，我很难在编辑器中辨别出哪个是测试，哪个是实际的类，因为两者都打开了。必须查找名称中的最后四个字母是令人厌烦的，而且这些字母并不总是显示。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2301553|对我来说，另一种语法导致每天在文件之间进行几次错误的交换，这很耗时。|2301554|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I prefer using the TestClassName syntax. When using the other syntax I have trouble identifying which is the test and which is the actual class in editors when I have both open. Having to look for the Last four letters in the name is tiresome and also these letters are not always displayed. 

For me the other syntax leads to several wrong swapping´s between files every day and that is time consuming.

blocks|key|669474|text|我认为如果你单独工作，你对你的测试感到舒适是很重要的。但是如果你在一个小组里，你最好坐下来把一些东西修好。我个人倾向于对类使用后缀，对方法使用前缀，并尝试让我的团队适应这种约定。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|669475|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I think it is important you feel comfortable with your tests if you are working alone. But if you're in a group, you better sit down and get something fixed. I personally tend to use suffix for classes and prefix for methods and try to have my groups adapt to this convention.

blocks|key|669439|text|当我想将我的测试分成多个类时，我也会使用MyClassTest_XXX。当测试一个大的类并且我希望测试逻辑分组时，这是有用的。(无法控制遗留代码，因此会出现这种情况。)然后我有像KitchenSinkTest_ForArray，KitchSinkTest_ForCollection之类的东西。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|669440|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I also use MyClassTest_XXX when I want to split my test into multiple classes. This is useful when testing a big class and I want the tests logically grouped. (Can't control legacy code so this scenario does come up.) Then I have something like KitchenSinkTest_ForArray, KitchSinkTest_ForCollection, etc.

blocks|key|667748|text|我建议使用MyClassTests。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|667749|类应该是名词短语，所以常用的MyClassTest和不常用的MyClassTests、MyClassTestCase或MyClassTestFixture都可以。从技术上讲，JUnit测试类的一个实例表示一个test+fixture，但是TestFixture对我来说有点太冗长了。|667750|我认为MyClassTests以最好的方式传达了意图，因为一个类中通常有多个测试方法，每个方法代表一个测试(测试用例)。|667751|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/junit-team/junit4/wiki/Test-fixtures^0|5|C|0|E|B|U|C|17|F|1N|I|3B|B|2W|C|0|0|3|C|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]|$9|Z|A|10|B|C]|$9|11|A|12|B|C]|$9|13|A|14|B|C]]|D|@$9|15|A|16|1|17]]|E|$]]|$1|H|3|I|5|6|7|18|8|@$9|19|A|1A|B|C]]|D|@]|E|$]]|$1|J|3|-4|5|6|7|1B|8|@]|D|@]|E|$]]]|K|$L|$5|M|N|O|E|$P|Q]]]]

I suggest <code>MyClassTests</code>. 

Classes should be noun phrases, so commonly used <code>MyClassTest</code> and less common <code>MyClassTests</code> or <code>MyClassTestCase</code> or <code>MyClassTestFixture</code> all work. Technically, an instance of a JUnit test class represents a <a href="https://github.com/junit-team/junit4/wiki/Test-fixtures" rel="nofollow noreferrer">test fixture</a>, but <code>TestFixture</code> is a bit too verbose for me.

I think that <code>MyClassTests</code> conveys intent in the best way because there are typically multiple test methods in a class each representing a single test (test case).

blocks|key|3708888|text|我更喜欢后缀:+TestCase。这与：http://xunitpatterns.com/Testcase%2520Class.html一致|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3708889|entityMap|0|LINK|mutability|MUTABLE|url|http://xunitpatterns.com/Testcase%2520Class.html^0|K|1A|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

i prefer the suffix: TestCase. this is consistant with: <a href="http://xunitpatterns.com/Testcase%20Class.html" rel="nofollow noreferrer">http://xunitpatterns.com/Testcase%20Class.html</a>

Class under test MyClass.java
JUnit test case name alternatives: 

<pre><code>TestMyClass.java
MyClassTest.java
</code></pre>

<a href="http://moreunit.sourceforge.net" rel="noreferrer">http://moreunit.sourceforge.net</a> seems to use "Test" as prefix default but I have seen both uses. Both seems to be recognized when running the entire project as unit test in eclipse as it is the annotation inside classes that are parsed for @Test. I guess maven does the same thing. 

Which is preferred?

Naming convention JUnit suffix or prefix Test

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

被测类MyClass.java JUnit测试用例名称替代：TestMyClass.javaMyClassTest.java似乎默认使用"Test“作为前缀，但我看到这两种用法都有。当在eclipse中将整个项目作为单元测试运行时，这两者似乎都能被识别出来，因为它是为@Test解析的类中的注释。我猜maven也是这么做的。哪一个是首选的？

问命名约定JUnit后缀或前缀测试
EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问命名约定JUnit后缀或前缀测试EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问命名约定JUnit后缀或前缀测试
EN