|
Post by horstmelch on Aug 2, 2006 7:42:02 GMT -5
Hello, First, thanks alot for SimplyVbUnit and vbCorLib. I'm using vbCorLib for about a week and want to thank you for sharing these wonderful projects. There is so much stuff to learn, but it's fun! Also, I had never really looked at unit testing until yesterday, when I started my first project using SimplyVBUnit. I'm really amazed how well this is working and coded all night. Every VB coder should be forced to use SimplyVBUnit for a day - you would have a hard time keeping up with the "Thank you!" emails . I think I remember that there were unit tests in the vbCorLib source code at some time, but they are no longer included in the current release. I sure could learn a lot from your tests and would like to ask you if you could provide the unit tests for the current release again, please? Greetings Horst
|
|
|
Post by Kelly Ethridge on Aug 2, 2006 14:17:40 GMT -5
Hello,
Thanks for the kind words. I'm glad these things have been helpful!
I stopped including unit tests because I thought they were getting in the way of most people, but I can put them back in. I will include them in the 2.0 release. Until then I will put together a version 1.5.5 release set and post them on source forge.
Again, thanks!
Kelly
|
|
|
Post by horstmelch on Aug 2, 2006 15:04:00 GMT -5
That's perfect. Thanks a lot, Kelly!
Alex
|
|
|
Post by Kelly Ethridge on Aug 2, 2006 15:50:18 GMT -5
Hello,
Well that wasn't nearly as hard as I expected, so I'm sure I missed something. I have posted a zip file at source forge. It does require SimplyVBUnit v2.x. Let me know if you were successful setting it up.
Thanks, Kelly
|
|
|
Post by horstmelch on Aug 7, 2006 17:40:27 GMT -5
I had downloaded the unit tests as soon as you published them and have no problems running the tests except for compile errors caused by "comparer.Default" in the code. It was extremely helpful to have so many examples and I could improve my own unit test a lot - thanks! Also, the unit tests provide useful documentation. I had some problems testing asynchronous code, but my current solution is ok and maybe I can improve it after you release the unit tests for System.Net.Sockets . I'm really looking forward to these new classes. On my computers I’m the latest VBCorLib binary from SourceForge and its working fine. Maybe it’s just me, but I couldn’t compile the sources without breaking binary compatibility (I had referenced the provided binary as compatible library). That’s no problem at all, but I thought I’d let you know. Is there a way to donate to this project? I’m not skilled enough to contribute code, but wouldn’t hesitate to click a donate button. It would also make me feel better when asking questions about the library – and I still have a lot of these . Thanks for posting the unit tests so quickly!
|
|
|
Post by Kelly Ethridge on Aug 7, 2006 17:51:13 GMT -5
Hello!
You can solve the Compare problem by changing the priority in your Program References. There is a Comparer function that is exposed by both SimplyVBUnit and VBCorLib. The unit test is getting the SimplyVBUnit version because I didn't directly specify which version to get. If you move the VBCorLib reference above the SimplyVBUnitLib reference all should be well.
And I appreciate your offer of a donation. I never considered it because the original intent of this project (besides the fun) was to give back to the open source community from which I had taken. That makes it sound like I just stole everything lol.
Again, thanks! Kelly
|
|
|
Post by horstmelch on Aug 7, 2006 18:13:36 GMT -5
Hi,
Thanks for the explanation, it compiles now.
|
|