I got around the non-display of namespaces in test results by using
nested classes. There really isn't much gain other than naming, and I
haven't had any problems with the technique. Here's a sample output:
TestCase 'MbUnit v3.0.5.550/Servicing.Tests/Signatures/
signature_service/when_signatures_do_not_exist_for_the_conversion/
should_create_signature_entries_for_primary_and_non_guarantor_indirect_liabilities'
passed.
Namespace ConversionReprice
<TestFixture()> _
Public Class Signatures
<TestFixture()> _
Public Class signature_service
<TestFixture()> _
Public Class
when_signatures_do_not_exist_for_the_conversion
<Test()> _
Public Sub
should_create_signature_entries_for_primary_and_non_guarantor_indirect_liabilities
()
...
It would probably be cleaner syntax wise to use namespaces, but this
workaround is fine for me right now.
Dan Lash
On Feb 24, 3:47 pm, Jeff Brown <[email protected]> wrote:
> Yup. I have gone back and forth a few times regarding the
> representation of namespaces in test results. It's a tricky problem
> because it's ultimately context sensitive. There are reasonable cases
> for different levels of detail.
>
> I'm curious to hear what others think on this topic.
>
> On Feb 24, 2009, at 12:32 PM, ulu <[email protected]> wrote:
>
>
>
>
>
> > Hi Jeff,
>
> > Just guessing, wouldn't it be cool to see the test class' namespace
> > (instead of just the assembly name) in the test output window, as well
> > as in the report?
>
> > I'm trying to organize my tests into multiple namespaces, so that I
> > don't have to put all the context information in the test class name.
> > I'm just playing with the idea, maybe there are guidelines or
> > something?
>
> > What do the others think?
>
> > ulu
>
> > On Feb 15, 6:48 am, "Jeff Brown" <[email protected]> wrote:
> >> I'm starting to wrap up v3.0.6.
>
> >> I hope to get it released by the end of next week, then jump
> >> straight into
> >> v3.1 which will feature major architectural improvements.
>
> >> Please help us out by trying a recent nightly build
> >> from:http://ccnet.gallio.org/Distributables/
>
> >> Here's a summary of some of the bits that are new in v3.0.6:
>
> >>http://blog.bits-in-motion.com/2009/01/gallio-update.html
>
> >> To that list we may also add:
>
> >> * XmlSerializationAssert has been eliminated. Use the new Xml
> >> serialization
> >> assert methods Assert.IsXmlSerializableType, Assert.XmlSerialize,
> >> Assert.XmlDeserialize and Assert.XmlSerializeThenDeserialize instead.
>
> >> * Added Assert.IsSerializableType, Assert.Serialize,
> >> Assert.Deserialize,
> >> Assert.SerializeThenDeserialize and other methods to help test
> >> runtime
> >> object serialization.
>
> >> * Added Assert.IsFailurePending to enable the detection of whether
> >> the
> >> current Assert.Multiple block (or [MultipleAssertions] test) has
> >> already
> >> encountered a failure but not yet terminated.
>
> >> * Added Assert.Terminate and Assert.TerminateSilently to enable a
> >> test in
> >> progress to be terminated with a particular result code. Obviates
> >> the need
> >> to throw a new SilentTestException.
>
> >> * More improvements to contract verifiers including a new collection
> >> contract verifier.
>
> >> * Bunch of reflection layer fixes to improve stability and
> >> performance in R#
> >> and VSTS.
>
> >> * Added [Parallelizable] attribute. Can control degree of
> >> parallelism with
> >> [assembly: DegreeOfParallelism].
>
> >> * Default timeout is now 10 minutes for test cases and unlimited
> >> for test
> >> fixtures (used to be the other way around. Can override with
> >> [assembly:
> >> DefaultTestCaseTimeout]
>
> >> * Fixed a bug running under .Net Framework 2.0 pre-SP2.
>
> >> * Icarus debugging support and other improvements.
>
> >> * Echo supports Gallio project files.
>
> >> Jeff.- Hide quoted text -
>
> - Show quoted text -
--~--~---------~--~----~------------~-------~--~----~
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?hl=en
-~----------~----~----~----~------~----~------~--~---
