darrinps wrote: > If you look at the link I provided, it specifies otherwise: > > "You can create a test project anywhere in your file system, but *the > best approach is to add the test project so that its root directory tests/is > at the same level as the > src/ directory of the main application's projec*t. This helps you find > the tests associated with an application. For example, if your application > project's root directory is MyProject, then you should use the following > directory structure:
That is not otherwise. This page and the example you quote show one way to organize two projects. It says plain as day "create a test project" right in the part you quote. Apparently you skipped that step before. It's still set up as a separate project. Read that page. > MyProject/ > AndroidManifest.xml > res/ > ... (resources for main application) > src/ > ... (source code for main application) ... > tests/ > AndroidManifest.xml > > Notice the presence of its own manifest. > res/ > ... (resources for tests) > src/ > ... (source code for tests) > > " > > > That is why I went down this path. Looks like some (most maybe) do it the > easy/separate way but some (Mark) have gotten it to work the suggested way. > You misread the instructions. They clearly tell you to set up a separate test project. >From that page: "You should always use Android tools to create a test project." Did you do that? "The Android SDK contains tools for Eclipse with ADT and for the command line that create and update test projects for you. The tools create the directories you use for source code and resources and the manifest file for the test package. The command-line tools also create the Ant build files you need." Q.E.D. -- Lew -- 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
