tdd

I've got a class that has a private member that has for type System.Windows.Forms.Timer . There's also a private method that is being called every time my timer ticks. Is it worth testing the method? (since it's private) How can I test it? (I know I can have my test class inheriting the class I want to test...) Should I be mocking my timer? Because if I have to test a class that uses an internal timer, my tests may take a lot of time to complete, right? edit: Actually, the method has a dependency on timing, here's the code: private void alertTick(object sender, EventArgs e) { if

Consider this class: public class Content { public virtual bool IsCheckedOut {get; private set;} public virtual void CheckOut() { IsCheckedOut = true; } public virtual void CheckIn() { //Do Nothing for now as demonstrating false positive test. } } The Checkin method is intentionally empty. Now i have a few test methods to verify the status of calling each method. [TestMethod] public void CheckOutSetsCheckedOutStatusToTrue() { Content c = new Content(); c.CheckOut(); Assert.AreEqual(true, c.IsCheckedOut); //Test works as expected } [TestMethod] public void CheckInSetsCheckedOutStatusToFalse() {

使用unitils的dbunit模块进行测试。 真正的去访问数据库，每次测试之前打开一个事务，插入测试数据，业务操作，断言测试数据，回滚。 其中unitils+dbunit实现了除业务操作之外的所有步骤。 dbunit提供了将xml直接转换为数据库数据的功能。 unitils则进一步封装，提供了@DataSet，@ExpectDataset以及事务管理等功能，可以通过annotation的方式将数据文件导入数据库，也可以通过xml去断言数据，并且支持自动回滚，超级方便。 这里在使用 unitils整合dbunit的时候碰到了两个问题，记录一下。 关于问题，请分别查看下面两篇文章： unitils使用@DataSet插入测试数据，测试结束后不能回滚 mysql+unitils用@DataSet，抛NoSuchColumnException 最后，贴上一段标准DAO测试的代码： @DataSet public final class RoleDaoTest extends IntegrateBaseTest { @SpringBeanByType private RoleDao roleDao; @Test @ExpectedDataSet public void save() { Role role = new Role(); role.setName("Test Role");

So I'm creating a custom ActionFilter that's based mostly on this project http://www.codeproject.com/KB/aspnet/aspnet_mvc_restapi.aspx . I want a custom action filter that uses the http accept headers to return either JSON or Xml. A typical controller action will look like this: [AcceptVerbs(HttpVerbs.Get)] [AcceptTypesAttribute(HttpContentTypes.Json, HttpContentTypes.Xml)] public ActionResult Index() { var articles = Service.GetRecentArticles(); return View(articles); } The custom filter overrides the OnActionExecuted and will serialize the object (in this example articles) as either JSON or

I have an example class public class MyClass{ ActionResult Method1(){ .... } [Authorize] ActionResult Method2(){ .... } [Authorize] ActionResult Method3(int value){ .... } } Now what I want is to write a function returning true/false that can be executed like this var controller = new MyClass(); Assert.IsFalse(MethodHasAuthorizeAttribute(controller.Method1)); Assert.IsTrue(MethodHasAuthorizeAttribute(controller.Method2)); Assert.IsTrue(MethodHasAuthorizeAttribute(controller.Method3)); I got to the point where public bool MethodHasAuthorizeAttribute(Func<int, ActionResult> function) { return

I'm about to start out my first TDD (test-driven development) program, and I (naturally) have a TDD mental block..so I was wondering if someone could help guide me on where I should start a bit. I'm creating a function that will read binary data from socket and parses its data into a class object. As far as I see, there are 3 parts: 1) Logic to parse data 2) socket class 3) class object What are the steps that I should take so that I could incrementally TDD? I definitely plan to first write the test before even implementing the function. The issue in TDD is "design for testability" First, you

I'm not brand new to the concept of unit testing but at the same time I've not yet mastered them either. The one question that has been going through my head recently as I've been writing unit tests while writing my code using the TDD methodology is: to what level should I be testing? Sometimes I wonder if I'm being excessive in the use of unit testing. At what point should a developer stop writing unit tests and get actual work done? I might need to clarify that question before people assume I'm against using TDD... What I'm struggling with is the granularity of my test.... When my app has a