harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Qiu" <sean.xx....@gmail.com>
Subject Re: [testing] make the tests structure comply with our testing conventions
Date Fri, 26 Oct 2007 07:36:53 GMT
What i am going to do is to run our tests within RI 1.5.0 first,
move the failed testing classes from src/test/api to src/test/impl and
reserve their packaging names.

The encountered problem is that some tests may contain both api testcases
and impl testcases.
IMHO, we can just move these testing classes into src/test/impl.
So the tests in src/test/api can run successfully in any compatible

Does it make sense? Any suggestions? Any volunteers?

2007/10/26, Sean Qiu <sean.xx.qiu@gmail.com>:
> To supply an independent tests archive,IMHO,
> make tests meet our testing conventions[1] should be a good start.
> I have taken a glance at the structure of luni module,
> and found that it does not comply with our conventions accurately.
> I guess this may be a common situation.
> So i am going to make our luni module comply with our convention[1] first.
> For example, the package "org.apache.harmony.luni.tests.java.io" should
> be moved to src/test/impl/common rather than src/test/api/common,
> since it is implementatin dependent.(am i right?)
> Any suggestions? If no one object, i will start to do it.
> [1] http://harmony.apache.org/subcomponents/classlibrary/testing.html
> --
> Sean Qiu
> China Software Development Lab, IBM

Sean Qiu
China Software Development Lab, IBM

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message