Using TextFixture attribute with parameters doesn't print the parameters in the output

Bug #414073 reported by cliff v.
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
NUnit V2
Status tracked in Trunk
2.5
Fix Released
Medium
Charlie Poole
Trunk
Fix Released
Medium
Charlie Poole

Bug Description

Hi,

when using the following:

    [TestFixture(1)]
    [TestFixture(2)]
    public class NoPrinting
    {
        public NoPrinting( int id)
        {

        }

        [Test]public void Simple()
        {
            Assert.Fail();
        }
    }

you get this output:

TestCase 'NUnit.Tests.Integration.NoPrinting.Simple' failed:
 Integration\NUnit.cs(42,0): at NUnit.Tests.Integration.NoPrinting.Simple()

TestCase 'NUnit.Tests.Integration.NoPrinting.Simple' failed:
 Integration\NUnit.cs(42,0): at NUnit.Tests.Integration.NoPrinting.Simple()

With this, you have no idea what the values were that caused the fixture to fail. I'd expect to see the similar output that's generated when you use TestCase...()

cliff

Revision history for this message
Jamie Cansdale (jcansdale) wrote :

Are you saying you would expect the test names to be:

NUnit.Tests.Integration.NoPrinting(1).Simple()
NUnit.Tests.Integration.NoPrinting(2).Simple()

?

Revision history for this message
cliff v. (powerdude) wrote : Re: [Bug 414073] Re: Using TextFixture attribute with parameters doesn't print the parameters in the output

yes!!

On Sat, Aug 15, 2009 at 11:34 AM, Jamie Cansdale <email address hidden>wrote:

> Are you saying you would expect the test names to be:
>
> NUnit.Tests.Integration.NoPrinting(1).Simple()
> NUnit.Tests.Integration.NoPrinting(2).Simple()
>
> ?
>
> --
> Using TextFixture attribute with parameters doesn't print the parameters in
> the output
> https://bugs.launchpad.net/bugs/414073
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in NUnit Test Framework 2.5: New
>
> Bug description:
> Hi,
>
> when using the following:
>
> [TestFixture(1)]
> [TestFixture(2)]
> public class NoPrinting
> {
> public NoPrinting( int id)
> {
>
> }
>
> [Test]public void Simple()
> {
> Assert.Fail();
> }
> }
>
> you get this output:
>
> TestCase 'NUnit.Tests.Integration.NoPrinting.Simple' failed:
> Integration\NUnit.cs(42,0): at
> NUnit.Tests.Integration.NoPrinting.Simple()
>
> TestCase 'NUnit.Tests.Integration.NoPrinting.Simple' failed:
> Integration\NUnit.cs(42,0): at
> NUnit.Tests.Integration.NoPrinting.Simple()
>
> With this, you have no idea what the values were that caused the fixture to
> fail. I'd expect to see the similar output that's generated when you use
> TestCase...()
>
> cliff
>

--
thanks

cliff

Revision history for this message
Charlie Poole (charlie.poole) wrote : RE: [Bug 414073] Re: Using TextFixture attribute with parametersdoesn't print the parameters in the output

That makes sense... the fixture name is available when we create
the test method, so it should be relatively easy.

Charlie

> -----Original Message-----
> From: <email address hidden> [mailto:<email address hidden>] On
> Behalf Of cliff v.
> Sent: Saturday, August 15, 2009 8:46 AM
> To: <email address hidden>
> Subject: Re: [Bug 414073] Re: Using TextFixture attribute
> with parametersdoesn't print the parameters in the output
>
> yes!!
>
> On Sat, Aug 15, 2009 at 11:34 AM, Jamie Cansdale
> <email address hidden>wrote:
>
> > Are you saying you would expect the test names to be:
> >
> > NUnit.Tests.Integration.NoPrinting(1).Simple()
> > NUnit.Tests.Integration.NoPrinting(2).Simple()
> >
> > ?
> >
> > --
> > Using TextFixture attribute with parameters doesn't print the
> > parameters in the output
> > https://bugs.launchpad.net/bugs/414073
> > You received this bug notification because you are a direct
> subscriber
> > of the bug.
> >
> > Status in NUnit Test Framework 2.5: New
> >
> > Bug description:
> > Hi,
> >
> > when using the following:
> >
> > [TestFixture(1)]
> > [TestFixture(2)]
> > public class NoPrinting
> > {
> > public NoPrinting( int id)
> > {
> >
> > }
> >
> > [Test]public void Simple()
> > {
> > Assert.Fail();
> > }
> > }
> >
> > you get this output:
> >
> > TestCase 'NUnit.Tests.Integration.NoPrinting.Simple' failed:
> > Integration\NUnit.cs(42,0): at
> > NUnit.Tests.Integration.NoPrinting.Simple()
> >
> > TestCase 'NUnit.Tests.Integration.NoPrinting.Simple' failed:
> > Integration\NUnit.cs(42,0): at
> > NUnit.Tests.Integration.NoPrinting.Simple()
> >
> > With this, you have no idea what the values were that caused the
> > fixture to fail. I'd expect to see the similar output that's
> > generated when you use
> > TestCase...()
> >
> > cliff
> >
>
>
> --
> thanks
>
> cliff
>
> --
> Using TextFixture attribute with parameters doesn't print the
> parameters in the output
> https://bugs.launchpad.net/bugs/414073
> You received this bug notification because you are the
> registrant for NUnit 2.5.
>

Changed in nunit-2.5:
importance: Undecided → Medium
status: New → Won't Fix
status: Won't Fix → Confirmed
assignee: nobody → Charlie Poole (charlie.poole)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.