Steven,

I'll look into this and keep you posted.

I apologize that csUnit is causing this issue. At the same time I'd like to thank you to raise the issue as now we can look into it and find a solution, which will benefit all other users as well.

Kind regards,
   Manfred.
---
Manfred Lange.
csUnit Lead Developer
http://www.csunit.org

Steven Evans wrote:

Hi,

  I am trying to create a csunit project using 2.0.3 but keep getting the error:

wizard.config could not be loaded.  Cound not find a part of the path “D:\Program%20Files\csunit.org\csunit%202.0.3\ wizard.config”

 

 

Can anyone help fix this issue?

 

 

Thanks

Hi,

  I am trying to create a csunit project using 2.0.3 but keep getting the error:

wizard.config could not be loaded.  Cound not find a part of the path “D:\Program%20Files\csunit.org\csunit%202.0.3\ wizard.config”

 

 

Can anyone help fix this issue?

 

 

Thanks

Lets hope it's a good one... I've been using nunit with testdriven in 2005
and I really really don't like it compared to csUnit...

Amir Kolsky
XP& Software


>-----Original Message-----
>From: csunit@yahoogroups.com [mailto:csunit@yahoogroups.com]
>On Behalf Of manfred_lange_agile
>Sent: Friday, April 28, 2006 9:05 PM
>To: csunit@yahoogroups.com
>Subject: [csunit] csUnit 2.1.1 BETA released
>
>csUnit 2.1.1 BETA Released
>==========================
>
>csUnit 2.1.1 BETA has been released and is available for
>download at http//www.csunit.org/download.
>
>This release has been compiled and tested with .NET 2.0. It is
>the first .NET 2.0 based version that contains an all new
>implementation of an addin for VS2005.
>
>Some areas in the code have been heavily refactored. It looks
>almost like a new implementation when compared to csUnit 2.0
>and earlier. On an opportunistic basis generics were introduced.
> The code has substantially improved, and we will continue
>towards that path.
>The major focus was on the core, the event handling, the
>command pattern implementation, and the GUI in general. The
>latter includes both the csUnitControl but also csUnitRunner,
>the GUI frontend. In particular we worked on improving the usability.
>
>
>We also ran some profiling sessions. As a consequence csUnit
>2.1.1 is up to 50% faster than earlier versions.
>
>Work that we expect to add for the before the production
>release of version 2.1 includes further refactoring in
>particular in the test execution engine, further usability
>improvements, categories support, and some smaller performance
>improvements.
>
>As always all bugfixes from earlier versions have been rolled
>over into this version.
>
>Please support the project with your donation (see button at
>http://www.csunit.org/download). Thank you!
>
>
>About csUnit
>============
>Inspired by JUnit, csUnit brings the power of unit testing to
>the .NET framework. csUnit is your key to unit testing and
>test-driven development using .NET languages such as C#,
>Visual Basic .NET, Visual J#, or Managed C++. csUnit was
>founded in 2001. For more information see http://www.csunit.org.
>
>
>
>Kind regards,
>   Manfred.
>---
>Manfred Lange.
>csUnit lead developer
>Email: manfred at csunit dot org
>http://www.csunit.org
>
>
>
>
>
>
>Yahoo! Groups Links
>
>
>
>
>
>

Lets hope it's a good one... I've been using nunit with testdriven in 2005
and I really really don't like it compared to csUnit...

  Amir Kolsky
XP& Software


>-----Original Message-----
>From: csunit@yahoogroups.com [mailto:csunit@yahoogroups.com]
>On Behalf Of manfred_lange_agile
>Sent: Friday, April 28, 2006 9:05 PM
>To: csunit@yahoogroups.com
>Subject: [csunit] csUnit 2.1.1 BETA released
>
>csUnit 2.1.1 BETA Released
>==========================
>
>csUnit 2.1.1 BETA has been released and is available for
>download at http//www.csunit.org/download.
>
>This release has been compiled and tested with .NET 2.0. It is
>the first .NET 2.0 based version that contains an all new
>implementation of an addin for VS2005.
>
>Some areas in the code have been heavily refactored. It looks
>almost like a new implementation when compared to csUnit 2.0
>and earlier. On an opportunistic basis generics were introduced.
> The code has substantially improved, and we will continue
>towards that path.
>The major focus was on the core, the event handling, the
>command pattern implementation, and the GUI in general. The
>latter includes both the csUnitControl but also csUnitRunner,
>the GUI frontend. In particular we worked on improving the usability.
>
>
>We also ran some profiling sessions. As a consequence csUnit
>2.1.1 is up to 50% faster than earlier versions.
>
>Work that we expect to add for the before the production
>release of version 2.1 includes further refactoring in
>particular in the test execution engine, further usability
>improvements, categories support, and some smaller performance
>improvements.
>
>As always all bugfixes from earlier versions have been rolled
>over into this version.
>
>Please support the project with your donation (see button at
>http://www.csunit.org/download). Thank you!
>
>
>About csUnit
>============
>Inspired by JUnit, csUnit brings the power of unit testing to
>the .NET framework. csUnit is your key to unit testing and
>test-driven development using .NET languages such as C#,
>Visual Basic .NET, Visual J#, or Managed C++. csUnit was
>founded in 2001. For more information see http://www.csunit.org.
>
>
>
>Kind regards,
>   Manfred.
>---
>Manfred Lange.
>csUnit lead developer
>Email: manfred at csunit dot org
>http://www.csunit.org
>
>
>
>
>
>
>Yahoo! Groups Links
>
>
>
>
>
>

csUnit 2.1.1 BETA Released
==========================

csUnit 2.1.1 BETA has been released and is available for download at
http//www.csunit.org/download.

This release has been compiled and tested with .NET 2.0. It is the
first .NET 2.0 based version that contains an all new implementation
of an addin for VS2005.

Some areas in the code have been heavily refactored. It looks almost
like a new implementation when compared to csUnit 2.0 and earlier. On
an opportunistic basis generics were introduced.
  The code has substantially improved, and we will continue towards
that path.
The major focus was on the core, the event handling, the command
pattern implementation, and the GUI in general. The latter includes
both the csUnitControl but also csUnitRunner, the GUI frontend. In
particular we worked on improving the usability.


We also ran some profiling sessions. As a consequence csUnit 2.1.1 is
up to 50% faster than earlier versions.

Work that we expect to add for the before the production release of
version 2.1 includes further refactoring in particular in the test
execution engine, further usability improvements, categories support,
and some smaller performance improvements.

As always all bugfixes from earlier versions have been rolled over
into this version.

Please support the project with your donation (see button at
http://www.csunit.org/download). Thank you!


About csUnit
============
Inspired by JUnit, csUnit brings the power of unit testing to the .NET
framework. csUnit is your key to unit testing and test-driven
development using .NET languages such as C#, Visual Basic .NET, Visual
J#, or Managed C++. csUnit was founded in 2001. For more information
see http://www.csunit.org.



Kind regards,
    Manfred.
---
Manfred Lange.
csUnit lead developer
Email: manfred at csunit dot org
http://www.csunit.org

As several releases have been made available and as this has led to a
several changes of csUnit, we felt it was about time to also update
the "Getting Started" tutorial.

You can find the new version at http://www.csunit.org/tutorials

Kind regards,
Manfred.
---
Manfred Lange.
csUnit Lead Developer
manfred @ csunit . org

csUnit 2.0.3 Released
=====================
csUnit 2.0.3 has been released and is available for download at
http//www.csunit.org/download.

This release has been tested with .NET 1.1 and VS.NET 2003 including a
side-by-side installation of VS2003 and VS2005.

This is a maintenance release and contains the following bugfixes:

1) BUGFIX, csUnitRunner, SourceForge Tracker ID 1447592: Console not
always
redirected. [12Mar2006, ml]

2) BUGFIX, csUnitRunner: Some methods for controls were not invoke on
the proper
thread. Where these cases have been identified, these methods are now
called
using Invoke() if InvokeRequired returns 'true'. [14Mar2006, ml]

3) BUGFIX, csUnit: Added Assert.Equals(double, double) and
Assert.Equals(double,
double, string). Furthermore added five additional tests to ensure
that if any
of the double values is NaN (Not a number), the assertions still work
properly.
[23Mar2006, ml]

