I think all 3 presented options are bad if your intent is to run a proper unit test. A unit test must be blazing fast, you should be able to run hundreds of those in a second or so (depending on the hardware of course, but you get the idea). So once you say “I … Read more
Let us use the same sample code as in my answer to the related AspectJ unit testing question: Java class to be targeted by aspect: package de.scrum_master.app; public class Application { public void doSomething(int number) { System.out.println(“Doing something with number ” + number); } } Aspect under test: package de.scrum_master.aspect; import org.aspectj.lang.ProceedingJoinPoint; import org.aspectj.lang.annotation.Around; import … Read more
Thanks so much to @Justin and @Petro for your answers, which have helped me immensely. The solution I have come up with is a combination of the techniques you suggested. The solution described below provides a new database for each run of the tests, and a separate transaction for each test. I added a connection … Read more
A SQLite memory database only exists as long as the connection to it remains open. To use it in unit tests with NHibernate: 1. Open an ISession at the beginning of your test (maybe in a [SetUp] method). 2. Use the connection from that session in your SchemaExport call. 3. Use that same session in … Read more
It seems to me that instrumentation testing is integration testing with the ability to control the life cycle and the events (onStart, onCreate etc) of the app. Unit testing, as i understand it, is testing a Unit (eg Class) for its data and behavior. For example, say you have a game: this game runs on … Read more
Where I work we use RedGate Data Generator to generate test data. Since we work in the banking domain. When we have to work with nominative data (Credit card numbers, personnal ID, phone numbers) we developed an application that can mask these database fields so we can work with them as real data. I can … Read more
I don’t recommend nesting unless absolutely necessary. You may be able to “flatten” your permutations into a single table, something like this: https://github.com/intuit/karate/issues/661#issue-402624580 That said, look out for the alternate option to Examples: which just might work for your case: https://github.com/intuit/karate#data-driven-features EDIT: In version 1.3.0, a new @setup life cycle was introduced that changes the … Read more
To test operations that involve the HTTP request, you have to actually initialize an *http.Request and set it to the Gin context. To specifically test c.BindQuery it’s enough to properly initialize the request’s URL and URL.RawQuery: func mockGin() (*gin.Context, *httptest.ResponseRecorder) { w := httptest.NewRecorder() c, _ := gin.CreateTestContext(w) // test request, must instantiate a request … Read more
If you haven’t already, you might want to check out Dan North’s excellent article, What’s in a Story? as a starting point. We have two main uses for Cucumber stories. First, because the story form is very specific it helps focus the product owner’s articulation of the features he wants built. This is the “token … Read more
If you think about the responsibility of the AccessDenied component, it isn’t really to send the user home. That’s the overall behaviour you want, but the component’s role in that is simply to send the user to “/”. At the component unit level, therefore, the test could look something like this: import React, { FC … Read more