tdd

When doing TDD , how to tell "that's enough tests for this class / feature"? I.e. when could you tell that you completed testing all edge cases? With Test Driven Development, you’ll write a test before you write the code it tests. Once you’re written the code and the test passes, then it’s time to write another test. If you follow TDD correctly, you’ve written enough tests once you’re code does all that is required. As for edge cases, let's take an example such as validating a parameter in a method. Before you add the parameter to you code, you create tests which verify the code will handle

Which way is proper for mocking and testing code that iters object returned by open() , using mock library? whitelist_data.py : WHITELIST_FILE = "testdata.txt" format_str = lambda s: s.rstrip().lstrip('www.') whitelist = None with open(WHITELIST_FILE) as whitelist_data: whitelist = set(format_str(line) for line in whitelist_data) if not whitelist: raise RuntimeError("Can't read data from %s file" % WHITELIST_FILE) def is_whitelisted(substr): return 1 if format_str(substr) in whitelist else 0 Here's how I try to test it. import unittest import mock TEST_DATA = """ domain1.com domain2.com

I am writing a test using GoogleTest for the following class and I am getting the above error. class Base { // Other Functions; CSig objSig[50]; } The Class CSig is as follows: class CSig { //... constructor, destructor(empty) and some functions CMod *objMod; CDemod *objDemod; } CSig :: CSig { bIsInitialised = false; for (int i=0; i<MAX_NUM; i++) { PStrokePrev[i] = 0.0; } } However, when I discard CSig objSig[50] , the tests run fine. What can I do to solve this issue? Also, I need to have CSig objSig[50] in the Base class. A SEH (Structured Exception Handling) exception is not a C++-exception

When using Mockito 1.9.x I have been using Whitebox to set values of fields to "inject" mocks. Se example below: @Before public void setUp() { eventHandler = new ProcessEventHandler(); securityService = new SecurityServiceMock(); registrationService = mock(RegistrationService.class); Whitebox.setInternalState(eventHandler, "registrationService", registrationService); Whitebox.setInternalState(eventHandler, "securityService", securityService); } I really like this approach, but now that I tried to upgrade to Mockito 2.2.7 I noticed (or rather, my IDE noticed and told me quite a few times) that

I'm attempting to test a React component with Jest/Enzyme while using Webpack. I have a very simple test @ import React from 'react'; import { shallow } from 'enzyme'; import App from './App'; it('App', () => { const app = shallow(<App />); expect(1).toEqual(1); }); The relative component it's picking up is : import React, { Component } from 'react'; import { render } from 'react-dom'; // import './styles/normalize.css'; class App extends Component { render() { return ( <div>app</div> ); } } render(<App />, document.getElementById('app')); However, running jest causes a failure: Invariant