nunit / nunit/docs

Issues with Implementing Values Attribute and Customizing Name Format

Open
#305 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

This may be an issue with documentation(or a feature request, i'll lean on the side that i'm missing something), however I am currently running into an issue that i'm having difficulty finding a workaround.

Currently I am able to use the Values attribute correctly, however i am not able to use the Values attribute in conjuncture with a custom name assigned to the collection of test cases.
I've attempted TestCaseSource, however I am unable to implement this change using the Values attribute (with it's current restrictions).

Simple Business Description:

  • I have a test with 3+ parameters (all using the value property, (all enums in this case))
  • I have Label that is generated, however it does not accurately convey what that test is doing.

Desired Result:

  • Have the parameters used displayed along with the name of the variable they're assigned to.

Ex:
The shared enum has 3 values, All, Some, and None.
Test will display as:
Test("Param1Name : All, Param2Name: Some, Param3Name: None")

Instead, I am getting:
Test(All,Some,None)

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

Review the documentation for Values, TestCaseSource, and generated test names first; the issue does not name a file or test. Determine whether the requested parameter-name format is a documentation change or a feature request, and define the expected displayed format before proceeding.

Written by the indexing model from the issue text.

Assessment

Domain
testing
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.