All bugfixes have been carried over to the 2.1.* head revision as well
so that they are incorporated into the next 2.1 beta version.


.NET 2.0 and VS 2005
====================
A first beta version has been made available for .NET 2.0 at the end
of March 2006. It can be downloaded at http://www.csunit.org/download

A beta version that also includes an addin for VS 2005 is planned for
end of April 2006.

Please support the project with your donation (see button at
http://www.csunit.org/download). Thank you!


About csUnit
============
Inspired by JUnit, csUnit brings the power of unit testing to the .NET
framework. csUnit is your key to unit testing and test-driven
development using .NET languages such as C#, Visual Basic .NET, Visual
J#, or Managed C++. csUnit was founded in 2001. For more information
see http://www.csunit.org.



Kind regards,
    Manfred.
---
Manfred Lange.
csUnit lead developer
Email: manfred @ csunit . org (remove spaces)
http://www.csunit.org

csUnit 2.1.0 BETA Released
==========================

csUnit 2.1.0 BETA has been released and is available for download at
http//www.csunit.org/download.

This release has been compiled and tested with .NET 2.0.

Some areas in the code have been heavily refactored. It looks almost
like a new implementation when compared to previous releases. The
major focus was on the core, the event handling, the command pattern
implementation, and the GUI in general. The latter includes both the
csUnitControl but also csUnitRunner, the GUI frontend. On an
opportunistic basis generics were introduced.

Furthermore, all bugfixes from csUnit 2.0.x have been brought over.

Please support the project with your donation (see button at
http://www.csunit.org/download). Thank you!

Regarding support for VS 2005: We have planned a first beta version
available for VS 2005 by the end of April 2006.


About csUnit
============
Inspired by JUnit, csUnit brings the power of unit testing to the .NET
framework. csUnit is your key to unit testing and test-driven
development using .NET languages such as C#, Visual Basic .NET, Visual
J#, or Managed C++. csUnit was founded in 2001. For more information
see http://www.csunit.org.



Kind regards,
    Manfred.
---
Manfred Lange.
csUnit lead developer
Email: manfred @ csunit . org (remove spaces)
http://www.csunit.org

Manfred,
Thanks your prompt reply and confirming what I found.
I originally found the problem in 1.9.4, upgraded to 2.0.2 and found
it was still occuring.
Your assumptions are correct, and no I don't think you've overlooked
anything.
Regards
Nigel
--- In csunit@yahoogroups.com, Manfred Lange <ml@...> wrote:

Typo: It should read:
"I added the missing tests for items 2 to 4."
Kind regards,
Manfred.
---
Manfred Lange.
csUnit Lead Developer
http://www.csunit.org
Manfred Lange wrote:

I tested the issue with csUnit 2.0.2, and here are the results for Assert.Equals() with doubles:
1) Assert.Equals(double, NaN) works as expected, that is it fails
2) Assert.Equals(double, NaN, double) does not work as expected. It passes
3) Assert.Equals(double, double, NaN) does not work as expected. It passes.
4) Assert.Equals(double, double, <nullString)>) does not work as expected. It passes.
A test for the first case was already in place.
I added the missing tests for items 2 to 3. The fixes will be available in csUnit 2.0.3, which is planned for April 8.
Possible workarounds until then:
1) Add the following line in the tests:
Assert.False(Double.IsNaN(<yourDoubleVariable>));
2) Use Assert.Equals(double, double) without message or permitted

