官术网_书友最值得收藏!

Even more assertions

If the assertions that are reviewed previously do not seem to be enough for your tests' needs, there is still another class included in the Android framework that covers other cases. This class is MoreAsserts (http://developer.android.com/reference/android/test/MoreAsserts.html).

These methods are also overloaded to support different parameter types. Among the assertions, we can find the following:

  • assertAssignableFrom: This asserts that an object is assignable to a class.
  • assertContainsRegex: This asserts that an expected Regex matches any substring of the specified String. It fails with the specified message if it does not.
  • assertContainsInAnyOrder: This asserts that the specified Iterable contains precisely the elements expected, but in any order.
  • assertContainsInOrder: This asserts that the specified Iterable contains precisely the elements expected, but in the same order.
  • assertEmpty: This asserts that an Iterable is empty.
  • assertEquals: This is for some Collections not covered in JUnit asserts.
  • assertMatchesRegex: This asserts that the specified Regex exactly matches the String and fails with the provided message if it does not.
  • assertNotContainsRegex: This asserts that the specified Regex does not match any substring of the specified String, and fails with the provided message if it does.
  • assertNotEmpty: This asserts that some Collections not covered in JUnit asserts are not empty.
  • assertNotMatchesRegex: This asserts that the specified Regex does not exactly match the specified String, and fails with the provided message if it does.
  • checkEqualsAndHashCodeMethods: This is a utility used to test the equals() and hashCode() results at once. This tests whether equals() that is applied to both objects matches the specified result.

The following test checks for an error during the invocation of the capitalization method called via a click on the UI button:

@UiThreadTest
public void testNoErrorInCapitalization() {
String msg = "capitalize this text";
editText.setText(msg);

button.performClick();

String actual = editText.getText().toString();
String notExpectedRegexp = "(?i:ERROR)";
String errorMsg = "Capitalization error for " + actual;
assertNotContainsRegex(errorMsg, notExpectedRegexp, actual);
}

If you are not familiar with regular expressions, invest some time and visit http://developer.android.com/reference/java/util/regex/package-summary.html because it will be worth it!

In this particular case, we are looking for the word ERROR contained in the result with a case-insensitive match (setting the flag i for this purpose). That is, if for some reason, capitalization doesn't work in our application, and it contains an error message, we can detect this condition with the assertion.

Note

Note that because this is a test that modifies the user interface, we must annotate it with @UiThreadTest; otherwise, it won't be able to alter the UI from a different thread, and we will receive the following exception:

INFO/TestRunner(610): ----- begin exception -----
INFO/TestRunner(610): android.view.ViewRoot$CalledFromWrongThreadException: Only the original thread that created a view hierarchy can touch its views.
INFO/TestRunner(610):     at android.view.ViewRoot.checkThread(ViewRoot.java:2932)
[...]
INFO/TestRunner(610):     at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1447)
INFO/TestRunner(610): ----- end exception -----
主站蜘蛛池模板: 景德镇市| 中方县| 新龙县| 社旗县| 武隆县| 旌德县| 西安市| 福海县| 西乌珠穆沁旗| 江城| 阜新市| 安溪县| 吉木乃县| 文安县| 海城市| 汤原县| 分宜县| 蚌埠市| 新野县| 三江| 怀柔区| 米林县| 宜州市| 全南县| 鄂伦春自治旗| 锡林浩特市| 阳曲县| 天全县| 栾川县| 甘南县| 莫力| 比如县| 利辛县| 育儿| 碌曲县| 招远市| 丰台区| 凤阳县| 白水县| 永和县| 慈利县|