search

JasonWongYH / android-test-kit

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

GITR cannot be configured in Eclipse with ADT 22.3 #17

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Setup a test project using the GITR
2. Go to Eclipse > Run configuration and create a new configuration
3. Select 
com.google.android.apps.common.testing.testrunner.GoogleInstrumentationTestRunne
r

Expected:
No error

Got:
The instrumentation runner must be of type 
android.test.InstrumentationTestRunner

Versions:
Windows XP SP3, Maven 3.0, m2e, TestKit git version b49a13f0

Original issue reported on code.google.com by m...@thomaskeller.biz on 13 Nov 2013 at 12:34

GoogleCodeExporter commented 9 years ago 
I don't have a windows machine. Is this still an issue?

Original comment by vale...@google.com on 9 Jan 2014 at 7:35

GoogleCodeExporter commented 9 years ago 
I don't have this Windows machine available anymore, only a Mac now. If you 
tested on Mac then I guess it won't happen to me either anymore.

But I wonder why you already closed this bug as "WontFix" already - is 
"NeedInfo" not more sufficient...?!

Original comment by m...@thomaskeller.biz on 9 Jan 2014 at 10:22

GoogleCodeExporter commented 9 years ago 
I still have the issue with v1.1. I'm on Windows. I've looked into the Error 
Log but there's nothing. I would gladly help regarding this issue. Is there 
anything I can do?

Original comment by thier...@gmail.com on 10 Jan 2014 at 1:13

GoogleCodeExporter commented 9 years ago 
I have the same issue with v1.1 on a Mac with Eclipse Kepler and ADT 22.3

Original comment by Daniel.B...@gmail.com on 25 Jan 2014 at 8:40

GoogleCodeExporter commented 9 years ago 
I have the same issue with v1.1 on a Mac with ADT 22.3

Original comment by Just.s...@gmail.com on 27 Feb 2014 at 5:15

GoogleCodeExporter commented 9 years ago 
I encountered the same issue with v1.1 on a Mac with Eclipse Kepler and ADT 22.3

Original comment by jeschua....@googlemail.com on 12 Mar 2014 at 9:08

GoogleCodeExporter commented 9 years ago 
I have this issue with espresso-contrib-1.1-bundled with ADT 22.3 too.

Original comment by arne.jan...@gmail.com on 17 Mar 2014 at 12:30

GoogleCodeExporter commented 9 years ago 
Please reopen this issue.

Original comment by arne.jan...@gmail.com on 17 Mar 2014 at 12:31

GoogleCodeExporter commented 9 years ago 
The problem only occurs if you select a single testclass in the run 
configuration. If you select a project or a package to test, the error does not 
show up.

Still, this is a problem.

Original comment by arne.jan...@gmail.com on 17 Mar 2014 at 12:36

GoogleCodeExporter commented 9 years ago 
We're also seeing this, and the issue not restricted to Windows. But to me this 
sounds more like a bug in the Eclipse ADT plugin than in the GITR. ATD's check 
simply seems to be too strict, it should check for being derived from 
android.app.Instrumentation instead.

Original comment by sschuberth on 15 Apr 2014 at 11:48

GoogleCodeExporter commented 9 years ago 
I've filed a bug against Eclipse ADT about this: 
http://code.google.com/p/android/issues/detail?id=68575

Original comment by sschuberth on 15 Apr 2014 at 1:36