Have a look at the Google Testing blog: Using dependency injection to avoid singletons Singletons are Pathological Liars Root Cause of Singletons Where have all the Singletons Gone? Clean Code Talks – Global State and Singletons Dependency Injection. And also: Once Is Not Enough Performant Singletons Finally, Misko Hevery wrote a guide on his blog: … Read more
The other answer’s tests should be written as: describe(‘directives’, function() { var $scope, form; beforeEach(module(‘exampleDirective’)); beforeEach(inject(function($compile, $rootScope) { $scope = $rootScope; var element = angular.element( ‘<form name=”form”>’ + ‘<input ng-model=”model.somenum” name=”somenum” integer />’ + ‘</form>’ ); $scope.model = { somenum: null } $compile(element)($scope); form = $scope.form; })); describe(‘integer’, function() { it(‘should pass with integer’, function() … Read more
Finally, I’ve discovered, that I have to add the following settings to the subproject: lazy val webapp = project settings( Seq( projectDependencies ++= Seq( …. “org.scalatest” %% “scalatest” % “2.2.2” % Test, “junit” % “junit” % “4.11” % Test, crossPaths := false, “com.novocode” % “junit-interface” % “0.11” % Test ) ): _* ) It is … Read more
My own unit testing library, Unquote, takes advantage of F# quotations to allow you to write test assertions as plain, statically checked F# boolean expressions and automatically produces nice step-by-step test failure messages. For example, the following failing xUnit test [<Fact>] let “demo Unquote xUnit support“ () = test <@ ([3; 2; 1; 0] |> … Read more
With a slight refactoring, you may easily achieve 100% coverage. foo/bar.go: package foo import ( “fmt” “os” ) var osExit = os.Exit func Crasher() { fmt.Println(“Going down in flames!”) osExit(1) } And the testing code: foo/bar_test.go: package foo import “testing” func TestCrasher(t *testing.T) { // Save current function and restore at the end: oldOsExit := … Read more
Yes, with a simple refactoring. Create a zSomeFunc variable of function type, initialized with z.SomeFunc, and have your package call that instead of z.SomeFunc(): var zSomeFunc = z.SomeFunc func abc() { // … v := zSomeFunc() // … } In tests you may assign another function to zSomeFunc, one that is defined in tests, and … Read more
tl;dr To make it short – there’s no way to unit test Spring Data JPA repositories reasonably for a simple reason: it’s way to cumbersome to mock all the parts of the JPA API we invoke to bootstrap the repositories. Unit tests don’t make too much sense here anyway, as you’re usually not writing any … Read more
Keep them separate. A unit test is supposed to tell you which unit failed. Keeping them separate also allows you to isolate the problem quickly w/o requiring you to go through a lengthy debug cycle.
From Mockito 3.4.0 (2020-07-10), it is possible to mock static methods out of the box even in JUnit 5, without any extension. In the documentation, you can find an example: 48. Mocking static methods (since 3.4.0) Important note: You need to use inline mock maker. So the dependency to use is not the core one: <dependency> … Read more
You’re right that you can’t just set the input, you also need to dispatch the ‘input’ event. Here is a function I wrote earlier this evening to input text: function sendInput(text: string) { inputElement.value = text; inputElement.dispatchEvent(new Event(‘input’)); fixture.detectChanges(); return fixture.whenStable(); } Here fixture is the ComponentFixture and inputElement is the relevant HTTPInputElement from the … Read more