TestingK9

You can help us by running some simple automated tests for K-9 on your device. All you need is adb.

Download the latest test build from https://k9mail.ci.cloudbees.com/job/master/lastSuccessfulBuild/ for the development branch, or https://k9mail.ci.cloudbees.com/job/4.0-MAINT/lastSuccessfulBuild/ for the stable build (the version published to Google Play). There should be two "Build Artifacts" to download -- one is K-9, and the other is tests for K-9. Install them both on your device. The package has been renamed so it installs as a completely different app than the version of K-9 you are using for your mail, so it should be safe to test. You'll find this version of K-9 installed as "K-9 CloudBees" instead of "K-9 Mail", and you can even try it out if you so desire.

If you're running tests because you encountered a bug in a specific version of K-9, find the build with the corresponding note "Changes: 1. Bumped manifest to [version number]".

Run our automated tests on your device:

adb install [-r] K9Cloud-master-2012-06-08_23-39-55-609cdf6bc5-10.apk
adb install [-r] K9CloudTests-master-2012-06-08_23-39-55-609cdf6bc5-10.apk
adb shell am instrument -w -e coverage false com.fsck.k9cloud.tests/com.zutubi.android.junitreport.JUnitReportTestRunner
adb pull /system/build.prop .
adb pull /data/data/com.fsck.k9cloud/files/junit-report.xml .

Please report the filename of K-9 tested and your phone model and carrier. Also attach the junit-report.xml file if your phone is rooted or the screen output test results if not rooted, as well as the build.prop file (build.prop describes your particular hardware and Android version, as well as some things that root users can tweak, but has no personal information) to [email protected]. The results you send will be published, in whole or in part, except for any identifying information from the email headers other than perhaps the Message-ID.

Sample successful test output:

com.fsck.k9.activity.MessageReferenceTest:.......  
com.fsck.k9.helper.Address:...  
com.fsck.k9.helper.HtmlConverterTest:...  
com.fsck.k9.helper.Utility_quoteAtoms:..  
com.fsck.k9.mail.internet.MimeUtilityTest:..  
com.fsck.k9.mail.internet.ViewablesTest:.....  
com.fsck.k9.mail.store.ImapResponseParserTest:.....  
com.fsck.k9.mail.store.ImapStoreUriTest:.........  
com.fsck.k9.mail.store.imap.ImapUtilityTest:..  
Test results for InstrumentationTestRunner=......................................  
Time: 0.157  

OK (38 tests)

Sample unsuccessful output:

com.fsck.k9.activity.MessageReferenceTest:.......
com.fsck.k9.helper.Address:...
com.fsck.k9.helper.HtmlConverterTest:...
com.fsck.k9.helper.Utility_quoteAtoms:..
com.fsck.k9.mail.internet.MimeUtilityTest:..
com.fsck.k9.mail.internet.ViewablesTest:...
Failure in testTextPlusRfc822Message:
junit.framework.ComparisonFailure: expected:<...+00:00...> but was:<......>
	at com.fsck.k9.mail.internet.ViewablesTest.testTextPlusRfc822Message(ViewablesTest.java:185)
	at java.lang.reflect.Method.invokeNative(Native Method)
	at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:169)
	at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:154)
	at android.test.InstrumentationTestRunner.onStart(InstrumentationTestRunner.java:430)
	at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1447)
.
com.fsck.k9.mail.store.ImapResponseParserTest:.....
com.fsck.k9.mail.store.ImapStoreUriTest:.........
com.fsck.k9.mail.store.imap.ImapUtilityTest:..
Test results for InstrumentationTestRunner=.....................F.................
Time: 1.858

FAILURES!!!
Tests run: 38,  Failures: 1,  Errors: 0