blocks|key|1220662|text|大多数时候是这样做的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1220663|<SOME_DIR>/project/src/com/foo/Application.java
<SOME_DIR>/project/test/com/foo/ApplicationTest.java|code-block|syntax|javascript|1220664|因此，您可以将它们分开，并且仍然可以测试包/受保护的功能，因为测试在同一个包中。|1220665|你不能测试私有的东西，除非它自己在类中声明。|1220666|在交付时，您只需打包由src生成的.class，而不是测试。|offset|length|style|CODE|1220667|entityMap^0|0|0|0|0|H|6|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|@]|A|$]]|$1|I|3|J|5|6|7|V|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|W|8|@$M|X|N|Y|O|P]]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

Most of the times is done like this:

<pre><code>&lt;SOME_DIR&gt;/project/src/com/foo/Application.java
&lt;SOME_DIR&gt;/project/test/com/foo/ApplicationTest.java
</code></pre>

So, you keep them separated and you can still test the package/protected functionality because the test is in the same package.

You can't test private stuff, unless it is declared inside the class it self.

Upon delivery, you just pack the <code>.class</code> generated by src, not the tests

blocks|key|1220751|text|我建议遵循Apache+Software+Foundation's+standard+directory+structure，它会产生以下结果：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1220752|module/
++src/
++++main/
++++++java/
++++test/
++++++java/|code-block|syntax|javascript|1220753|这使测试与源代码分离，但在目录结构中处于同一级别。如果你通读Apache是如何定义它们的结构的，你会发现它也有助于划分其他的关注点，包括资源，配置文件，其他语言等。|1220754|此结构还允许单元测试测试被测单元的包和受保护级别的方法，假设您将测试用例放在与它们测试的包相同的包中。关于测试私有方法--我不会费心的。其他的东西，无论是公共的，包的，还是受保护的，都会调用它们，你应该能够获得完整的测试覆盖范围来测试这些东西。|1220755|顺便说一下，上面的链接指向Apache的标准构建工具Maven。他们的每个Java项目都符合这个标准，我遇到的每个用Maven构建的项目也是如此。|1220756|entityMap|0|LINK|mutability|MUTABLE|url|http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html^0|5|1L|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@$A|X|B|Y|1|Z]]|C|$]]|$1|D|3|E|5|F|7|10|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|11|8|@]|9|@]|C|$]]|$1|K|3|L|5|6|7|12|8|@]|9|@]|C|$]]|$1|M|3|N|5|6|7|13|8|@]|9|@]|C|$]]|$1|O|3|-4|5|6|7|14|8|@]|9|@]|C|$]]]|P|$Q|$5|R|S|T|C|$U|V]]]]

I recommend following the <a href="http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html" rel="noreferrer">Apache Software Foundation's standard directory structure</a>, which yields this:

<pre><code>module/
 src/
 main/
 java/
 test/
 java/
</code></pre>

This keeps tests separate from source, but at the same level in the directory structure. If you read through how Apache defines their structure, you'll see it helps partition other concerns out as well, including resources, config files, other languages, etc.

This structure also allows unit tests to test package and protected level methods of the units under test, assuming you place your test cases in the same package as what they test. Regarding testing private methods - I would not bother. Something else, either public, package, or protected calls them and you should be able to get full test coverage testing those things.

By the way, the link above is to Maven, Apache's standard build tool. Every Java project they have conforms to this standard, as well as every project I have encountered that is built with Maven.

blocks|key|1220786|text|实际上，将你的生产和测试项目分成两个独立的实体是很有意义的，但在两个项目中具有相同的包结构。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1220787|因此，如果我有一个项目'my-+project‘，我还创建了'my-project-test'，所以我有以下目录结构：|1220788|my-project
++%2B---+src/com/foo
my-project-test
++%2B---test/com/foo|code-block|syntax|javascript|1220789|此方法可确保测试代码依赖项不会污染生产代码。|1220790|在我个人看来，包的私有和受保护的方法应该像公共方法一样进行测试。因此，我希望我的测试类与生产类位于同一个包中。|1220791|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

Actually it makes a lot of sense to separate your Production and Test projects into 2 separate entities, but have the same package structure in both projects.

So if I have a project 'my-project' I also create 'my-project-test', so I have the following directory structure:

<pre><code>my-project
 +--- src/com/foo
my-project-test
 +---test/com/foo
</code></pre>

This approach ensures that test code dependencies do not pollute production code.

In my personal opinion, package private and protected methods should be tested as well as public methods. Hence I want my test classes in the same package as production classes.

blocks|key|1435858|text|这就是我们设置它的方式，我们喜欢它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1435859|build/
src/
test/build/
test/src/|code-block|syntax|javascript|1435860|所有测试代码都编译到自己的构建目录中。这是因为我们不想让产品错误地包含测试类。|1435861|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|$]]

This is how we have it set up and we like it.

<pre><code>build/
src/
test/build/
test/src/
</code></pre>

All testing code compiles into its own build directory. This is because we don't want production to contain test classes by mistake.

When building a suite of unit tests for Java code, is there a convention for where to place test code in relation to source code?

For example, if I have a directory <code>/java</code> that contains a bunch of <code>.java</code> source files, is it better to put the test cases in <code>/java</code> itself or use something like <code>/java/test</code>.

If the latter is preferred, how do you test the internals of the code when the <code>private</code> /<code>protected</code> members of a class aren't available outside the package?

Java unit tests, directory layout

单元测试

Java

在为Java代码构建一套单元测试时，是否有关于将测试代码放在与源代码相关的位置的约定？例如，如果我有一个包含一堆.java源文件的目录/java，那么将测试用例放在/java本身中还是使用/java/test之类的内容更好？如果选择后者，那么当类的private /protected成员在包之外不可用时，如何测试代码的...

问Java单元测试，目录布局
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Java单元测试，目录布局EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Java单元测试，目录布局
EN