nunit / nunit/docs

Documentation needed about how to write a "where" statement for test cases resulting from TestCase attribute or TestFixture parameters

Open
#138 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Dockerfile
Stars
600
Forks
158
Avg merge
16h 8m
Merged PRs (30d)
21

Description

Please, can you write a couple of more examples in the documentation about the Test Selection Language about how to select tests resulting from TestCase attribute or TestFixture various constructing values etc.
For example I have a test that I want to select Test.ClipboardTests("no").TestBug345. I see this full name by doing the following on the assembly:

using (ITestEngine engine = TestEngineActivator.CreateInstance(true))
{
     engine.WorkDirectory = Environment.CurrentDirectory;
     engine.InternalTraceLevel = InternalTraceLevel.Verbose;

     TestPackage package = MakeTestPackage(assemblyName);
     ITestRunner runner = engine.GetRunner(package);
     return runner.Explore(TestFilter.Empty);
} 

The ClipboardTests test fixture has these attributes:

[TestFixture("en-US")]
[TestFixture("no")]
public  class ClipboardTests{
.
.
.
}

I have been trying to single out that test when running the command line by using:
--where="test=~/.*Test.ClipboardTests(\"no\").TestBug345.*/"
However, that does not work.
Of course, if I do --where="test=~/.*Test.ClipboardTests.*/", then I get all the tests in that fixture.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Test Selection Language documentation and its command-line --where entry point. Use the shown TestFixture constructor values and TestBug345 example to add examples for selecting tests produced by TestCase and TestFixture parameters. Done means the documentation explains the appropriate filter syntax for the specific test and the broader fixture selection.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
cli, documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.