tdd

I'm testing a React/Reflux application using Jest. I have the following function in a store: onLoad: function() { console.log("ORIGINAL LOAD"); // http request here } I'm trying to mock it out so that it just does what it needs to do without doing the actual network stuff: beforeEach(function() { // mock out onLoad so instead of making API call the store gets test data PostStore.onLoad = jest.genMockFunction().mockImplementation(function () { var p1 = new Post( "54da7df5119025513400000a", // id "Test Post", // title "Kji6ftLjUqhElgnqOBqMUKxYONpU7nK/cu6jTA==\n", // owner anonId "Test Course 1",

I'm still learning the dark arts of TDD and recently I've been trying to learn how to do TDD in VB6 and what I basically narrow down the list to was the free simplyvbunit and the most costly vbunit3. My application is an richtext editor with plenty of 3rd party dll and I was scouring high and low in Google to find how to do unit test this exe file. So my question is how do you unit test an exe file? Especially in the context for VB6 and if you have any good example with vbunit3 or simplyvbunit, you're simply a lifesaver as I'm drowing in the material right now and I still can't write one unit

As far as I know typical workflow of TDD is based on black box testing. First we define interface then write one or set of test and then we implement code that pass all tests. So look at the example below: from abc import ABCMeta class InterfaceCalculator: __metaclass__ = ABCMeta @abstractmethod def calculate_mean(self): pass Exemplary test case from unittest import TestCase class TestInterfaceCalculator(TestCase): def test_should_correctly_calcluate_mean(self): X=[1,1] expected_mean = 1 calcluator =Calculator() self.assertAlmostEqual(calculator.calculate_mean(X), expected_mean) I skip

I am trying to test the logic from some existing classes. It is not possible to re-factor the classes at present as they are very complex and in production. What I want to do is create a mock object and test a method that internally calls another method that is very hard to mock. So I want to just set a behaviour for the secondary method call. But when I setup the behaviour for the method, the code of the method is invoked and fails. Am I missing something or is this just not possible to test without re-factoring the class? I have tried all the different mock types (Strick,Stub,Dynamic,Partial

I have not used Unit Testing so far, and I intend to adopt this procedure. I was impressed by TDD and certainly want to give it a try - I'm almost sure it's the way to go. Boost looks like a good choice, mainly because it's being maintained. With that said, how should I go about implementing a working and elegant file-structure and project-structure ? I am using VS 2005 in Win XP. I have been googling about this and was more confused than enlightened. Our Boost based Testing structure looks like this: ProjectRoot/ Library1/ lib1.vcproj lib1.cpp classX.cpp ... Library2/ lib2.vcproj lib2.cpp

It seems to me that most people write their tests against in-memory, in-process databases like SQLite when working with NHibernate. I have this up and running but my first test (that uses NHibernate) always takes between 3-4 seconds to execute. The next test runs much faster. I am using FluentNhibernate to do the mapping but get roughly the same timings with XML mapping files. For me the 3-4 second delay seriously disrupts my flow. What is the recomended way of working with TDD and NHibernate? Is it possible to mock ISession to unit test the actual queries or can this only be done with in