Could be I'm wrong, but I believe that if an application is to serve as a "Best Practices' app, it should also include units tests (NUnit). Do these unit tests exist in the development teams environment and if so, could we get them? Thanks, Kevin
Are the Issue Tracker developers active in this forum? I have been watching the posts on ASP.net forums for awhile now and have noticed that many questions go unanswered. I understand that we are all busy, but if the development team or a representation of
the development team is not active in this forum I would like to know so that I am not wasting my valuable time posting here. If there is a better place for this discussion, I would be more than willing to take it there if I knew where "there" was. Thanks,
Kevin
Hi Kevin, Thanks for using the Issue Tracker! The Issue Tracker was released to the community and now belongs to the community. Microsoft does not offer formal support for the Issue Tracker. This forum is the place for anyone using the Issue Tracker to share
what they know and answer each others questions. -- best, Stephen Walther
I would be intereste on understandign a little bit more on what you would like to see us ship for unit test. Could you drill more on your ideas? thanks in advance AdnreS
AndresS
This posting is provided "AS IS" with no warranties, and confers no rights.
Hi Andre, I too would be interested in seeing some real world unit tests. The samples and articles look fine but I find it difficult translating that to my own code\business objects. I've found NunitASP very helpful though...in particular the extreme programming
method\example that they give. However I don't see myself using that technique and I certainly can't use on our existing application. For me at least, *anything* would be useful to help understand how I can apply it! Many thanks Best regards Steve
One of the reasons that I want to see unit tests is so that I can learn from them so it is hard for me to elaborate in my needs. In my world (Enterprise Developement), unit testing is a necessity since we have developed a common application framework and libraries
that all out corporate applications use. We need to know that changes we make to support a new requirement for an application will not break any of the other applications. For this, we implement tests that run all framwork, common and business logic against
known "good & bad" data. Whenever we run across a new bug, we first build a test that fails and then we fix the bug so that the test passes. Now that particular bug should never be a problem again. Up til a few years ago the unit testing has been our own flavor
of testing because there wasn't any tools for the language we used. Now we are venturing into the .NET world that has unit testing tools such as NUnit that we would like to utilize. Seeing these tools in use for real-world applications will help developers
new to .NET learn using "good" habits right from the start instead of having to change their ways later on. It also serves to help understand the applicatuins since we can easily see how classes are used and the expected results are coded in the unit tests.
Hope this helps. Kevin
Stephen, I keep waiting for another release of Issue Tracker (cause it's not ready for primetime, as I expect you know), yet you speak as if it is no longer in Beta. Am I missing something? Jon
I'm really interested in using NUnit I've read all about it and I'm starting to really get the hang of it but I have some questions. In terms of the whole concept what concept is used when deside when a class is a test fixture or not? At first I thought that
code you were writing would have it's one test cases within it's classes, but this would mean that test cases would be public to an classes that use my code, so... I startting to think that a completely seperate class or even class library is used for all
testing. I know that I would not like test classes to appear in my code for any classes that use or derived from my class library. Pretty much like how NUnitAsp works. But the tests as a seperate class library only allow programmers to test the public functions
of a class and non of the private or protected. Is this how it should be? I'm thinking the seperate class library is the best way to go. But I'm looking for a second opinion. I've read so much about nunit and how to program with it, but I can't seem to find
anything in terms of these practices. Would someone please inform me.
Thank you for your time,
DissidenceTSB ASP.NET C# programmer since July 14, 2003
"I don't fear computers , I fear lack of them" - Isaac Asimov
None
0 Points
24 Posts
Unit Tests = Best Practices
May 14, 2004 04:07 PM|meierk|LINK
None
0 Points
24 Posts
Re: Unit Tests = Best Practices
May 17, 2004 04:30 PM|meierk|LINK
Member
10 Points
180 Posts
Microsoft
Re: Unit Tests = Best Practices
Jun 04, 2004 01:01 AM|swalther|LINK
Member
12 Points
116 Posts
Re: Unit Tests = Best Practices
Jun 04, 2004 10:49 AM|AndresS|LINK
This posting is provided "AS IS" with no warranties, and confers no rights.
None
0 Points
2 Posts
Re: Unit Tests = Best Practices
Jun 07, 2004 12:20 PM|SteveHurcombe|LINK
None
0 Points
24 Posts
Re: Unit Tests = Best Practices
Jun 07, 2004 12:52 PM|meierk|LINK
None
0 Points
11 Posts
Re: Unit Tests = Best Practices
Jun 08, 2004 08:26 AM|jonogden|LINK
None
0 Points
45 Posts
Re: Unit Tests = Best Practices
Sep 15, 2004 11:15 PM|DissidenceTSB|LINK
DissidenceTSB
ASP.NET C# programmer since July 14, 2003
"I don't fear computers , I fear lack of them" - Isaac Asimov
"Trust your technolust" - Hackers