search

suli1 / android-test-kit

Automatically exported from code.google.com/p/android-test-kit
0 stars 0 forks source link

Improve the startup time #27

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Run Espresso with a very simple test in Eclipse

What is the expected output? What do you see instead?
Expected: The test starts in few seconds
Actual: It took almost a minute to start the test. If I run 60 times a day 
during my development, I waste an hour a day just to wait it to start!

What version of the product are you using? On what operating system?
1.0-SNAPSHOT

Please provide any additional information below.

Original issue reported on code.google.com by K76...@gmail.com on 26 Nov 2013 at 3:13

GoogleCodeExporter commented 9 years ago 
This is not an Espresso issue. Most likely, this is due to the number of 
classes in your apk. Try running a single test, instead of letting am 
instrument find every single test case in your apk. If it is much quicker, then 
it is due to classpath scanning of your apk to find tests.

Original comment by vale...@google.com on 16 Dec 2013 at 6:10

GoogleCodeExporter commented 9 years ago 
But I am using Eclipse, and GITR does not extend InstrumentationTestRunner, so 
I can't select a single TestCase class.

Original comment by K76...@gmail.com on 17 Dec 2013 at 3:43