I can't figure out how to test my library project using the r14 tools.

I'm using the "self-contained project" method described at the bottom
of Managing Projects page:

http://developer.android.com/guide/developing/projects/index.html

"Testing a Library Project [...] You can set up a set up a standard
application project that depends on the library and put the
instrumentation in that project. This lets you create a self-contained
project that contains both the tests/instrumentations and the code to
test."

I have such a project and was previously able to test it with:

# ant run-tests

Before I updated the project, "default.properties" contained:

android.library.reference.1=..

and "build.properties" contained:

tested.project.dir=.

After updating the lib-project, I updated the test project:

# android update test-project --path . --main .

But after updating the test project, neither the previous command "ant
run-tests" nor the updated command "ant debug installt test" will
succeed.

"ant debug installt test" fails:

sdk\tools\ant\build.xml:484: subant task calling a target that depends
on its parent target '-build-setup'.

Then I noticed that the new property "project.is.test" had not been
set by the update, so I added that to ant.properties, but then even
"ant clean" fails:

sdk\tools\ant\build.xml:372: subant task calling its own parent
target.

Is this method for testing library projects doable using the r14 tools?

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Reply via email to