You might be able to do what you need with net.Pipe which basically gives you both ends of a connection (think, after .Accept()) server, client := net.Pipe() go func() { // Do some stuff server.Close() }() // Do some stuff client.Close()
Many of the other answers hint at it, but I’m going to more explicitly say that yes, naive implementations of dependency injection can break encapsulation. The key to avoiding this is that calling code should not directly instantiate the dependencies (if it doesn’t care about them). This can be done in a number of ways. … Read more
You might be testing the wrong thing – you should not have different tests for every method in your code. You might have too many tests because you test implementation and not functionality – try testing how things are done test what is done. For example if you have a customer that is entitled to … Read more
No. At the moment, you have to check the difference by yourself or use the float-cmp crate. Also check out the f32 constants.
It may seem trivial to quote Wikipedia, but I think it’s very succinct and accurate in this case: A unit is the smallest testable part of an application. This seems to agree with the comment in your question that a unit is “the smallest piece of the code that can be usefully tested”. In other … Read more
I’ve looked at one such project where the number of unit tests made the system take too long to test everything. “Too long” meaning that you basically didn’t do that as part of your normal development routine. However, what they had done was to categorize the unit tests into two parts. Critical tests, and “everything … Read more
mockFn.mockRestore only works for a mock function created with jest.spyOn: const obj = { func: () => ‘original’ } test(‘func’, () => { const mock = jest.spyOn(obj, ‘func’); mock.mockReturnValue(‘mocked’); expect(obj.func()).toBe(‘mocked’); // Success! mock.mockRestore(); expect(obj.func()).toBe(‘original’); // Success! }) jest.spyOn wraps the original function and provides mockRestore as a way to restore the original function. jest.mock calls … Read more
I’m a huge fan of Selenium. Saying ‘unit-testing your web ui’ isn’t exactly accurate as some of the comments have mentioned. However, I do find Selenium to be incredibly useful for performing those sort of acceptance and sanity tests on the UI. A good way to get started is using Selenium IDE as part of … Read more
A summary from the answers by jdehaan and Eric Brown, as well as this question (see also this question): N.B. These solutions may affect other error reporting as well, e.g. failure to load a DLL or open a file. Option 1: Disable globally Works globally on the entire user account or machine, which can be … Read more
You should use Moq to create your Mock object and set CallBase property to true to use the object behavior. From the Moq documentation: CallBase is defined as “Invoke base class implementation if no expectation overrides the member. This is called “Partial Mock”. It allows to mock certain part of a class without having to … Read more