nunit / nunit/docs

Showing the actual value of complex type parameter with NUnit in the reports

Open
#244 3 comments 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

Hi guys,
first forgive me if this is not the right place to ask questions, but to me it is most suitable.

I remember that I've seen somewhere in the web about showing actual value of complex type parameter. Bear with me while I explain what I mean.

With this test:

[Test]
public void Post_StakeToDifferetnSelectionsViaBetsBetIdEndpoint_ReturnsCorrectData(
   [ValueSource(typeof(JsonContextCache), nameof(JsonContextCache.RandomThreeUniqueSelecionIds))] string[] selectionIds,
   [ValueSource(typeof(TestData), nameof(TestData.OddStyles))] OddStyle oddStyle, 
   [Values(true, false)] bool logged)

My report is generated as following:

Post_StakeToDifferetnSelectionsViaBetsBetIdEndpoint_ReturnsCorrectData(System.String[],European,True)
This also applies for user defined custom types as well.

What I want to achieve however is showing the actual values of this complex type parameters:
Post_StakeToDifferetnSelectionsViaBetsBetIdEndpoint_ReturnsCorrectData(["1","2","3"],European,True)

Is it possible using nUnit or I am mistaken that I've seeing this in the web?
I've also asked that question on SO - https://stackoverflow.com/questions/47649312/showing-the-actual-value-of-complex-type-parameter-with-nunit-in-the-reports
Thanks,
kuskmen

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 linked Stack Overflow question and NUnit's documentation for parameterized tests and report naming. Confirm whether complex parameter values are supported in reports, then document the supported behavior or limitation using the test example in this issue. Done means the documentation gives a clear answer and an example or workaround.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
documentation, testing
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.