blocks|key|99721|text|最大的变化之一似乎是Android+Studio将测试应用程序集成到应用程序项目中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|99722|我不确定这是否对你的具体问题有帮助，但我找到了一个使用Gradle项目进行测试的指南。Android+Gradle+user+Guide|offset|length|99723|entityMap|0|LINK|mutability|MUTABLE|url|http://tools.android.com/tech-docs/new-build-system/user-guide#TOC-Testing^0|0|17|P|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

One of the major changes it seems is that with Android Studio the test application is integrated into the application project.

I'm not sure if this helps your specific problem, but I found a guide on making tests with a Gradle project.
<a href="http://tools.android.com/tech-docs/new-build-system/user-guide#TOC-Testing" rel="nofollow">Android Gradle user Guide</a>

blocks|key|99813|text|到目前为止(studio+0.61)，维护适当的项目结构就足够了。不需要像在eclipse中那样创建单独的测试项目(见下文)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|99814|​|99815|📷|atomic|offset|length|99816|99817|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/ffccf41fe9e69bffadfbc9cb6cff2aea.jpeg|imageAlt^0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@$G|V|H|W|1|X]]|A|$]]|$1|I|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q|R|-4]]]]

As of now (studio 0.61) maintaining proper project structure is enough.
No need to create separate test project as in eclipse (see below).

<img src="https://i.stack.imgur.com/Bctbs.jpg" alt="Tests structure">

blocks|key|99885|text|Android+Studio一直是一个移动的目标，首先是开发人员预览版，现在是测试版。项目中测试类的路径在一段时间内发生了变化，但无论您使用的是哪个版本的AS，都会在.iml文件中声明该路径。目前，在0.8.3版本中，您将在内部iml文件中找到以下内容：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|99886|++++++<sourceFolder+url="file://$MODULE_DIR$/src/androidTest/res"+type="java-test-resource"+/>
++<sourceFolder+url="file://$MODULE_DIR$/src/androidTest/resources"+type="java-test-resource"+/>
++<sourceFolder+url="file://$MODULE_DIR$/src/androidTest/assets"+type="java-test-resource"+/>
++<sourceFolder+url="file://$MODULE_DIR$/src/androidTest/aidl"+isTestSource="true"+/>
++<sourceFolder+url="file://$MODULE_DIR$/src/androidTest/java"+isTestSource="true"+/>
++<sourceFolder+url="file://$MODULE_DIR$/src/androidTest/groovy"+isTestSource="true"+/>
++<sourceFolder+url="file://$MODULE_DIR$/src/androidTest/jni"+isTestSource="true"+/>
++<sourceFolder+url="file://$MODULE_DIR$/src/androidTest/rs"+isTestSource="true"+/>|code-block|syntax|javascript|99887|.iml文件告诉您将测试类放在哪里。|99888|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|$]]

Android Studio has been kind of a moving target, first being a developer preview and now being in beta.
The path for the Test classes in the project has changed during time, but no matter what version of AS you are using, the path is declared in your .iml file. Currently, with version 0.8.3, you'll find the following inside the inner iml file:

<pre><code> &lt;sourceFolder url="file://$MODULE_DIR$/src/androidTest/res" type="java-test-resource" /&gt;
 &lt;sourceFolder url="file://$MODULE_DIR$/src/androidTest/resources" type="java-test-resource" /&gt;
 &lt;sourceFolder url="file://$MODULE_DIR$/src/androidTest/assets" type="java-test-resource" /&gt;
 &lt;sourceFolder url="file://$MODULE_DIR$/src/androidTest/aidl" isTestSource="true" /&gt;
 &lt;sourceFolder url="file://$MODULE_DIR$/src/androidTest/java" isTestSource="true" /&gt;
 &lt;sourceFolder url="file://$MODULE_DIR$/src/androidTest/groovy" isTestSource="true" /&gt;
 &lt;sourceFolder url="file://$MODULE_DIR$/src/androidTest/jni" isTestSource="true" /&gt;
 &lt;sourceFolder url="file://$MODULE_DIR$/src/androidTest/rs" isTestSource="true" /&gt;
</code></pre>

The .iml file is telling you where to place your test classes.

blocks|key|316909|text|从Android+Studio+1.1开始，我们已经获得了官方的(实验性的)支持来编写单元测试(Roboelectric也是如此)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|316910|来源：https://sites.google.com/a/android.com/tools/tech-docs/unit-testing-support|offset|length|316911|entityMap|0|LINK|mutability|MUTABLE|url|https://sites.google.com/a/android.com/tools/tech-docs/unit-testing-support^0|0|3|23|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

As of Android Studio 1.1, we've got official (experimental) support for writing Unit Tests (Roboelectric works as well).

Source: <a href="https://sites.google.com/a/android.com/tools/tech-docs/unit-testing-support" rel="nofollow">https://sites.google.com/a/android.com/tools/tech-docs/unit-testing-support</a>

blocks|key|99938|text|Android+Studio不断发展，因此上面的回应最终将不再适用。对于当前版本的Android+Studio+1.2.1.1，有一个关于测试的很好的教程，请访问：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|99939|http://evgenii.com/blog/testing-activity-in-android-studio-tutorial-part-1/|offset|length|99940|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|23|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@$D|O|E|P|1|Q]]|A|$]]|$1|F|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|C]]]]

