android - ApplicationTestCase deprecated in API level 24 -

-

i created default empty project on android studio 2.1.2 api 24. in sample project, google offers depreciated class applicationtestcase:

this class deprecated in api level 24. use activitytestrule instead. new tests should written using android testing support library.

sample:

import android.app.application; import android.test.applicationtestcase;  /**  * <a href="http://d.android.com/tools/testing/testing_android.html">testing fundamentals</a>  */ public class applicationtest extends applicationtestcase<application> {     public applicationtest() {         super(application.class);     } }

my question: why android test case deprecated? how replace applicationtestcase activitytestrule?

edit:

i try expresso, on api 24 (compilesdkversion 24) have error:

error:conflict dependency 'com.android.support:appcompat-v7'. resolved versions app (24.0.0) , test app (23.1.1) differ. see http://g.co/androidstudio/app-test-app-conflict details. error:conflict dependency 'com.android.support:design'. resolved versions app (24.0.0) , test app (23.1.1) differ. see http://g.co/androidstudio/app-test-app-conflict details. error:conflict dependency 'com.android.support:support-annotations'. resolved versions app (24.0.0) , test app (23.1.1) differ. see http://g.co/androidstudio/app-test-app-conflict details. error:conflict dependency 'com.android.support:recyclerview-v7'. resolved versions app (24.0.0) , test app (23.1.1) differ. see http://g.co/androidstudio/app-test-app-conflict details.

when try add lib in build.gradle:

// android junit runner androidtestcompile 'com.android.support.test:runner:0.5' // junit4 rules androidtestcompile 'com.android.support.test:rules:0.5' // espresso core androidtestcompile 'com.android.support.test.espresso:espresso-core:2.2.2' // espresso-contrib datepicker, recyclerview, drawer actions, accessibility checks, countingidlingresource androidtestcompile 'com.android.support.test.espresso:espresso-contrib:2.2.2' // espresso-web webview support androidtestcompile 'com.android.support.test.espresso:espresso-web:2.2.2' // espresso-idling-resource synchronization background jobs androidtestcompile 'com.android.support.test.espresso:espresso-idling-resource:2.2.2'

my conclusion moment neither android test case nor expresso works on android api 24. right?

edit: 2016-08-05

i fix previous error on expresso that:

def espressoversion = '2.2.2' def testrunnerversion = '0.5' androidtestcompile "com.android.support.test:rules:${testrunnerversion}" androidtestcompile "com.android.support.test.espresso:espresso-core:${espressoversion}" configurations.androidtestcompile.dependencies.each { androidtestcompiledependency ->     androidtestcompiledependency.exclude group: 'com.android.support' }

the new androidtest example beta version of android studio 2.2 generates, this:

@runwith(androidjunit4.class) public class exampleinstrumentedtest {     @test     public void useappcontext() throws exception {         // context of app under test.         context appcontext = instrumentationregistry.gettargetcontext();          assertequals("org.mypackage", appcontext.getpackagename());     } }

just deprecation warning suggests, new instrumentation tests should use instrumentationregistry instead of extending androidtestcase. run them androidjunit4.

the relevant dependencies section in build.gradle looks this:

androidtestcompile('com.android.support.test.espresso:espresso-core:2.2.2', {     exclude group: 'com.android.support', module: 'support-annotations' })

Comments

Post a Comment

Popular posts from this blog

sql - invalid in the select list because it is not contained in either an aggregate function -

-
i can't figure out rewrite sql statement avoid error below msg 8120, level 16, state 1, line 26 column 'staffmember.staffmemberid' invalid in select list because not contained in either aggregate function or group clause. sql statment select (select [dbo].[udf_readstaffmemberbasic](sm.staffmemberid) xml path ('staffmembersummary'), root ('items'), type ), count(sm.staffmemberid) totalresults, ceiling(cast(count(sm.staffmemberid) decimal)/ @pagesize) totalpages staffmember sm inner join staffmembertoadditionalrole ar on sm.staffmemberid = ar.staffmemberid (sm.firstname '%' + @name + '%' or sm.surname '%' + @name + '%') , (@floorid null or sm.floorid = @floorid) , (@directorateid null or sm.directorateid = @directorateid) , (@additionalroleid null or ar.additionalroleid = @additionalroleid) order sm.staffmemberid offset @page * @pagesize rows fe...
Read more

Angularjs unit testing - ng-disabled not working when adding text to textarea -

-
i trying test angularjs component using karma, mocha, power-assert. have textarea , button in component, button disabled based on length of text in textarea. when run component in browser works perfectly. can't figure out how test functionality. here's bit of code. inquiryform.js function inquiryform($scope) { // plan add logic here } angular.module('myapp').component('inquiryform', { controller: inquiryform, controlleras: 'inquiryform', templateurl: 'inquiryform.html' }); inquiryform.html <div class="contact"> <div>thanks contacting us.</div> <form> <textarea ng-model="inquiryform.inquirytext" name=""></textarea> <input type="submit" value="send" ng-disabled="!inquiryform.inquirytext.length"> </form> </div> inquiryformtest.js describe('inquiry form ', () => { let $r...
Read more

How to start daemon on android by adb -

-
can me please, head swollen... i trying run daemon on android emu/device command: adb -s <device_name> shell su -c /dir/daemon <port_number> but nothink happens, , no errors! if do: adb -s <device> shell and form shell cmdline: su -c /dir/daemon <port_number> than work fine. try use shell-script , run: adb -s <device_name> shell sh su -c /dir/script.sh <port_number> and try generate script qt code port number , use: adb -s <device_name> shell sh su -c /dir/script.sh but not helped... problem if enter adb shell previous run daemon - work. problem on different device/emu/iso_image different command format not work. example: adb -s <device_name> shell su -c /dir/daemon <port_number> // work @ emu, not @ iso and vice: adb -s <device_name> shell su -c "/dir/daemon <port_number>" // work @ iso etc. everybody can answer what's matter? sorry english adb shell su -c ...
Read more