NUnitLite Forum Rss Feed

NEW POST: NUnitLite for Silverlight

erichexter — Tue, 08 Apr 2008 02:02:31 GMT

Do you have the console runner ported to silverlight as well?

NEW POST: NUnitLite for Silverlight

mwatts42 — Thu, 13 Mar 2008 21:55:34 GMT

sagostinho wrote:
Hello there,

I'm doing some development in Silverlight 2.0, but due to the sandbox/architecture I can't use any of the existing frameworks, including NUnitLite. Is there anybody working on this?
If not I would like to try porting NUnitLite to Silverlight.

Any thoughts about this out there?

Best regards!

I have already ported it and have the basics working and passing unit tests. I have also contacted Charlie to try and determin how this should be contributed back to the project but have not yet heard back from him.

NEW POST: NUnitLite for Silverlight

sagostinho — Wed, 05 Mar 2008 18:49:35 GMT

Hello there,

I'm doing some development in Silverlight 2.0, but due to the sandbox/architecture I can't use any of the existing frameworks, including NUnitLite. Is there anybody working on this?
If not I would like to try porting NUnitLite to Silverlight.

Any thoughts about this out there?

Best regards!

NEW POST: works with XNA

cpoole — Tue, 21 Aug 2007 14:39:30 GMT

Good to hear! I'm hoping to hear from folks using it on other platforms and I'll start a page listing them.

If you come up with ideas for improvement, please let us know - either here or on the NUnitLite mailing list at http://groups.google.com/group/nunitlite.

Charlie

NEW POST: works with XNA

TriangleMan — Tue, 21 Aug 2007 09:21:01 GMT

Just thought I'd report that NUnitLite seems to work great with XNA (Microsoft's framework for .NET game development) including on the Xbox, where NUnit (heavy) is missing the system components that it needs. Thanks for building this project!

NEW POST: Compact Framework Support

cpoole — Thu, 09 Aug 2007 02:04:22 GMT

I haven't been keeping up with the forums here and haven't been updating NUnitLite either since I have focused on the new NUnit releases. However, I'm now getting the code base updated and preparing for a release and I have set up a mailing list, which I think will work better for me in having discussions.

Regarding the problems with .NET CF, I have a build that works on my own machine and I'll be updating the code and putting out an 0.1 release soon. The issues are easy enough to resolve:

EmptyTypes is just new Type0 - I added a static Reflect.EmptyTypes to make it easy

Environment.NewLine is trickier than you might think. I used another static and initialized it to "\r\n" if PocketPC or WindowsCE is defined. Otherwise, I initialize it to Environment.NewLine. I'm not sure that will work on any compact frameworks on Linux - if there even are any. :-(

GetTypeArray() is easy to implement. I put it into Reflect.cs.

GetConstructor() - I haven't seen this problem. Maybe it's just a side-effect of the EmtpyTypes problem.

I'd appreciate it if we could move this discussion to the new mailing list on GoogleGroups. You can join it at http://groups.google.com/group/nunitlite

I'll also be announcing there when I update the code - I made a few recent updates but they don't include the stuff above yet.

Charlie

NEW POST: Compact Framework Support

alanbrito — Tue, 31 Jul 2007 13:10:58 GMT

Here is our source for MobileUnit at SourceForge:

http://sourceforge.net/projects/mobileunit

It is a lightweight version of nunit with a GUI test runner and some .NET Forms testing convenience classes. You will find a sample test project in the downloads section.

Compact Framework Support:

alanbrito — Tue, 06 Feb 2007 20:51:08 GMT

{quote} Hi, I am a Mobile Developer and am very interested in a NUnit Test Framework that supports Compact Framework 2. {quote} I have ported the entire nunit core framework down to CF 2. I have a GUI test runner that runs on either the emulator or an actual device. I also created several gui testing utilities for convenience. Things like similating button clicks, keyboard input, etc... We have been successfully using this for a few months now, and it is a huge benefit to be able to do true TDD on the mobile platform. It is very easy to use. If you are interested in this, I can email you the entire source code with instructions. I've spoken a couple of times with Charlie about integrating what I have with nunitlite, but we have both apparently been very busy. My email address is alan.baldwin [at] gmail_dot_com. Regards, -Alan-

Developer Forum: RE: Compact Framework Support

dclavey — Mon, 08 Jan 2007 14:57:02 GMT

