Many great responses to this are also on my question: “Beginning TDD – Challenges? Solutions? Recommendations?” May I also recommend taking a look at my blog post (which was partly inspired by my question), I have got some good feedback on that. Namely: I Don’t Know Where to Start? Start afresh. Only think about writing … Read more
Yes. This is a link to a study by Boby George and Laurie Williams at NCST and a another by Nagappan et al. I’m sure there are more. Dr. Williams publications on testing may provide a good starting point for finding them. [EDIT] The two papers above specifically reference TDD and show 15-35% increase in … Read more
I just want to point out that while most of the responders assumed these were unit tests, the question did not specify that they were. nUnit is a great tool that can be used for a variety of testing situations. I can see appropriate reasons for wanting to control test order. In those situations I … Read more
That’s not testing, that’s “looking manually at output” (known in the biz as LMAO). More formally it’s known as “looking manually for abnormal output” (LMFAO). (See note below) Any time you change code, you must run the app and LMFAO for all code affected by those changes. Even in small projects, this is problematic and … Read more
I understand BDD to be more about specification than testing. It is linked to Domain Driven Design (don’t you love these *DD acronyms?). It is linked with a certain way to write user stories, including high-level tests. An example by Tom ten Thij: Story: User logging in As a user I want to login with … Read more
Solved it with adding this to my .eslintrc: “import/no-extraneous-dependencies”: [“error”, {“devDependencies”: true}] [no-extraneous-dependencies] Add exceptions? #422 Based on this user’s reply: you could set the option devDependencies: true in an .eslintrc in your test folder: rules: import/no-extraneous-dependencies: [error, { devDependencies: true }] Then you’ll get reports of any packages referenced that are not included dependencies … Read more
Martin Fowler wrote an excellent article on this subject. From that article: Meszaros uses the term Test Double as the generic term for any kind of pretend object used in place of a real object for testing purposes. The name comes from the notion of a Stunt Double in movies. (One of his aims was … Read more
There is actually a shunit2, an xUnit based unit test framework for Bourne based shell scripts. I haven’t used it myself, but it might be worth checking out. Similar questions have been asked before: Unit Testing for Shell Scripts Test Anything Protocol in Shell Scripts
I’ve introduced unit tests to code bases that did not have it previously. The last big project I was involved with where I did this the product was already in production with zero unit tests when I arrived to the team. When I left – 2 years later – we had 4500+ or so tests … Read more
You can use fixture_file_upload method to test file uploading: Put your test file in “{Rails.root}/spec/fixtures/files” directory before :each do @file = fixture_file_upload(‘files/test_lic.xml’, ‘text/xml’) end it “can upload a license” do post :uploadLicense, :upload => @file response.should be_success end In case you were expecting the file in the form of params[‘upload’][‘datafile’] it “can upload a license” … Read more