tdd

I have one test that needs to work more then 1 minute (VS2008, MSTest, tests are launched from the VisualStudio): const int TestTimeout = 1; [TestMethod] [Timeout(10*60*1000)] // 10 minutes public void Login_ExpirationFail_Test() { IAuthenticationParameters parameters = new AuthenticationParameters(...); LdapAuthentication auth1 = new LdapAuthentication(); IAuthenticationLoginResult res = auth1.Login(parameters); Assert.IsNotNull(res); Assert.IsFalse(string.IsNullOrEmpty(res.SessionId)); const int AdditionalMilisecodns = 400; System.Threading.Thread.Sleep((TestTimeout * 1000 +

I'm working in a project that uses the new ASP.NET WebAPI. My current task is to accept an uploaded file. So far, I have used TDD to drive out the WebAPI code, but I've hit a wall with uploading. I'm currently following the advice found at http://www.asp.net/web-api/overview/working-with-http/sending-html-form-data,-part-2 , but there seems to be no way at all to drive this out of a unit test. In order to get at the file and form data, I have to use MultipartFormDataStreamProvider , which is impossible to mock and/or override. Short of forsaking my TDD approach, what can I do? Here's the code

I try to use TDD as much as I can. When I do, I stowe all comunication with the outside away in wrapper classes. A few minutes ago, I made a wrapper for the static class Directory , so I can test my other code without talking to the actual file system. But what about unit testing the wrapper itself? Since I use TDD, it nags me that I haven't written tests for it. On the other hand, It is a wrapper and nothing else, so do I really need to? I tend to do the same and not worry about unit testing wrapper classes, as long as I've satisfied myself that they contain the bare minimum amount of code.

I have started following TDD in my project. But ever since I started it after reading some articles, I am bit confused since the development has slowed down. Whenever I refactor my code, I need to change the existing test cases I have written before because they will start failing. Following is the example: public class SalaryManager { public string CalculateSalaryAndSendMessage(int daysWorked, int monthlySalary) { int salary = 0, tempSalary = 0; if (daysWorked < 15) { tempSalary = (monthlySalary / 30) * daysWorked; salary = tempSalary - 0.1 * tempSalary; } else { tempSalary = (monthlySalary /

I am frequently running into issues in capybara with request tests failing because capybara is not waiting for ajax events to complete before moving on. Google seems to indicate I should be using :resynchronize option for my tests to fix this. But it is not working. To prove this is an issue, failing tests can be fixed by putting a sleep statement after the ajax call. This seems hacky any bad practice as the appropriote delay will vary depending on the speed of the machine running the tests. And picking a suitably large value will seriously slow down running a test suite with lots of ajax

I'm trying to test user model, for which I've devise authentication. The problem I'm facing is, 1. Having 'password'/'password_confirmation' fields in fixtures is giving me invalid column 'password'/'password_confirmation' error. If I remove these columns from fixture and add in user_test.rb require 'test_helper' class UserTest < ActiveSupport::TestCase def setup @user = User.new(name: "example user", email: "example@example.com", password: "Test123", work_number: '1234567890', cell_number: '1234567890') end test "should be valid" do assert @user.valid? end test "name should be present" do