Hello All,

 

 

We’re just starting to run automated tests on our build system and are using categories to selectively run tests depending upon the time of day that the build is being run. Whilst this is a fine idea in theory, the problem we’re having is that it doesn’t work. We’re using CruiseControl.NET 0.91, NAnt 0.85.1932.0, and NUnit 2.2.0 on Win2k3 Standard.

 

The problems are as follows.

 

If we follow the example in the documentation at http://nant.sourceforge.net/release/latest/help/types/categoryset.html, e.g.

 

<categories>

            <include name=”AllBuilds”/>

            <exclude name=”Obsolete”/>

</categories>

 

what actually happens is that the specified categories are completely ignored, and all tests are run regardless of their category… this of course causes the builds to fail because some of the “Obsolete” tests no longer work. It also means that our “Nightly” tests run – these are nightly mainly because they are long running, so we definitely don’t want to run them on every build.

 

Now, the above documentation (which I know is preliminary) clearly states that (i) neither <include> nor <exclude> have name attributes, and (ii) that <include> and <exclude> contain a list of <category> items. However, if we do the following:

 

<categories>

            <include>

                        <category name=”AllBuilds”/>

            </include>

            <exclude>

                        <category name=”Obsolete”/>

            </exclude>

</categories>

 

it still doesn’t work, and fails with the following error message:

 

'name' is a required attribute of < ... />.

 

So we’re a bit stumped at the moment unfortunately. If anybody knows how to make this work I’d be extremely grateful to hear from you.

 

Also, whilst we’re on the subject of documentation, at the top of http://nant.sourceforge.net/release/latest/help/tasks/nunit2.html it says “In order to run a test assembly built with NUnit 2.0 or 2.1 using the NAnt <nunit2> task, you must add the following node to your test config file”, but we’ve no idea which “test configuration file” it’s talking about – we don’t have a configuration file for our tests, so what does this mean? Again, I realise this is preliminary documentation, however if anybody does have any idea what it means, again I’d be grateful to hear from you.

 

 

Many thanks,

Bart

 

 

======================

Bart Read

Software Engineer

Red Gate Software Ltd

+44 (0) 870 160 0037 ext 31

======================

 

Reply via email to