Yet Another Use of a Unit Test Framework

Believe me, I understand TDD. I grok it. It is in my soul.

I also happen to believe (and know from experience) that unit test frameworks are valuable far beyond their use in TDD. Some of the best uses are for integration tests at the API level.

It is this coolness that makes it so handy to run a unit test harness as a load test run using VSTS. I worked with one client who had a particular need for this in testing a HUGE network of independently addressable embedded Linux devices, each one exposing a TCP/IP-level API. More on how to running unit tests as load tests here.

But on to my latest use of a unit test. Remember back in the day when we wrote libraries without unit test frameworks? What did we do? We wrote a little command line EXE to exercise the thing while we wrote it and never checked that in to SCC. It worked, mostly.

I often have the same need when writing Windows Forms applications. I want to spool up and play with a window without all of the overhead of the entire application. So, here’s my test.

   1: namespace ElegantCode.BeSure.Test.GivenTheConfirmationDialogIsDisplayed
   2: {
   3:     [TestClass]
   4:     public class WhenTheUserClicksNo
   5:     {
   6:         [TestMethod]
   7:         public void ThenTheDialogResultShouldBeNo()
   8:         {
   9:             ConfirmationForm confirmationDialog = new ConfirmationForm();
  10:             DialogResult result = confirmationDialog.ShowDialog();
  11:  
  12:             Assert.AreEqual(result, DialogResult.No);
  13:         }
  14:     }
  15: }

No, this is not a unit test. All this does for me is allow me to open the window in a run time environment, see it lay out on the screen, click around on it, etc.

If you notice the structure of the test naming, I am using a little BDD convention because I am wondering about the idea of building a manual regression suite this way. What if a tester sites down and runs through a manual test by launching the a unit test harness that drives the UI.

It’s an interesting idea, anyway.

Published by

David Starr

David Starr is Director of Technical Learning at GoDaddy. He is a professional software craftsman committed to improving agility, collaboration, and technical excellence in software development teams. He is the founder of Elegant Code Solutions, has served in numerous leadership contexts, and was as an early and consistent advocate for agile software development. He has successfully led product development initiatives and organizational transitions in numerous positions including Chief Software Craftsman at Scrum.org, Sr. Program Manager for Visual Studio and Team Foundation Server at Microsoft, Chief Software Architect, Director of Product Development, Pluralsight Author, independent consultant, and trainer. David’s professional focus is on all aspects of developing, delivering, and operating software systems. With specific attention on the end-to-end process, methods, and practices of high performing development teams, his skills transcend specific technology stacks, although he has has a specific skills focusing on the Microsoft stack. He speaks at various international conferences, is a frequent guest on various podcasts, author of articles throughout the technology industry, and the founder of Elegant Code Solutions. He is a 5 time Microsoft MVP in Visual Studio ALM.

3 thoughts on “Yet Another Use of a Unit Test Framework”

  1. Great post..thx for sharing your knowledge and especially thx for sharing the link to the post that explains — how to run
    unit tests as load tests… A situation that requires that emerged just recently and I was in great need to learn it ASAP..so again a BIG thx for that…

Comments are closed.