To answer your last question, the recommended approach is to use <MemoryRouter>< *your component here* ></MemoryRouter> in your tests. Typescript does not pick up that this component will pass the required props to your component, as such I assume it not to be a type safe approach. This is for React Router v4 and doesn’t … Read more
Use dependency injection. Coupling it with generics and monomorphism, you don’t lose any performance: use std::io::{self, BufRead, Write}; fn prompt<R, W>(mut reader: R, mut writer: W, question: &str) -> String where R: BufRead, W: Write, { write!(&mut writer, “{}”, question).expect(“Unable to write”); let mut s = String::new(); reader.read_line(&mut s).expect(“Unable to read”); s } #[test] fn … Read more
You have to specify the callback done as the argument to the function which is provided to mocha – in this case the it() function. Like so: describe(‘api’, function() { it(‘should load a user’, function(done) { // added “done” as parameter assert.doesNotThrow(function() { doRequest(options, function(res) { assert.equal(res, ‘{Object … }’); // will not fail assert.doesNotThrow … Read more
From my experience, 25% effort is spent on Analysis; 50% for Design, Development and Unit Test; remaining 25% for testing. Most projects will fit within a +/-10% variance of this rule of thumb depending on the nature of the project, knowledge of resources, quality of inputs & outputs, etc. One can add a project management … Read more
As it happens, Mocha 0.10.0 allows unstubbing on any_instance(). str = “Not Stubbed!” String.any_instance.stubs(:to_s).returns(“Stubbed!”) puts str.to_s # “Stubbed!” String.any_instance.unstub(:to_s) puts str.to_s # “Not Stubbed!”
Here is the solution only use jestjs and typescript, nothing more. index.ts: export function getUserInfo() { const userInfo = window.sessionStorage.getItem(‘userInfo’); if (userInfo) { return JSON.parse(userInfo); } return {}; } index.spec.ts: import { getUserInfo } from ‘./’; const localStorageMock = (() => { let store = {}; return { getItem(key) { return store[key] || null; }, … Read more
I personally prefer Shoulda to RSpec. I find that Shoulda has less magic syntax than RSpec. My problem with RSpec is that yeah it’s very readable when I read it aloud, but when I get to writing it, hmmmm, I’m never sure how a given assertion should be written. Prag Dave explains the problem better … Read more
You’re close. You just need to call the method on your mock before calling expectLastCall() So you expectation would look like this: userService.addUser(newUser1); EasyMock.expectLastCall(); EasyMock.replay(dbMapper); userService.addUser(newUser1); This works because the mock object is in Record mode before the call to replay(), so any calls to it will perform default behaviour (return null/do nothing) and will … Read more
Keeping testers busy tends to get easier as a project matures (there is more to test!), but the following points apply in the early stages too: Testers can prepare their test plans, test cases, and automated tests for the user stories before (or while) they are implemented. This helps the team discover any inconsistency or … Read more