Home/ Questions/Q 9280467
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-18T17:52:41+00:00

I have read/watched so much about TDD & BDD recently that I really want

  • 0

I have read/watched so much about TDD & BDD recently that I really want to master it. I have been a developer that only writes code and then tests it from outside (like we always started). The problem seems to be in getting up and running with TDD. I want to just create a simple Winform app in which I want to show a list of something lets say products. I just don’t know where to get started, should I write a test for controller first? the controller needs reference to view and service and so on so forth. ASP.Net MVC is built for testing therefore it is a bit easy to get started but Winforms are a real pain. Kindly give me some Videos (Most preffered) that show TDD in Winforms.

I have watched tons of videos that show you testing a class or feature but how do you test UI that does not support testing?

In short I want to know if anyone has been doing TDD for a while, how
does he/she do it in Winforms?

I have written loads of code that I just delete because I get stuck, Please help!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Here’s how I do it for any kind of UI, be it Web or Winforms or WPF or Swing in Java or even a web service interface that’s going to be used by another system.

    • Write the UI, and hard-code any data behind it.
    • Write a controller, and move the hard-coded data to the controller. The controller should just be presenting the data in a form that the UI can understand.

    Your controller now has no behavior; just static data – but it’s got the right API for the UI, and now you know how the UI wants to use it.

    • Write an example that shows how the UI will use the controller in the most basic form.
    • Make the example work.
    • Write another example that shows how the controller behaves differently in a different context.
    • Make the example work.

    Those are your unit tests! If you know that your controller is going to need some other classes to collaborate with, you can mock those out too.

    Once your collaborators are mocked out, you already know how the controller wants to use them. Again, you have the API for those collaborators already, because the controller is using them.

    This is what we’re doing when we talk about “outside-in” in BDD.

    • 0