delta.

If I overlooked something in this issue, please let me know. Thank

you!

I apologize for the inconvenience. To avoid reappearance, the tests will also be rolled forward to csUnit 2.1.0 Beta, which we plan to have available by the end of this month. csUnit 2.1.0 and later will be the version that is compiled against .NET 2.0.
Kind regards,
Manfred.
---
Manfred Lange.
csUnit Lead Developer
http://www.csunit.org
Manfred Lange wrote:

Hi,
first, the standard question: which version are you using?
For now I assume that you are using the latest released version csUnit 2.0.2.
I assume that the expected value does not have the value "NaN"?
If my assumptions are correct, then I would see this as a bug. I'll check, and post results here.
Kind regards,
Manfred.
---
Manfred Lange.
csUnit Lead Developer
http://www.csunit.org
gnrutter wrote:

When using Assert.Equals to test the value of a double against an
expected value, I discovered that if the value of the 'actual'
parameter is Nan (Not A Number)then the method does not throw an
exception when I would have expected it to. This results in the unit
test passing when it should fail.
Is this a known problem?
[...]

Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/csunit/
<*> To unsubscribe from this group, send an email to:
csunit-unsubscribe@yahoogroups.com
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/

Manfred,

Thanks your prompt reply and confirming what I found.

I originally found the problem in 1.9.4, upgraded to 2.0.2 and found
it was still occuring.

