We should get “Program” class from the main project but it automatically references Microsoft.AspNetCore.Mvc.Testing.Program class public class VersioningTests : IClassFixture<WebApplicationFactory<Program>> this code must reference our main Program code. So we must put a reference to the Program class on the last line in Program.cs file: public partial class Program { }
Note that if you are trying to use xUnit and its IClassFixture<T> pattern, you will run into problems if you just use the InternalsVisibleTo approach. Specifically, you’ll get something like this: “Inconsistent accessibility: base class WebApplicationFactory<Program> is less accessible than class CustomWebApplicationFactory.” Of course you can solve this by making CustomWebApplicationFactory internal but it only …
Golden rule of TDD says: Never write new functionality without failing test. If you are not following this rule, then you are doing TDD partially (like writing unit tests only for several classes in your application). That’s better than nothing (at least you know these classes do what required, but you cannot be sure that …
I can’t speak to being a best practice, but here’s what I’ve done in the past. Unit tests: Create unit tests for non-trivial beans (ie, most of your Spring related beans) Use Mocks for injected services where practical (ie, most if not all the time). Use a standard naming convention for these tests in the …
There’s a semi decent implementation at node-mocks-http Require it: var mocks = require(‘node-mocks-http’); you can then compose req and response objects: req = mocks.createRequest(); res = mocks.createResponse(); You can then test your controller directly: var demoController = require(‘demoController’); demoController.login(req, res); assert.equal(res.json, {}) caveat There is at time of writing an issue in this implementation to …
You can’t login user from selenium driver. It’s just impossible without some hacks. But you can login once per TestCase by moving it to setUp method. You can also avoid copy-pasting by creating your class inherit from LiveServerTestCase. UPDATE This code worked for me: self.client.login(username=superuser.username, password=’superpassword’) #Native django test client cookie = self.client.cookies[‘sessionid’] self.browser.get(self.live_server_url + …
I’ve used JUnit for doing a lot of integration testing. Integration testing can, of course, mean many different things. For more system level integration tests, I prefer to let scripts drive my testing process from outside. Here’s an approach that works well for me for applications that use http and databases and I want to …
The solution is this: <build> <pluginManagement> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-surefire-plugin</artifactId> <version>2.19.1</version> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-failsafe-plugin</artifactId> <version>2.19.1</version> </plugin> </plugins> </pluginManagement> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-compiler-plugin</artifactId> <version>3.6.1</version> <configuration> <source>1.7</source> <target>1.7</target> </configuration> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-failsafe-plugin</artifactId> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-surefire-plugin</artifactId> <configuration> <skip>${surefire.skip}</skip> </configuration> <executions> <execution> <goals> <goal>integration-test</goal> <goal>verify</goal> </goals> </execution> </executions> </plugin> </plugins> </build> <dependencies> <dependency> <groupId>junit</groupId> <artifactId>junit</artifactId> <version>4.12</version> …
Great question. It seems like you hit the limits of Mockito. Mockito is great if what you want to inspect object interactions. What you want, though, seems to be observability (and controllability) at a higher level of abstraction. I’m afraid that the mocks or stubs you need for that should be carefully designed and hand-crafted. …