I don’t use the GUI much at all. I
use the testdriven.net for interactive and cruise control for the rest.
Thanks,
David
BTW, I installed Vista
yesterday. I can envision about how to change ccnet to be windows gadget and be
more effective, but that is another subject all together.
Thanks for your feedback, I would be interested to
hear everybodies thoughts on the GUI. Do they use it much, do they prefer
the NUnit GUI or ZaneBug GUI, if they could run MbUnit on these GUI's would
they prefer that?
Let me know your throughts
On 7/12/06, P. van
der Velde <[EMAIL PROTECTED]>
wrote:
Hi All
I've been using MbUnit for a few weeks now and I must say it's a great
testing framework. Slowly I'm finding good ways of doing things and I
like it a lot.
I'm having some issues with both the GUI and the Html reports.
First off the UI. Every time I load my project I get the attached error
message. No idea why that happens. Mind you the project loads fine, the
tree is populated and everything still works so I'm all happy.
The second thing about the UI is that you can't load two of them at the
same time. Normally this is not an issue except if I'm debugging with
VS. Normally I will have a Mbunit GUI open to do my normal tests. If I
then start debugging VS automatically opens an other instance so that I
can run the unit tests and step through them in the debugger. The
problem is though that you can't open another version of the GUI because
some assemblies are locked (I think the QuickGraph ones).
The last thing is that the tree can be very confusing. I personally
don't use the different categories (author, severity, ...), I only use
the namespace part so it would be very nice if we could turn the
non-used elements of as they distract from the rest of the tree.
Oh and one more thing. Would it be possible to add a top level node to
the tree that will contain the different test assemblies as their
children. That way you can run all the tests in all the assemblies with
a single click. Now you have to run the tests for each assembly separately.
The Html reports have some other issues with them. The main problem is
that the order of the tests is random. It would be very nice if the
tests were alphabetically ordered (by namespace). Also there seems to be
some duplication. I'm currently testing 2 assemblies and the report
looks like:
Total score for all the tests
Total score for the first assembly
....
Result for unit test fixture(s) (for both assemblies)
....
Total score for the second assembly
....
Result for unit test fixture(s) (for both assemblies)
....
So the results are displayed twice which makes it very confusing.
Also as a little nitpick the original G-unit logo is still in the html
reports ;-)
Anyway thanks for a cool testing framework.
Regards
Petrik
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "MbUnit.User" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/MbUnitUser
-~----------~----~----~----~------~----~------~--~---
|
