DZone
Performance Zone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
  • Refcardz
  • Trend Reports
  • Webinars
  • Zones
  • |
    • Agile
    • AI
    • Big Data
    • Cloud
    • Database
    • DevOps
    • Integration
    • IoT
    • Java
    • Microservices
    • Open Source
    • Performance
    • Security
    • Web Dev
DZone > Performance Zone > Command Line Usability With dotnet Test

Command Line Usability With dotnet Test

I hate the new dotnet test command. It doesn't have good usability. It includes lots of duplicate info and makes it hard to find relevant info like failing tests.

Oren Eini user avatar by
Oren Eini
·
Apr. 09, 17 · Performance Zone · Opinion
Like (2)
Save
Tweet
3.39K Views

Join the DZone community and get the full member experience.

Join For Free

I hate the new “dotnet test” command.

I don’t think that anyone ever thought about looking at the output it generates for real projects.

For example, here is a section from the log output our fast tests:

image

There is so much crap here — including duplicate information and a whole bunch of mess that it is very hard to find relevant information.

For example, there is a failing test here. How long will it take you to find it?

Another important aspect for us is the fact that this will actually run the same process.

If you have something that will crash the test process, you’ll never get to see what is going on.

The picture below shows what a crash due to stack overflow looks like when using “dotnet test.”

image

As a result of this, we moved to dotnet xunit, which is a much better test runner.

image

We get color coding, including red for failing tests, so we don’t have to hunt them.

What is more important is that it will not hide crucial information from us because it feels like it. If there is a crash, we can actually see what happened.

image

I know it sounds trivial, but “dotnet test” doesn’t even have it.

Testing Command (computing) Usability

Published at DZone with permission of Oren Eini, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • What Are Microservices?
  • 12 Modern CSS Techniques For Older CSS Problems
  • Automation Testing vs. Manual Testing: What's the Difference?
  • What I Miss in Java, the Perspective of a Kotlin Developer

Comments

Performance Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • MVB Program
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends:

DZone.com is powered by 

AnswerHub logo