OK I have the following solution as suggested by: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=737835&SiteID=1 Change the following code: public static object Construct(Type type, params object[] args) { Type[] argTypes; if (args == null) { args = new object[0]; //Was argTypes = Type.EmptyTypes; argTypes = new Type[0]; } else { //Was argTypes = Type.GetTypeArray(args); argTypes = new Type[args.Length]; for (int x = 0; x < args.Length; x++) { argTypes[x] = args[x].GetType(); } } ConstructorInfo ctor = GetConstructor(type, argTypes); return ctor.Invoke(args); }

Developer Forum: RE: Compact Framework Support

dclavey — Fri, 05 Jan 2007 15:41:33 GMT

ok, after some testing the biggest problem with CF2 version is in the Reflect.cs class, construct function: public static object Construct(Type type, params object[] args) { Type[] argTypes; if (args == null) { args = new object[0]; argTypes = Type.EmptyTypes; } else { argTypes = Type.GetTypeArray(args); } ConstructorInfo ctor = GetConstructor(type, argTypes); return ctor.Invoke(args); } The expressions: Type.EmptyTypes; Type.GetTypeArray(args); are not valid for CF2, I guess I could replace Type.EmptyTypes with new Type[0]. but what to replace GetTypeArray with is the problem. Type does support GetType, but expects you to tell it what type to get! Any Solutions?

Developer Forum: Compact Framework Support

dclavey — Fri, 05 Jan 2007 11:41:35 GMT

Hi, I am a Mobile Developer and am very interested in a NUnit Test Framework that supports Compact Framework 2. History - I have tried cross compiling both the CSUnit and the NUnit projects - but they both use features which are not supported by CF. I have just tried cross compiling your NUnitLite code under CF2 and was surprised that I had a few problems with Change Set: 11989: Type.EmptyTypes - not supported Type.GetTypeArray(args) - not supported ConstructorInfo ctor = GetConstructor( type, argTypes ) - not supported ctor.Invoke(args) - not supported Environment.NewLine - not supported (all over the code) I have put temporary fixes in, but have not yet successfully run a test on a Mobile 5 device - probably hours away. I would be very interested in developing a Visual Interface (Runner) to NUnitLite that works on Phone / Pocket PC different screen configs etc. I like the way CSUnit looks (reports problems within tree itself). I think its important that a Red - Green tester interface exists. I presume that CF is still a target? Do you need a Mobile Tester?

User Forum: RE: Latest Build: 5644 has some compile error message...

cpoole — Tue, 14 Nov 2006 09:39:59 GMT

OK, I checked it out and back in, which should fix it. It doesn't seem to handle working disconnected very cleanly.

User Forum: RE: Latest Build: 5644 has some compile error message...

chicken867 — Mon, 13 Nov 2006 10:43:54 GMT

I've try the latest release (#10946), too... has the same problem. The project file of NUnitLite do not include those two files: Msgs.cs Framework/MsgUtils.cs everything is ok after include those 2 files into project :D

User Forum: RE: Latest Build: 5644 has some compile error message...

chicken867 — Mon, 13 Nov 2006 10:28:25 GMT

Thanks a lot, I got the problem in build #5644 project. I open the /NUnitLite.sln in visual studio 2005, and I found in NUnitLite project do not include those two files in project: Msgs.cs Framework/MsgUtils.cs After I include them into project and build, everything is ok now :D

User Forum: RE: Latest Build: 5644 has some compile error message...

cpoole — Sat, 11 Nov 2006 22:16:54 GMT

I just downloaded the zip myself, and the files are definitely there. Of course, they aren't in your command line so they won't be found. Sorry to have taken so long to respond. I need to set things up to get notified when someone posts. Charlie

User Forum: Latest Build: 5644 has some compile error message...

chicken867 — Fri, 27 Oct 2006 06:13:50 GMT

First, NUnitLite is a great idea, work very good in my web site project. I wrote some test fixture in App_Code, and show test result in another *.aspx page. When I download build #5644 and compile it, I got some messages, seems the source code lost 2 classes (class Msgs, class MsgUtils) ------ Rebuild All started: Project: NUnitLite, Configuration: Debug Any CPU ------ D:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Csc.exe /noconfig /nowarn:1701,1702 /errorreport:prompt /warn:4 /define:DEBUG;TRACE /reference:D:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Data.dll /reference:D:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.dll /reference:D:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Drawing.dll /reference:D:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Xml.dll /debug+ /debug:full /optimize- /out:obj\Debug\NUnitLite.dll /target:library Constraints\BinaryOperations.cs Constraints\CollectionConstraints.cs Constraints\ComparisonConstraints.cs Constraints\Constraint.cs Constraints\ConstraintBuilder.cs Constraints\EmptyConstraint.cs Constraints\EqualConstraint.cs Constraints\NotConstraint.cs Constraints\SameAsConstraint.cs Constraints\StringConstraints.cs Constraints\TypeConstraints.cs Framework\Attributes.cs Framework\Exceptions.cs Framework\IExpectException.cs Framework\InvalidTestCase.cs Framework\Reflect.cs Framework\SyntaxHelpers.cs MessageWriter.cs Framework\Assert.cs Framework\StackFilter.cs Framework\TextMessageWriter.cs Framework\NullListener.cs Framework\ProxyTestCase.cs Runner\CommandLineOptions.cs Runner\ResultSummary.cs Framework\TestListener.cs Framework\TestProgressListener.cs Runner\TestLoader.cs Runner\TestRunner.cs Framework\TestSuite.cs Framework\ITest.cs Properties\AssemblyInfo.cs Framework\TestCase.cs Framework\TestResult.cs Runner\ConsoleUI.cs E:\Home\MyDesktop\NUnit.2.2.8\NUnitLite-5644\NUnitLite\src\NUnitLite\Constraints\StringConstraints.cs(75,41): error CS0103: The name 'Msgs' does not exist in the current context E:\Home\MyDesktop\NUnit.2.2.8\NUnitLite-5644\NUnitLite\src\NUnitLite\Constraints\StringConstraints.cs(77,41): error CS0103: The name 'Msgs' does not exist in the current context E:\Home\MyDesktop\NUnit.2.2.8\NUnitLite-5644\NUnitLite\src\NUnitLite\Constraints\StringConstraints.cs(93,41): error CS0103: The name 'Msgs' does not exist in the current context E:\Home\MyDesktop\NUnit.2.2.8\NUnitLite-5644\NUnitLite\src\NUnitLite\Constraints\StringConstraints.cs(95,41): error CS0103: The name 'Msgs' does not exist in the current context E:\Home\MyDesktop\NUnit.2.2.8\NUnitLite-5644\NUnitLite\src\NUnitLite\Constraints\StringConstraints.cs(111,41): error CS0103: The name 'Msgs' does not exist in the current context E:\Home\MyDesktop\NUnit.2.2.8\NUnitLite-5644\NUnitLite\src\NUnitLite\Constraints\StringConstraints.cs(113,41): error CS0103: The name 'Msgs' does not exist in the current context E:\Home\MyDesktop\NUnit.2.2.8\NUnitLite-5644\NUnitLite\src\NUnitLite\Framework\TextMessageWriter.cs(104,19): error CS0103: The name 'Msgs' does not exist in the current context E:\Home\MyDesktop\NUnit.2.2.8\NUnitLite-5644\NUnitLite\src\NUnitLite\Framework\TextMessageWriter.cs(107,24): error CS0103: The name 'MsgUtils' does not exist in the current context E:\Home\MyDesktop\NUnit.2.2.8\NUnitLite-5644\NUnitLite\src\NUnitLite\Framework\TextMessageWriter.cs(271,19): error CS0103: The name 'Msgs' does not exist in the current context E:\Home\MyDesktop\NUnit.2.2.8\NUnitLite-5644\NUnitLite\src\NUnitLite\Framework\TextMessageWriter.cs(282,19): error CS0103: The name 'Msgs' does not exist in the current context E:\Home\MyDesktop\NUnit.2.2.8\NUnitLite-5644\NUnitLite\src\NUnitLite\Framework\TextMessageWriter.cs(293,19): error CS0103: The name 'Msgs' does not exist in the current context E:\Home\MyDesktop\NUnit.2.2.8\NUnitLite-5644\NUnitLite\src\NUnitLite\Framework\TextMessageWriter.cs(301,49): error CS0103: The name 'Msgs' does not exist in the current context E:\Home\MyDesktop\NUnit.2.2.8\NUnitLite-5644\NUnitLite\src\NUnitLite\Constraints\EqualConstraint.cs(229,28): error CS0103: The name 'MsgUtils' does not exist in the current context E:\Home\MyDesktop\NUnit.2.2.8\NUnitLite-5644\NUnitLite\src\NUnitLite\Constraints\EqualConstraint.cs(232,41): error CS0103: The name 'Msgs' does not exist in the current context E:\Home\MyDesktop\NUnit.2.2.8\NUnitLite-5644\NUnitLite\src\NUnitLite\Constraints\EqualConstraint.cs(234,41): error CS0103: The name 'Msgs' does not exist in the current context E:\Home\MyDesktop\NUnit.2.2.8\NUnitLite-5644\NUnitLite\src\NUnitLite\Constraints\EqualConstraint.cs(279,35): error CS0103: The name 'MsgUtils' does not exist in the current context E:\Home\MyDesktop\NUnit.2.2.8\NUnitLite-5644\NUnitLite\src\NUnitLite\Constraints\EqualConstraint.cs(280,33): error CS0103: The name 'MsgUtils' does not exist in the current context E:\Home\MyDesktop\NUnit.2.2.8\NUnitLite-5644\NUnitLite\src\NUnitLite\Constraints\EqualConstraint.cs(283,49): error CS0103: The name 'Msgs' does not exist in the current context E:\Home\MyDesktop\NUnit.2.2.8\NUnitLite-5644\NUnitLite\src\NUnitLite\Constraints\EqualConstraint.cs(285,49): error CS0103: The name 'Msgs' does not exist in the current context E:\Home\MyDesktop\NUnit.2.2.8\NUnitLite-5644\NUnitLite\src\NUnitLite\Constraints\EqualConstraint.cs(311,37): error CS0103: The name 'MsgUtils' does not exist in the current context E:\Home\MyDesktop\NUnit.2.2.8\NUnitLite-5644\NUnitLite\src\NUnitLite\Constraints\EqualConstraint.cs(314,49): error CS0103: The name 'Msgs' does not exist in the current context E:\Home\MyDesktop\NUnit.2.2.8\NUnitLite-5644\NUnitLite\src\NUnitLite\Constraints\EqualConstraint.cs(314,70): error CS0103: The name 'MsgUtils' does not exist in the current context E:\Home\MyDesktop\NUnit.2.2.8\NUnitLite-5644\NUnitLite\src\NUnitLite\Constraints\EqualConstraint.cs(318,39): error CS0103: The name 'MsgUtils' does not exist in the current context E:\Home\MyDesktop\NUnit.2.2.8\NUnitLite-5644\NUnitLite\src\NUnitLite\Constraints\EqualConstraint.cs(319,49): error CS0103: The name 'Msgs' does not exist in the current context E:\Home\MyDesktop\NUnit.2.2.8\NUnitLite-5644\NUnitLite\src\NUnitLite\Constraints\EqualConstraint.cs(320,21): error CS0103: The name 'MsgUtils' does not exist in the current context E:\Home\MyDesktop\NUnit.2.2.8\NUnitLite-5644\NUnitLite\src\NUnitLite\Constraints\EqualConstraint.cs(320,72): error CS0103: The name 'MsgUtils' does not exist in the current context E:\Home\MyDesktop\NUnit.2.2.8\NUnitLite-5644\NUnitLite\src\NUnitLite\Constraints\EqualConstraint.cs(326,37): error CS0103: The name 'Msgs' does not exist in the current context E:\Home\MyDesktop\NUnit.2.2.8\NUnitLite-5644\NUnitLite\src\NUnitLite\Constraints\EqualConstraint.cs(331,37): error CS0103: The name 'Msgs' does not exist in the current context E:\Home\MyDesktop\NUnit.2.2.8\NUnitLite-5644\NUnitLite\src\NUnitLite\Constraints\EqualConstraint.cs(370,39): error CS0103: The name 'MsgUtils' does not exist in the current context Compile complete -- 29 errors, 0 warnings ========== Rebuild All: 0 succeeded, 1 failed, 0 skipped ==========

Developer Forum: RE: Assert.That

cpoole — Wed, 30 Aug 2006 01:37:49 GMT

I set up a small test and managed to get the following test to run using C++/CLI... [TestFixture] public ref class AssertTests { public: [Test] void AssertTest() { Assert::That(2+2, Is::EqualTo(4)); } }; This requires more testing, but I'm thinking that the new C++/CLI is more forgiving than the older managed C++.

Developer Forum: RE: Assert.That

cpoole — Wed, 30 Aug 2006 01:04:27 GMT

Well, let's see... First the EqualityMatcher has to be constructed. The constructor takes an object and you're giving it an object, so no problem. Next a proper That overload needs to be identified. In C#, the int is automatically boxed and the That( object ) method is used. In C++, we would need to have That( int ), which would redirect to That( object ). This is the same as current NUnit. Now, lets say you called the following, in C++ Assert.That( 2+2, new EqualMather( 4 ) ); This has the added problem that there is no int constructor for EqualMatcher. So yes, we would be forced to add a new constructor of type int to EqualMatcher. But again, this seems no worse than what we already do for Assert. Note that we don't have to handle ALL possible casts. If we cover double, then float will be handled. Long takes care of int and short. And so on... Of course, this is speculative till I get a chance to write some C++ tests Charlie

Developer Forum: RE: Assert.That

trayburn — Wed, 30 Aug 2006 00:25:45 GMT

I guess I'm not certain how the matchers will cleanly handle the following example (I'm moving fast tonight, if there is syntax errors, please forgive me): int myValInt = 10; string myValString = "To be or not to be"; Assert.That(myValInt, new EqualityMatcher(myValString)); Unlike in the Assert model of NUnit itself, there is no way to ensure compile-time type correctness. And handling all various odd-ball casts in each and every Matcher seems a little crazy. Sure we can likely abstract alot of it into base classes which the Matcher's share, but it's going to be "interesting" to get right. Tim

User Forum: Test of Rmail

cpoole — Tue, 29 Aug 2006 21:53:53 GMT

Testing forwarding of the RSS feed via email