tdd

how to write unit tests to internal classes ??? You write tests which specify the behaviour of the top-level class' external interface. Whether that class uses internal classes to implement that behaviour or not, is an implementation detail of the class, and the tests don't need to know anything about it. If the internal class cannot be adequately tested through the top-level class' interface, then it's usually best to move the internal class out and test it directly as a new top-level class. Wanting to test internal classes is a code smell that the internal class might be significant enough

I know what the advantages are and I use fake data when I am working with more complex systems. What if I am developing something simple and I can easily set up my environment in a real database and the data being accessed is so small that the access time is not a factor, and I am only running a few tests. Is it still important to create fake data or can I forget the extra coding and skip right to the real thing? When I said real database I do not mean a production database, I mean a test database, but using a real live DBMS and the same schema as the real database. Uncle Bob The reasons to

There are a lot of testing methods out there i.e. blackbox , graybox , unit , functional , regression etc. Obviously, a project cannot take on all testing methods. So I asked this question to gain an idea of what test methods to use and why should I use them. You can answer in the following format: Test Method - what you use it on e.g. Unit Testing - I use it for ...(blah, blah) Regression Testing - I use it for ...(blah, blah) I was asked to engage into TDD and of course I had to research testing methods. But there is a whole plethora of them and I don't know what to use (because they all

My basic logic is to have an infinite loop running somewhere and test it as best as possible. The reason for having an infinite loop is not important (main loop for games, daemon-like logic...) and I'm more asking about best practices regarding a situation like that. Let's take this code for example: module Blah extend self def run some_initializer_method loop do some_other_method yet_another_method end end end I want to test the method Blah.run using Rspec (also I use RR , but plain rspec would be an acceptable answer). I figure the best way to do it would be to decompose a bit more, like

I have attributes on certain tests that I ideally don't want to run on every build. Most of my tests are normal unit tests and I do want them to run on every build. So: how can I exclude a test by category or project type? For example, I'd like to exclude CodedUItests : [CodedUITest] public class SearchViewTests ...or exclude tests in a given TestCategory : [TestMethod] [TestCategory("Database Integration")] public void ContactRepositoryGetByIdWithIdExpectCorrectContact() I particularly want to exclude the coded UI tests as they disrupt my ability to continue working, whereas all the other

I am trying to mock console.warn/error but i can't. I use a third-party-library which calls console.warn inside it. I need to test was it called or wasn't. In my test case i was trying to stub console.warn but it didn't help. After that i was trying to mock console manually it didn't work out either. console.warn = jest.fn(); testSchema('/app/components/Users/UserItem/UserItemContainer.js'); expect(console.warn).toBeCalled(); didn't work console.warn = jest.fn(); testSchema('/app/components/Users/UserItem/UserItemContainer.js'); console.warn('error'); expect(console.warn).toBeCalled(); did

I'm looking for research papers or studies made on Unit Testing and TDD effectiveness. Points of interest: Does TDD reduce Development time? Does overall development cost reduced as well? Is the result product more stable? Microsoft Research: Realizing quality improvement through test driven development: results and experiences of four industrial teams StudiesOfTestDrivenDevelopment has a summary and more links. An article on infoQ: Empirical Studies Show Test Driven Development Improves Quality . And a link to the Realizing quality improvement through TDD study . "TDD seems to be applicable

I have a lot of unit tests that pretty much tests the same behavior. However, data type changes. I am trying to create a generic method that can take any data type. I tried making my input parameter var but that's not allowed. Also, looked into c# generics but that usually deals with a list. You could make the parameter an object : public void DoSomething(object arg) { //... Or you could do what I prefer and make a generic method: public void DoSomething<T>(T arg) { //... The generic approach has two major advantages, and I'll give examples of why they're useful: Even though you don't