Daily Usage Issues

Test Case in separate column possible?

Started by GreenMoose on 3,571 views

[v3.12.0.15]

Is it possible to create a separate column for the test case when using e.g. NUnit's TestCase or TestCaseSource, or is this "out of reach" for NCrunch?

(My test names becomes quite long, and then I can't see the important part i.e. the test case).
A quirky workaround would be to right align the text I suppose.


Unrelated question: My "Shortened name" and "Name" columns both display the same thing (test name without namespace), what is the intention of these 2 ?

Thanks.
Under NUnit3, NCrunch is fully abstracted away from the TestCase/TestCaseSource generation system. It might be possible to infer the use of such a mechanism by deconstructing the test name, but there are drawbacks to such an approach in terms of future proofing and maintainability. I would recommend trying to address this problem by convention rather than tooling if at all possible.

Is there any chance you could give a screenshot showing the readability issue? We're considering making some improvements to the UI at the moment, and knowing where it falls short may help a bit.

The 'Shortened Name' column is identical to the name column in all but one situation: When rendering the name of a fixture under the 'Project, Fixture, Test' grouping option. In this situation, the shortened name does not include the fixture's namespace.
Here's screenshot when using 1 monitor (working from home, less often).
[img=https://i.imgur.com/3lSuL6l.png]Screenshot 1 horizontal monitor[/img]

Screenshot from office setup (3 monitors, test window is located on a secondary monitor standing vertically)

[img=https://i.imgur.com/eBVf95c.png]Screenshot vertical monitor[/img]
(I removed the server column for now since this solution is not using grid nodes, yet)

As you can see I am more interested in test cases in this scenario than the actual test name since I add test cases as work evolves (which NCrunch seems to have some issues with, a couple of bug reports submitted).

Maybe a neat solution would be to allow one ore several "custom" columns, where you can define the contents somehow with regex and placeholders?
E.g.

<customColums>
<column header="TestCase">
<regex input="$ShortenedName$" pattern=".*\((?<testCase>.*)\)$" text="\1"
</column>
</customColums>


Post a reply

Log in to reply.