If you want to mock a module that declare one or more services I have used this code: beforeEach(function(){ module(‘moduleToMock’); module(function ($provide) { $provide.value(‘yourService’, serviceMock); }); }); This is useful if the service you want to mock is also a service that you want to unit test (in another jasmine describe). The solution proposed by … Read more
You can run all the tests in a class, by passing the -Dtest=<class> flag to Maven: mvn clean test -Dtest=xxxxTest Since Surefire 2.8, you can also run an individual test, say a method testA within your unit tests, using the same flag: mvn clean test -Dtest=xxxxTest#testA More examples for running multiple tests, by name pattern … Read more
The correct way for Angular (ver. 2+): it(‘retrieves all the cars’, waitForAsync(inject([CarService], (carService) => { carService.getCars().subscribe(result => expect(result.length).toBeGreaterThan(0)); })); Async Observables vs Sync Observables It is important to understand that Observables can be either synchronous or asynchronous. In your specific example the Observable is asynchronous (it wraps an http call). Therefore you have to use … Read more
The best way, I have found, is to incrementally add the unit tests, not to just jump in and say we will now unit test the application. So, if you are going to touch the code, for bug fixes or refactoring, then first write the unit tests. For bugs unit tests will help prove where … Read more
This is not the most common thing to do, but still common enough to have its own name. This technique is called Guard Assertion. You can find a detailed description of it on page 490 in the excellent book xUnit Test Patterns by Gerard Meszaros (highly recommended). Normally, I don’t use this pattern myself, since … Read more
Your question was about how the MS Fakes framework is different from NMock and it appears the other answers have resolved some of that, but here is some more information regarding how they are the same and how they are different. NMock is also similar to RhinoMocks and Moq, so I’m grouping them in with … Read more
The simplest way to do this is to just use the useValue attribute and provide an Observable of the value you want to mock. RxJS < 6 import { Observable } from ‘rxjs/Observable’; import ‘rxjs/add/observable/of’; … { provide: ActivatedRoute, useValue: { params: Observable.of({id: 123}) } } RxJS >= 6 import { of } from ‘rxjs’; … Read more
Your test could be: it(‘should emit on click’, () => { const fixture = TestBed.createComponent(MyComponent); // spy on event emitter const component = fixture.componentInstance; spyOn(component.myEventEmitter, ’emit’); // trigger the click const nativeElement = fixture.nativeElement; const button = nativeElement.querySelector(‘button’); button.dispatchEvent(new Event(‘click’)); fixture.detectChanges(); expect(component.myEventEmitter.emit).toHaveBeenCalledWith(‘hello’); }); when your component is: @Component({ … }) class MyComponent { @Output myEventEmitter … Read more
Take a look at Markus Kuhn’s UTF-8 decoder capability and stress test file You’ll find examples of many UTF-8 irregularities, including lonely start bytes, continuation bytes missing, overlong sequences, etc.
Designs like MVP and MVC typically try to abstract as much logic out of the actual GUI as possible. One very popular article about this is “The Humble Dialog Box” by Michael Feathers. Personally I’ve had mixed experiences with trying to move logic out of the UI – sometimes it’s worked very well, and at … Read more