My ruby lib work (pri/kballard/ruby_lib_rewrite at thruhere) has
complete specs that are included at the ruby library level instead of
at the root level, so this is already being done for ruby.
I will note that generator tests should stay at the root level, only
library tests should be hoisted up to the library level.
-Kevin
On Jun 9, 2008, at 3:52 PM, Mark Slee wrote:
This sounds pretty reasonable to me and ultimately more scalable as
the
# of languages has ramped up. Integrating the tests with the build
processes per language is definitely a great idea and will make
running
the test much more painless.
I'd just ask that if you do this, please ensure it gets done across
all
languages at one. Don't want to end up in a situation where half the
language tests get migrated and the other half don't.
-----Original Message-----
From: Bryan Duxbury [mailto:[EMAIL PROTECTED]
Sent: Monday, June 09, 2008 3:30 PM
To: [email protected]
Subject: Unite library and test code?
How do people feel about keeping the language library code and their
respective tests together? It seems like it would be a little cleaner.
We also wouldn't have to redundant information at times, like the
separate build.xmls for Java.
-Bryan
--
Kevin Ballard
[EMAIL PROTECTED]
