14915
> -Ursprüngliche Nachricht-
> Von: Markus Schaber [mailto:m.scha...@codesys.com]
> Gesendet: Freitag, 14. Juni 2013 13:53
> An: Subversion Dev (dev@subversion.apache.org)
> Betreff: AW: Proposal for separating Tests into groups
>
> Hi,
>
> Considering Bens mails, and some p
ndet: Donnerstag, 13. Juni 2013 15:39
An: Markus Schaber
Cc: Subversion Dev (dev@subversion.apache.org)
Betreff: Re: Proposal for separating Tests into groups
On Thu, Jun 13, 2013 at 3:20 PM, Markus Schaber wrote:
> This are two alternative proposals for the test suite:
>
> Rationale: Develope
On Thu, Jun 13, 2013 at 4:11 PM, Markus Schaber wrote:
> I definitely remember that an existing test case which I had written was
> cut down in r1356418 because it took to long, and later converted into
> an #ifdef in r1356442.
I think there's only two tests that are like that, the one you
mentio
Hi, Ben,
Von: Ben Reser [b...@reser.org]
>On Thu, Jun 13, 2013 at 3:20 PM, Markus Schaber wrote:
>> This are two alternative proposals for the test suite:
>>
>> Rationale: Developers restrain from implementing some tests because they
>> just take to much time to run at every commit.
>
> I don't
On Thu, Jun 13, 2013 at 3:20 PM, Markus Schaber wrote:
> This are two alternative proposals for the test suite:
>
> Rationale: Developers restrain from implementing some tests because they just
> take to much time to run at every commit.
I don't think that's a problem with Subversion. I can run
Hi,
This are two alternative proposals for the test suite:
Rationale: Developers restrain from implementing some tests because they just
take to much time to run at every commit.
Other test systems like JUnit, NUnit or the CODESYS Test Manager come with ways
to select unit tests by category, s
6 matches
Mail list logo