Your assumptions are correct, and no I don't think you've overlooked
anything.

Regards
Nigel
--- In csunit@yahoogroups.com, Manfred Lange <ml@...> wrote:
>
> Typo: It should read:
>
> "I added the missing tests for items 2 to 4."
>
> Kind regards,
>    Manfred.
> ---
> Manfred Lange.
> csUnit Lead Developer
> http://www.csunit.org
>
> Manfred Lange wrote:
>
> > I tested the issue with csUnit 2.0.2, and here are the results for
> > Assert.Equals() with doubles:
> >
> > 1) Assert.Equals(double, NaN) works as expected, that is it fails
> > 2) Assert.Equals(double, NaN, double) does not work as expected. It
> > passes
> > 3) Assert.Equals(double, double, NaN) does not work as expected. It
> > passes.
> > 4) Assert.Equals(double, double, <nullString)>) does not work as
> > expected. It passes.
> >
> > A test for the first case was already in place.
> >
> > I added the missing tests for items 2 to 3. The fixes will be
> > available in csUnit 2.0.3, which is planned for April 8.
> >
> > Possible workarounds until then:
> >
> > 1) Add the following line in the tests:
> > Assert.False(Double.IsNaN(<yourDoubleVariable>));
> > 2) Use Assert.Equals(double, double) without message or permitted
delta.
> >
> > If I overlooked something in this issue, please let me know. Thank
you!
> >
> > I apologize for the inconvenience. To avoid reappearance, the tests
> > will also be rolled forward to csUnit 2.1.0 Beta, which we plan to
> > have available by the end of this month. csUnit 2.1.0 and later will
> > be the version that is compiled against .NET 2.0.
> >
> > Kind regards,
> >   Manfred.
> > ---
> > Manfred Lange.
> > csUnit Lead Developer
> > http://www.csunit.org
> >
> >
> >
> > Manfred Lange wrote:
> >
> >> Hi,
> >>
> >> first, the standard question: which version are you using?
> >>
> >> For now I assume that you are using the latest released version
> >> csUnit 2.0.2.
> >>
> >> I assume that the expected value does not have the value "NaN"?
> >>
> >> If my assumptions are correct, then I would see this as a bug. I'll
> >> check, and post results here.
> >>
> >> Kind regards,
> >>   Manfred.
> >> ---
> >> Manfred Lange.
> >> csUnit Lead Developer
> >> http://www.csunit.org
> >>
> >>
> >> gnrutter wrote:
> >>
> >>> When using Assert.Equals to test the value of a double against an
> >>> expected value, I discovered that if the value of the 'actual'
> >>> parameter is Nan (Not A Number)then the method does not throw an
> >>> exception when I would have expected it to. This results in the unit
> >>> test passing when it should fail.
> >>> Is this a known problem?
> >>> [...]
> >>
> >>
> >
>

Typo: It should read:

"I added the missing tests for items 2 to 4."

Kind regards,
    Manfred.
---
Manfred Lange.
csUnit Lead Developer
http://www.csunit.org

Manfred Lange wrote:

