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
You can split them very easily using JUnit categories and Maven. This is shown very, very briefly below by splitting unit and integration tests. Define A Marker Interface The first step in grouping a test using categories is to create a marker interface. This interface will be used to mark all of the tests that … Read more
You can try to change your default processor architecture in your Test Setting from X86 to X64. In my case this was the problem. This happens if the platform target of your project under test is set to x64.
Readability is more important for tests. If a test fails, you want the problem to be obvious. The developer shouldn’t have to wade through a lot of heavily factored test code to determine exactly what failed. You don’t want your test code to become so complex that you need to write unit-test-tests. However, eliminating duplication … Read more
@Ainar-G suggests several great patterns to separate tests. This set of Go practices from SoundCloud recommends using build tags (described in the “Build Constraints” section of the build package) to select which tests to run: Write an integration_test.go, and give it a build tag of integration. Define (global) flags for things like service addresses and … Read more
Martin Fowler wrote an excellent article on this subject. From that article: Meszaros uses the term Test Double as the generic term for any kind of pretend object used in place of a real object for testing purposes. The name comes from the notion of a Stunt Double in movies. (One of his aims was … Read more
2019 edition: In Async Code await Future.delayed(Duration(seconds: 1)); In Sync Code import ‘dart:io’; sleep(Duration(seconds:1)); Note: This blocks the entire process (isolate), so other async functions will not be processed. It’s also not available on the web because Javascript is really async-only.
What is unit testing? Unit testing simply verifies that individual units of code (mostly functions) work as expected. Usually you write the test cases yourself, but some can be automatically generated. The output from a test can be as simple as a console output, to a “green light” in a GUI such as NUnit, or … Read more
The fundamental difference between the three strategies you’ve listed is whether or not the test code is in the same package as the code under test. The decision to use package myfunc or package myfunc_test in the test file depends on whether you want to perform white-box or black-box testing. There’s nothing wrong with using … Read more
I’ve introduced unit tests to code bases that did not have it previously. The last big project I was involved with where I did this the product was already in production with zero unit tests when I arrived to the team. When I left – 2 years later – we had 4500+ or so tests … Read more