TestFixtures used by TestFixtureReference showing up in unexpected location in Icarus

[GoogleCodeExporter]

What steps will reproduce the problem? (see ExampleCode.cs)
1. Define a test fixture InnerFixture with some test.  Declare it inside a 
namespace.
2. Define a test fixture OuterFixture, which has a StaticTestFactory returning 
a TestFixtureReference to the InnerFixture.
3. Open Icarus and load the compiled test assembly

What is the expected output? What do you see instead?
  I expect InnerFixture to have 2 entries:
    1 inside the namespace where it is defined
    1 as a child of OuterFixture (similar to if a TestSuite is used)
  Observed output:
    Both InnerFixtures are inside the namespace.
    OuterFixture has no children.

What version of the product are you using? On what operating system?
  Gallio Icarus - Version 3.1 Build 397
  Windows XP SP3

Please provide any additional information below.
  The expected behaviour is observed if InnerFixture is not inside a namespace.
  The innerfixtures still behave at run-time as if they are children of the outerfixture ( InnerFixture is run by OuterFixture )

Original issue reported on code.google.com by tyr...@irdinc.com on 2 Sep 2010 at 10:54

Attachments:

• ExampleCode.cs

[GoogleCodeExporter]

Yeah, it's a bug in the way the tree is built for nested fixtures. It shouldn't 
affect the running of tests, but can cause the test selection filter to be 
wrong.

Original comment by grahamr...@gmail.com on 3 Sep 2010 at 9:14

• Changed state: Accepted
• Added labels: Type-Defect, Priority-Medium, Component-Icarus

[GoogleCodeExporter]

This looks like it's fixed in the version 3.2 build 601.  Thanks

Original comment by tyr...@irdinc.com on 27 Sep 2010 at 7:22