> I tested the issue with csUnit 2.0.2, and here are the results for
> Assert.Equals() with doubles:
>
> 1) Assert.Equals(double, NaN) works as expected, that is it fails
> 2) Assert.Equals(double, NaN, double) does not work as expected. It
> passes
> 3) Assert.Equals(double, double, NaN) does not work as expected. It
> passes.
> 4) Assert.Equals(double, double, <nullString)>) does not work as
> expected. It passes.
>
> A test for the first case was already in place.
>
> I added the missing tests for items 2 to 3. The fixes will be
> available in csUnit 2.0.3, which is planned for April 8.
>
> Possible workarounds until then:
>
> 1) Add the following line in the tests:
> Assert.False(Double.IsNaN(<yourDoubleVariable>));
> 2) Use Assert.Equals(double, double) without message or permitted delta.
>
> If I overlooked something in this issue, please let me know. Thank you!
>
> I apologize for the inconvenience. To avoid reappearance, the tests
> will also be rolled forward to csUnit 2.1.0 Beta, which we plan to
> have available by the end of this month. csUnit 2.1.0 and later will
> be the version that is compiled against .NET 2.0.
>
> Kind regards,
>   Manfred.
> ---
> Manfred Lange.
> csUnit Lead Developer
> http://www.csunit.org
>
>
>
> Manfred Lange wrote:
>
>> Hi,
>>
>> first, the standard question: which version are you using?
>>
>> For now I assume that you are using the latest released version
>> csUnit 2.0.2.
>>
>> I assume that the expected value does not have the value "NaN"?
>>
>> If my assumptions are correct, then I would see this as a bug. I'll
>> check, and post results here.
>>
>> Kind regards,
>>   Manfred.
>> ---
>> Manfred Lange.
>> csUnit Lead Developer
>> http://www.csunit.org
>>
>>
>> gnrutter wrote:
>>
>>> When using Assert.Equals to test the value of a double against an
>>> expected value, I discovered that if the value of the 'actual'
>>> parameter is Nan (Not A Number)then the method does not throw an
>>> exception when I would have expected it to. This results in the unit
>>> test passing when it should fail.
>>> Is this a known problem?
>>> [...]
>>
>>
>

I tested the issue with csUnit 2.0.2, and here are the results for
Assert.Equals() with doubles:

1) Assert.Equals(double, NaN) works as expected, that is it fails
2) Assert.Equals(double, NaN, double) does not work as expected. It passes
3) Assert.Equals(double, double, NaN) does not work as expected. It passes.
4) Assert.Equals(double, double, <nullString)>) does not work as
expected. It passes.

A test for the first case was already in place.

I added the missing tests for items 2 to 3. The fixes will be available
in csUnit 2.0.3, which is planned for April 8.

Possible workarounds until then:

1) Add the following line in the tests:
Assert.False(Double.IsNaN(<yourDoubleVariable>));
2) Use Assert.Equals(double, double) without message or permitted delta.

If I overlooked something in this issue, please let me know. Thank you!

I apologize for the inconvenience. To avoid reappearance, the tests will
also be rolled forward to csUnit 2.1.0 Beta, which we plan to have
available by the end of this month. csUnit 2.1.0 and later will be the
version that is compiled against .NET 2.0.

Kind regards,
    Manfred.
---
Manfred Lange.
csUnit Lead Developer
http://www.csunit.org



Manfred Lange wrote:

> Hi,
>
> first, the standard question: which version are you using?
>
> For now I assume that you are using the latest released version csUnit
> 2.0.2.
>
> I assume that the expected value does not have the value "NaN"?
>
> If my assumptions are correct, then I would see this as a bug. I'll
> check, and post results here.
>
> Kind regards,
>   Manfred.
> ---
> Manfred Lange.
> csUnit Lead Developer
> http://www.csunit.org
>
>
> gnrutter wrote:
>
>> When using Assert.Equals to test the value of a double against an
>> expected value, I discovered that if the value of the 'actual'
>> parameter is Nan (Not A Number)then the method does not throw an
>> exception when I would have expected it to. This results in the unit
>> test passing when it should fail.
>> Is this a known problem?
>> [...]
>

Hi,

first, the standard question: which version are you using?

For now I assume that you are using the latest released version csUnit
2.0.2.

I assume that the expected value does not have the value "NaN"?

If my assumptions are correct, then I would see this as a bug. I'll
check, and post results here.

Kind regards,
    Manfred.
---
Manfred Lange.
csUnit Lead Developer
http://www.csunit.org


