public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Meskauskas Audrius <audriusa@bluewin.ch>
To: Martin Olsson <mnemo@minimum.se>,  mauve-discuss@sources.redhat.com
Subject: Re: Mauve coding on Windows
Date: Sat, 10 Sep 2005 07:35:00 -0000	[thread overview]
Message-ID: <43228CB8.2060305@bluewin.ch> (raw)
In-Reply-To: <43229EF9.5090408@minimum.se>

No, I understand. You want to contribute to GNU Classpath project by 
writing new Mauve tests. But just for this you do not need to run all 
EXISTING Mauve tests. The existing tests are used to ensure that the new 
changes in GNU Classpath library itself do not introduce regressions, 
that nothing is spoiled while improving another part. You can write and 
run your tests on Sun's jre even without trying to build Classpath 
itself. After you commit them to CVS, others will run them on Classpath 
and use the results of your tests..

Of course, it is worthwhile to learn how to to run a complete Mauve test 
set, and how to build Classpath, and join the main project developing 
and so on. All this would be great from your side, but it takes time and 
may not be easy under Windows. The new Mauve tests are very important 
for us; our coverage is still not sufficient. There are still several 
important packages where no single class is covered. You told me you 
want to join us by writing new Mauve tests, I explained how to set up 
the developing platform in the fastest possible way.

Regards.
Audrius.


Martin Olsson wrote:

>
> I think you misunderstood; I actually intend to write tests for GNU 
> classpath.
>
>
> regards,
> martin
>
>
> Meskauskas Audrius wrote:
>
>> As your purpose is to just write some new tests and not to test GNU 
>> Classpath, the simplest and easiest way would be without much 
>> thinking to delete all tests.
>
> >
>
>>> I would like to write some test cases for the GNU classpath project. 
>>> I fetched Mauve from CVS (using eclipse "create project from cvs") 
>>> but I ran into a whole bunch of errors:
>>>
>>> http://mnemo.minimum.se/error.txt
>>>
>>> I think these errors are related to me running Windows 2000 and 
>>> windows does not allow a file called "Color" and a dir called "color".
>>>
>>> Someone on IRC said that there is atleast one other guy that uses 
>>> Windows for Mauve development (Jeroen?). If anyone can provide 
>>> information how I can setup a proper Mauve-compatible dev 
>>> environment on Windows please drop me a line.
>>>
>>> ---
>>>
>>> I also have another question, how do I know what test cases are 
>>> missing and needs to be implemented?
>>>
>>>
>>> rgrds
>>> martin
>>>
>>>
>>
>
>

  reply	other threads:[~2005-09-10  7:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-09 18:58 Martin Olsson
2005-09-09 20:01 ` Meskauskas Audrius
2005-09-09 23:54   ` Martin Olsson
2005-09-10  7:35     ` Meskauskas Audrius [this message]
2005-09-10  7:59       ` David Gilbert
2005-09-10  9:30         ` Mauve coding on Windows: The majority of tests runs under Windows Meskauskas Audrius
2005-09-10 10:18       ` Mauve coding on Windows Martin Olsson
2005-09-10 14:49         ` Dalibor Topic
2005-09-10  6:47 ` David Gilbert
2005-09-10  8:58 ` Andrew Haley
2005-09-10 17:15   ` Meskauskas Audrius
2005-09-16 17:08     ` Tom Tromey
2005-09-16 18:12       ` Meskauskas Audrius
2005-09-10 10:28 Jeroen Frijters

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=43228CB8.2060305@bluewin.ch \
    --to=audriusa@bluewin.ch \
    --cc=mauve-discuss@sources.redhat.com \
    --cc=mnemo@minimum.se \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).