Need help migrating test suites
Uche Ogbuji
Work on Amara 2.x has been proceeding pretty well. We're looking good
to gain at least an order of magnitude improvement in performance, we're
ditching a lot of cruft, cleaning up the code-base and APIs. If you're
curious, you can have a look at http://hg.4suite.org/amara/ , but really
it's not good for much more than having a look, for reasons that bring
me to the point of this message.
4Suite 1.x and Amara have great test suites. Having such extensive
tests has helped maintain code quality over the years. It will also be
key to accelerating the completion of Amara 2.x, if we can roll up our
sleeves and do some work. Our plan is to have the dev tree to the point
where in a week or two we can have people tentatively poke at bits of
XML processing functionality, but to make that happen we'll need you help.
We need volunteers to port the test suites. Here are some notes on what
such a migration will entail:
http://xml3k.org/Amara2/Developer_notes/Test_migration
In brief, Amara test suites need little more than import changes, while
4Suite tests will also require porting from the old Ft.Lib.Test
machinery to unittest (our stuff predated unittest but now it's time to
move along).
This is one of the most important things you can do to help, so if you
want to see Amara 2.x soon, with all its great improvements, please let
us know, and we'll start assigning volunteers to chunks of the work.
--
Uche Ogbuji http://uche.ogbuji.net
Founding Partner, Zepheira http://zepheira.com
Linked-in profile: http://www.linkedin.com/in/ucheogbuji
Articles: http://uche.ogbuji.net/tech/publications/
Luis Miguel Morillas
>
> Hi all,
>
> Work on Amara 2.x has been proceeding pretty well. We're looking good
> to gain at least an order of magnitude improvement in performance, we're
> ditching a lot of cruft, cleaning up the code-base and APIs. If you're
> curious, you can have a look at http://hg.4suite.org/amara/ , but really
> it's not good for much more than having a look, for reasons that bring
> me to the point of this message.
>
> 4Suite 1.x and Amara have great test suites. Having such extensive
> tests has helped maintain code quality over the years. It will also be
> key to accelerating the completion of Amara 2.x, if we can roll up our
> sleeves and do some work. Our plan is to have the dev tree to the point
> where in a week or two we can have people tentatively poke at bits of
> XML processing functionality, but to make that happen we'll need you help.
>
> We need volunteers to port the test suites. Here are some notes on what
> such a migration will entail:
>
> http://xml3k.org/Amara2/Developer_notes/Test_migration
>
> In brief, Amara test suites need little more than import changes, while
> 4Suite tests will also require porting from the old Ft.Lib.Test
> machinery to unittest (our stuff predated unittest but now it's time to
> move along).
>
> This is one of the most important things you can do to help, so if you
> want to see Amara 2.x soon, with all its great improvements, please let
> us know, and we'll start assigning volunteers to chunks of the work.
>
OK. I want to help. Tell me more about the chunks to work on.
> --
> Uche Ogbuji http://uche.ogbuji.net
> Founding Partner, Zepheira http://zepheira.com
> Linked-in profile: http://www.linkedin.com/in/ucheogbuji
> Articles: http://uche.ogbuji.net/tech/publications/
>
>
> >
>
--
Saludos,
--
Luis Miguel
Eric Larson
I'm also in. Do they need to be migrated from the 4Suite CVS and then
added to the Amara mercurial repo when ready?
Thanks!
Eric Larson
Eric Larson
Ok, I'm answering my own question. In poking around a good deal more
things are looking quite a bit clearer. With that in mind I did have a
few questions:
1. Is there a place we should say what we are working to reduce any conflicts?
2. Are we going to use anything like py.test or nose for running the tests?
I started looking through the Ft.Lib tests and my hope is to get
something working this week as far a migrations go. If someone has
migrated some tests already, please let folks know on the list.
Thanks!
Eric
Uche Ogbuji
> On Tue, Apr 1, 2008 at 6:16 PM, Eric Larson <ion...@gmail.com> wrote:
>
>> I'm also in. Do they need to be migrated from the 4Suite CVS and then
>> added to the Amara mercurial repo when ready?
>>
>>
>
> Ok, I'm answering my own question. In poking around a good deal more
> things are looking quite a bit clearer. With that in mind I did have a
> few questions:
>
> 1. Is there a place we should say what we are working to reduce any conflicts?
>
The plan is for me to organize the volunteers, so there should be no
conflicts.
> 2. Are we going to use anything like py.test or nose for running the tests?
>
I don't think so. I'd like to avoid an external dependency for
something as fundamental as testing.
> I started looking through the Ft.Lib tests and my hope is to get
> something working this week as far a migrations go. If someone has
> migrated some tests already, please let folks know on the list.
>
Again I'm planning to organize things. There is an order we should
pursue, and there is procedure for recording observations and such from
the conversion.
More on all that today.
Joel Bender
> We need volunteers to port the test suites.
Count me in. It will take me longer to get up to speed with the
unittest framework because I haven't used it before. Keep your
productivity expectations sufficiently low :-).
Joel
Uche Ogbuji
Ah, my friend, many hands make light work, so we can all afford to be a
bit less productive now that you've joined us :-)
Seriously, thanks. You'll find unittest pretty easy to work. Took me a
matter of minutes when I used to to start the Amara 1.x test suites.
You'll hear more on organization and directions today.
BTW, do you have any thoughts on my responses to your Amara 2.x ideas?
I hope you don't think I was slamming down your proposals. I'd really
like to know whether my suggestions help fill your use-case gaps,
because I will need help making sure Amara 2 bindery has a top-notch
API. I'm definitely not against changes and additions at this point. I
welcome them. But I do plan to be a bit cautious.
Thanks.
Eric Larson
On Wed, Apr 2, 2008 at 8:29 AM, Uche Ogbuji <uc...@ogbuji.net> wrote:
>
> Eric Larson wrote:
> > On Tue, Apr 1, 2008 at 6:16 PM, Eric Larson <ion...@gmail.com> wrote:
> >
>
> >> I'm also in. Do they need to be migrated from the 4Suite CVS and then
> >> added to the Amara mercurial repo when ready?
> >>
> >>
> >
> > Ok, I'm answering my own question. In poking around a good deal more
> > things are looking quite a bit clearer. With that in mind I did have a
> > few questions:
> >
> > 1. Is there a place we should say what we are working to reduce any conflicts?
> >
>
> The plan is for me to organize the volunteers, so there should be no
>
> conflicts.
>
> > 2. Are we going to use anything like py.test or nose for running the tests?
> >
>
> I don't think so. I'd like to avoid an external dependency for
> something as fundamental as testing.
>
>
>
> > I started looking through the Ft.Lib tests and my hope is to get
> > something working this week as far a migrations go. If someone has
> > migrated some tests already, please let folks know on the list.
> >
>
> Again I'm planning to organize things. There is an order we should
> pursue, and there is procedure for recording observations and such from
> the conversion.
>
> More on all that today.
>
Sounds good. Thanks for the clarification Uche.
Eric
John L. Clark
> > > This is one of the most important things you can do to help, so if you
> > > want to see Amara 2.x soon, with all its great improvements, please let
> > > us know, and we'll start assigning volunteers to chunks of the work.
> > >
> >
> > OK. I want to help. Tell me more about the chunks to work on.
> >
>
> I'm also in. Do they need to be migrated from the 4Suite CVS and then
> added to the Amara mercurial repo when ready?
I'm definitely interested in helping with the migration effort, as well.
Take care,
John L. Clark