TestFixTure Test TestDriven test driver
2-19-2005-23: 02 SAT [DEV development]
Test driver, when I heard it, it is exactly how long I have just started to enter the current company. At that time, it was just responsible for the Windows series driver of the entire product. So I didn't think about it, it seems that this is what I do every day. The driver test has begun to make a software, and it has begun to understand the test driver, which is to test the code unit. It is also not to use it, because my program is a Windows GUI program, it will run, debug it after writing. Even single step, so it doesn't matter. Later, Java / .NET, etc., Yippeesoft happy software slowly understood this significance, but there is no way to use. Because the task of work is not bad. This year begins .Net, naturally put NUNIT, a long-term Yippeesoft Happy Software name, trial for a day or two, and found that it is too much trouble. My machine is originally running. Net has already been quickly opened, and then a NUNIT feels uncomfortable. And the reason why the unit test tool is really because of running, single-step debugging is too slow, but also changed the code immediately as before the previous VB VC, but also to interrupt debugging, and run again. Finally found TestDriveN.Net this YippeSoft fun software tool, as a plug-in addIN in .NET IDE, you don't have to run separately, as long as the right mouse button, a test can be completed. It is really comfortable. However, it is actually running a TCP listening process alone, but it is not quiet, and it is better to use this in front of my debug O / R MAP. It feels comfortable. Cited increased TestDriven.NET 1.0 / TestDriven.Framework.dll TestDriven.NET 1.0 / TestDriven.NET.dll TestDriven.NET 1.0 / NUnit / nunit.framework.dll using System; using NUnit.Framework; YippeeSoft fun software using TestDriven; using System . DiAgnostics; Namespace Sksync & Leftsign; ///