gnrutter wrote:

>When using Assert.Equals to test the value of a double against an
>expected value, I discovered that if the value of the 'actual'
>parameter is Nan (Not A Number)then the method does not throw an
>exception when I would have expected it to. This results in the unit
>test passing when it should fail.
>
>Is this a known problem?
>
>
>
>
>
>
>Yahoo! Groups Links
>
>
>
>
>
>
>
>
>

When using Assert.Equals to test the value of a double against an
expected value, I discovered that if the value of the 'actual'
parameter is Nan (Not A Number)then the method does not throw an
exception when I would have expected it to. This results in the unit
test passing when it should fail.

Is this a known problem?

OK, I'm on my way to the other side of the world... I have sent you an
earlier version of the code sans the category arithmetic stuff. Do you need
me to send it again? The complete version I don't have on me right now

  Amir Kolsky
XP& Software


>-----Original Message-----
>From: csunit@yahoogroups.com [mailto:csunit@yahoogroups.com]
>On Behalf Of Manfred Lange
>Sent: Monday, March 13, 2006 5:46 AM
>To: csunit@yahoogroups.com
>Subject: Re: [csunit] Hi guys...
>
>Hi Amir,
>
>my understanding is that these are custom extensions that you
>have put in. Is this correct? If so, would you mind to zip up
>the sources, so that we can consider them for inclusion? In
>particular I would be interested in all kinds of test cases. Thank you!
>
>The current plan is to have a first version (probably beta)
>for .NET 2.0 by the end of March, and to have VS2005 support
>by the end of April.
>
>However, if we can fit the features in you have added, we'll
>consider them for inclusion. Having the sources available
>would help. Please make sure you can contribute the sources
>free from copyright claims. We would certainly give you
>credits for contributing the code, should we decide to use it.
>
>Cheers,
>   Manfred.
>
>
>Amir Kolsky wrote:
>
>>Just a query as to the status of a couple of the features that I have
>>in the 1.x version of csUnit, and have grown to depend upon...
>>
>>1. /fixture:NameOfClassTest
>          --
>>process this class only
>>    /fixture:NameOfClassTest+AnotherNameOfClassTest     --
>process these
>>classes only
>>    /fixture:-NameOfClassTest
>           --
>>remove this class from the list of processed classes
>>    /fixture:-NameOfClassTest-AnotherNameOfClassTest     --
>remove these
>>class from the list of processed classes
>>
>>2. /test:TestMethodName
>>    /test:TestMethodName+TestAnotherMethodName
>>    /test:-TestMethodName
>>    /test:-TestMethodName-TestAnotherMethodName
>>
>>3. /categories:ABC                     -- process only
>category ABC (used in
>>conjuction with a TestCategoryAttribute)
>>   /categories:XYZ+ABC              -- process only category
>ABC and XYZ
>>(used in conjuction with a TestCategoryAttribute)
>>   /categories:-ABC                     -- do not process category ABC
>>   /categories:-ABC-XYZ              -- do not process
>categories ABC and
>>XYZ
>>   /categories:-ABC+XYZ             -- do not process ABC but
>DO process
>>ABC&XYZ
>>  / categories:+XYZ-ABC             -- DO process XYZ but do
>NOT process
>>ABC&XYZ
>>the order in the above two is important
>>
>>4. /namespaces ----     similar to /fixture and /test
>>I often use these categories for distinguishing UI tests, acceptance
>>tests and combinations thereof... very useful.
>>
>>Thanks,
>> Amir Kolsky
>>XP& Software
>>
>>
>>
>>
>>Yahoo! Groups Links
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
>

I understand csUnit is a testing tool for .NET language. i read
tutorial at http://www.csunit.org/tutorials/index.html. I write a
simple project using csUnit. But i don't understand what csUnit can
do. you can show me more detail. What can csUnit do?

I understand csUnit is a testing tool for .NET language. i read
tutorial at http://www.csunit.org/tutorials/index.html. I write a
simple project using csUnit. But i don't understand what csUnit can
do. you can show me more detail. What can csUnit do?

Hi Amir,

my understanding is that these are custom extensions that you have put
in. Is this correct? If so, would you mind to zip up the sources, so
that we can consider them for inclusion? In particular I would be
interested in all kinds of test cases. Thank you!

The current plan is to have a first version (probably beta) for .NET 2.0
by the end of March, and to have VS2005 support by the end of April.

However, if we can fit the features in you have added, we'll consider
them for inclusion. Having the sources available would help. Please make
sure you can contribute the sources free from copyright claims. We would
certainly give you credits for contributing the code, should we decide
to use it.

Cheers,
    Manfred.


Amir Kolsky wrote:

>Just a query as to the status of a couple of the features that I have in the
>1.x version of csUnit, and have grown to depend upon...
>
>1. /fixture:NameOfClassTest                                             --
>process this class only
>    /fixture:NameOfClassTest+AnotherNameOfClassTest     --  process these
>classes only
>    /fixture:-NameOfClassTest                                            --
>remove this class from the list of processed classes
>    /fixture:-NameOfClassTest-AnotherNameOfClassTest     -- remove these
>class from the list of processed classes
>
>2. /test:TestMethodName
>    /test:TestMethodName+TestAnotherMethodName
>    /test:-TestMethodName
>    /test:-TestMethodName-TestAnotherMethodName
>
>3. /categories:ABC                     -- process only category ABC (used in
>conjuction with a TestCategoryAttribute)
>   /categories:XYZ+ABC              -- process only category ABC and XYZ
>(used in conjuction with a TestCategoryAttribute)
>   /categories:-ABC                     -- do not process category ABC
>   /categories:-ABC-XYZ              -- do not process categories ABC and
>XYZ
>   /categories:-ABC+XYZ             -- do not process ABC but DO process
>ABC&XYZ
>  / categories:+XYZ-ABC             -- DO process XYZ but do NOT process
>ABC&XYZ
>the order in the above two is important
>
>4. /namespaces ----     similar to /fixture and /test
>I often use these categories for distinguishing UI tests, acceptance tests
>and combinations thereof... very useful.
>
>Thanks,
> Amir Kolsky
>XP& Software
>
>
>
>
>Yahoo! Groups Links
>
>
>
>
>
>
>
>
>

csUnit 2.0.2 Released
=====================
csUnit 2.0.2 has been released and is available for download at
http//www.csunit.org/download.

This release has been tested with .NET 1.1 and VS.NET 2003. It
contains the following changes:

1) A new TestAssemblyFixtureAttribute. This can be used to implement a
class with an optional SetUp and an optional TearDown method. The
former method is called before any test in a test assembly is
executed. The latter is called once after all configured tests in a
test assembly have been executed, regardless of their outcome. This
delivers feature request "Assembly SetUp and TearDown" (SourceForge ID
758068).

2) The Assert class now also supports Assert.DoesNotContain() taking
two strings. Two overloads are available with one taking a third
parameter for a custom message, should the assertion fail.

3) csUnitCmd does not longer write a default file if no /xml directive
is supplied at the command line.

4) More tests/refactorings to improve overall quality. This affects in
particular assertions that take a permitted delta as one of their
parameters. The permitted delta cannot be negative any longer.