Android Studio keeps evolving so the responses above will eventually be no longer applicable. For the current version of Android Studio 1.2.1.1, there's a nice tutorial on testing at:

<a href="http://evgenii.com/blog/testing-activity-in-android-studio-tutorial-part-1/" rel="nofollow noreferrer">http://evgenii.com/blog/testing-activity-in-android-studio-tutorial-part-1/</a>

blocks|key|316957|text|在gradle文件中添加下面的lib|type|unstyled|depth|inlineStyleRanges|entityRanges|data|316958|+androidTestCompile('com.android.support.test.espresso:espresso-core:2.2.2',+{
++++++++exclude+group:+'com.android.support',+module:+'support-annotations'
++++})|code-block|syntax|javascript|316959|在androidTest目录中创建类HomeActivityTest，在运行测试之前，在字符串资源文件中添加flurry_api_key和sender_id字符串，并更改失败和成功案例的值。|316960|@RunWith(AndroidJUnit4.class)
public+class+HomeActivityTest
{
++++private+static+final+String+SENDER_ID+=+"abc";
++++private+static+final+String+RELEASE_FLURRY_API_KEY+=+"xyz";

++++@Test
++++public+void+gcmRegistrationId_isCorrect()+throws+Exception
++++{
++++++++//+Context+of+the+app+under+test.
++++++++Context+appContext+=+InstrumentationRegistry.getTargetContext();

++++++++Assert.assertEquals(SENDER_ID,+appContext.getString(R.string.sender_id));
++++}

++++@Test
++++public+void+flurryApiKey_isCorrect()+throws+Exception
++++{
++++++++//+Context+of+the+app+under+test.
++++++++Context+appContext+=+InstrumentationRegistry.getTargetContext();

++++++++Assert.assertEquals(RELEASE_FLURRY_API_KEY,+appContext.getString(R.string.flurry_api_key));
++++}
}|316961|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

Add below lib inside gradle file

<pre><code> androidTestCompile('com.android.support.test.espresso:espresso-core:2.2.2', {
 exclude group: 'com.android.support', module: 'support-annotations'
 })
</code></pre>

Create class HomeActivityTest inside androidTest directory and before running the test add flurry_api_key and sender_id string inside string resource file and change the value for failure and success case.

<pre><code>@RunWith(AndroidJUnit4.class)
public class HomeActivityTest
{
 private static final String SENDER_ID = "abc";
 private static final String RELEASE_FLURRY_API_KEY = "xyz";

 @Test
 public void gcmRegistrationId_isCorrect() throws Exception
 {
 // Context of the app under test.
 Context appContext = InstrumentationRegistry.getTargetContext();

 Assert.assertEquals(SENDER_ID, appContext.getString(R.string.sender_id));
 }

 @Test
 public void flurryApiKey_isCorrect() throws Exception
 {
 // Context of the app under test.
 Context appContext = InstrumentationRegistry.getTargetContext();

 Assert.assertEquals(RELEASE_FLURRY_API_KEY, appContext.getString(R.string.flurry_api_key));
 }
}
</code></pre>

blocks|key|99997|text|Android+Studio+v.2.3.3|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|99998|突出显示要测试的代码上下文，并使用热键：CTRL%2BSHIFT%2BT|99999|使用对话框界面完成设置。|100000|测试框架应该镜像您的项目包布局以获得最佳结果，但您可以手动创建自定义测试，前提是您具有正确的目录和构建设置。|100001|entityMap^0|0|M|0|K|4|P|5|V|1|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Q|8|@$9|R|A|S|B|C]|$9|T|A|U|B|C]|$9|V|A|W|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|X|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|Y|8|@]|D|@]|E|$]]|$1|L|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]]|M|$]]

<code>Android Studio v.2.3.3</code>

Highlight the code context you want to test, and use the hotkey: <code>CTRL</code>+<code>SHIFT</code>+<code>T</code>

Use the dialog interface to complete your setup.

The testing framework is supposed to mirror your project package layout for best results, but you can manually create custom tests, provided you have the correct directory and build settings.

Just downloaded Android Studio which is based off of the Intellij Idea.

How would one create tests?

I notice there is a option for create a Test Module but this doesn't seem to do anything, only create a new project with src

I also tried pressing the hot key CTRL+AlT+T which allows to create unit tests on an existing class but it seems to want to place it in the current project. Of course this doesn't help with TDD

Does anyone have any experience here ?

How can I create tests in Android Studio?

Android Studio

单元测试

Android

刚刚下载了基于Intellij Idea的Android Studio。如何创建测试？我注意到有一个用于创建测试模块的选项，但这似乎没有任何作用，只使用src创建了一个新项目我还尝试了按热键CTRL+AlT+T，它允许在现有类上创建单元测试，但它似乎希望将其放在当前项目中。当然，这对TDD没有帮助有没有人在这里有经验？

问如何在Android Studio中创建测试？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在Android Studio中创建测试？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在Android Studio中创建测试？
EN