[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] Re: [platform-core-dev] test suites



There should be one AutomatedTests class per project and there should be
one AllTests class per package.

The AutomatedTests class should live in the "api" package. (e.g. the
package that makes most sense, the one without "internal" in the name, the
one where people would look first when trying to run the tests)
   org.eclipse.core.tests.resources.AutomatedTests
   org.eclipse.core.tests.runtime.AutomatedTests


equinox-dev-admin@xxxxxxxxxxx wrote on 06/02/2004 10:45:29 AM:

>
> as a point of interest, how many AutomatedTests classes should there
> be (one per package?) and where should they/it be?
>
> I like the idea of the OSGi tests following the same model.
>
> Jeff
>
>

>
> DJ Houghton/Ottawa/IBM@IBMCA
> Sent by: platform-core-dev-admin@xxxxxxxxxxx
> 06/01/2004 05:15 PM
>
> Please respond to
> platform-core-dev
>
> To
>
> platform-core-dev@xxxxxxxxxxx
>
> cc
>
> Subject
>
> [platform-core-dev] test suites
>
>
>
>
>
>
>
>
> A reminder of how the test suites are organized:
>
> - The AutomatedTests class is the one which is used by the automated test
> suites to run all our tests.
> - There should be an AllTests class in each of our test packages which
> calls the #suite() methods for each test class to run in that package.
> - The AutomatedTests#suite() method should call the AllTests#suite()
> methods for each package.
>
> I have done a quick pass over the runtime and resources tests to make
them
> match this criteria. (with certain exceptions) I did not make any changes
> to the OSGi tests but perhaps this format could be considered by the OSGi
> team.
>
> _______________________________________________
> platform-core-dev mailing list
> platform-core-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/platform-core-dev