Please support the project with your donation (see button at
http://www.csunit.org/download). Thank you!

Regarding support for .NET 2.0 and VS 2005: We'll have a first beta
version available for .NET 2.0 by the end of March 2006. Support for
VS 2005 is planned for end of April 2006.


About csUnit
============
Inspired by JUnit, csUnit brings the power of unit testing to the .NET
framework. csUnit is your key to unit testing and test-driven
development using .NET languages such as C#, Visual Basic .NET, Visual
J#, or Managed C++. csUnit was founded in 2001. For more information
see http://www.csunit.org.



Kind regards,
    Manfred.
---
Manfred Lange.
csUnit lead developer
Email: manfred @ csunit . org (remove spaces)
http://www.csunit.org

Context: Uninstalling csUnit 1.9.x is required to install any other
version, including the current version 2.0.x.

Problem: After csUnit 1.9.x is uninstalled you might observe that the
wizards in VS.NET 2003 may not work anymore.

Solution: A repair tool for that is now available at
http://www.csunit.org/download (See csUnit Tools). The tool is called
VsLangProjRegTLib.exe.

Details: The setup for csUnit 1.9.x was created using a wizard, which
unfortunately also references a type library used by VS.NET. When
csUnit 1.9.x is uninstalled setup will also unregister that type
library. This breaks the wizards. The repair tool re-registers the
type library and the wizards work again without the need to repair or
reinstall VS.NET 2003.

The same tool might help repairing VS.NET 2003 if other AddIns are
removed as well, as these might have used the same wizards for
creating their setup. However, suitability of the repair tool has not
been tested with any other AddIn.

I apologize for any inconvenience this may have caused. To the best of
my knowledge csUnit 2.0 and later do not cause this issue.

Kind regards,
    Manfred.
---
Manfred Lange, csUnit lead developer
http://www.csunit.org

Just a query as to the status of a couple of the features that I have in the
1.x version of csUnit, and have grown to depend upon...

1. /fixture:NameOfClassTest                                             --
process this class only
     /fixture:NameOfClassTest+AnotherNameOfClassTest     --  process these
classes only
     /fixture:-NameOfClassTest                                            --
remove this class from the list of processed classes
     /fixture:-NameOfClassTest-AnotherNameOfClassTest     -- remove these
class from the list of processed classes

2. /test:TestMethodName
     /test:TestMethodName+TestAnotherMethodName
     /test:-TestMethodName
     /test:-TestMethodName-TestAnotherMethodName

3. /categories:ABC                     -- process only category ABC (used in
conjuction with a TestCategoryAttribute)
    /categories:XYZ+ABC              -- process only category ABC and XYZ
(used in conjuction with a TestCategoryAttribute)
    /categories:-ABC                     -- do not process category ABC
    /categories:-ABC-XYZ              -- do not process categories ABC and
XYZ
    /categories:-ABC+XYZ             -- do not process ABC but DO process
ABC&XYZ
   / categories:+XYZ-ABC             -- DO process XYZ but do NOT process
ABC&XYZ
the order in the above two is important

4. /namespaces ----     similar to /fixture and /test
I often use these categories for distinguishing UI tests, acceptance tests
and combinations thereof... very useful.

Thanks,
  Amir Kolsky
XP& Software

Hi!
I'm trying csUnit 2.0 and looks pretty good. Thanks!

I have noticed that it leaves a counter (number of runs?)
in the solution file.  May I ask what's for?  It bothers
a bit when you have the solution file version controlled.
I wouldn't mind if it goes either to registry, an own
file or even in the .suo.

Regards,
-Hernán.

Great to have the list - and to see work progressing :)

I am keen to have csUnit with VS2005 as I like the way csUnit works -
keep up the good work :)

Glenn Crouch mailto:glenn@...
ESB Consultancy http://www.esbconsult.com
Home of ESBPCS & ESB Calculators
Kalgoorlie-Boulder, Western Australia

A zip-file with the sources for csUnit 2.0.1 is available at:
http://prdownloads.sourceforge.net/csunit/csUnit.2.0.1.sources.zip?download

The file is provided for people who cannot use CVS to get access to
the source files.

If you have any further questions, please post to this group or
contact manfred @ csunit . org

Kind regards,
Manfred.
---
Manfred Lange, csUnit lead developer

We've just released csUnit 2.0.1. Please download from http://www.csunit.org

This version does not yet support VS.NET 2005 or .NET 2.0. It supports
VS.NET 2002/2003 and .NET 1.0/1.1.

We've also tested in an environment using VS.NET 2003 and VS.NET 2005
side-by-side. It can be used from VS.NET 2003, but not from VS.NET 2005.

csUnit 2.1, which will have VS.NET 2005 and .NET 2.0 support, is planned
for end of March 2006.

Best regards,
    Manfred.

Unfortunately, for reasons unknown to me Yahoo! has decided to
terminate and delete the csUnit group. I tried to recover it through
their customer care department but got not a single reply. Very
disappointing!

Therefore I decided to create a new one. Let's see how long this will
last.

Best regards,
Manfred.
---
manfred @ csunit . org (remove spaces)