Using the Unit Test tool to testdriven.net the debugger

Introduction

In the actual project, we will encounter the following problems:

1. When writing some programs that are not very good to debug, such as WebService and some background running programs, how to debug?

2. Some of the underlying frameworks exist in some architectures, how are these frameworks debugged?

3. When we write a method or some methods that exist to refer to each other, how do we debug from top to bottom?

4. When writing out a method, are you still using the following steps to debug? Compile, F9 breakpoints, run, debug? Don't you think it's a good time ...? Or do you think it's worth it for a method to debug/test a bunch of methods so that you don't miss out on some of the bugs?

5. If we want to use the Unit Test tool to test some of the underlying things, the normal process is to write a unit test module [test] and then use the Unit Test tool to perform the test. But this is one of the drawbacks of unit testing, too time-consuming ...

。。。。。。

Basis

First: Since we use the Unit test tool is testdriven.net, then the total first download a installation, download the address: http://www.testdriven.net/download.aspx.

Second: I'm not going to tell you about unit test theory, or how to use Unit Test tool testdriven.net for unit testing.

The core of this article is debugging, OK, nonsense don't say much, start.

After installing TestDriven.NET, in NET project, the code. cs file pops up in the right button menu, there will be three more options, such as the following figure: