Source code is available at http://github.com/orfjackal/gospec
First you must have Go installed on your machine, as instructed in Installing Go.
Install and Update
Download GoSpec using the
go get tool:
go get "github.com/orfjackal/gospec/src/gospec"
go help get for more instructions on using the tool.
See "Version History" for any additional upgrade notes.
Make a copy of the hello-world-template directory to get started. You can run its tests with the
go test command. All test files must end with
_test.go and all specs must be listed in
You can use the
go test command to run GoSpec's specs. The integration with gotest requires a couple of lines of boilerplate: you'll need to write a gotest test method, where you list all your specs and call GoSpec. See all_specs_test.go in the examples directory for an example. Also all your specs must be in files whose names end with
See gotest's documentation for instructions on how to use gotest.
GoSpec adds one additional parameter to gotest. Use the
-print-all parameter to print a list of all specs:
go test -print-all Otherwise only the failing specs are printed. The list of all specs can be useful as documentation.
The following imports are needed. The first imports the
gospec.Context interface and the second is needed for using GoSpec's expectation matchers (
Contains etc.) without having to prefix them with the package name. (In a future GoSpec version the matchers will be moved to their own package.)
import "github.com/orfjackal/gospec/src/gospec" import . "github.com/orfjackal/gospec/src/gospec"
The specs are written as functions which take
gospec.Context as a parameter. You can call the methods of
Context to declare expectations and nested specs.
For examples on how to write specs, see the files in the examples directory.
expectation_syntax_test.go explains the syntax for writing expectations.
execution_model_test.go explains GoSpec's runtime model, for example how the specs are isolated from each other and executed in parallel.
UPGRADE NOTES: Check your imports - when using the
go tool they are different than when using the old hand-written Makefiles.
- Build using the
gotool instead of Makefiles
- Upgraded to Go 1 (weekly.2012-02-07)
- Upgraded to Go release.r59 (weekly.2011-07-07)
- Upgraded to Go release.r58 (weekly.2011-06-23)
- Upgraded to Go release.r57.1 (weekly.2011-04-27)
- Upgraded to Go release.2011-01-20
- Upgraded to Go release.2010-10-13
- Fixed an occasional off-by-one in exception stack trace line numbers
- Upgraded to Go release.2010-09-29
- Issue 754 was fixed in Go release.2010-09-06, so line numbers in GoSpec's stack traces are now correct
- Fixed an occasional off-by-one in exception stack trace line numbers
- Upgraded to Go release.2010-09-06
UPGRADE NOTES: If you have written custom matchers, their result parameters' types have changed. Also the error messages are expected to be in a slightly different format. See expectation_syntax_test.go or GoSpec's built-in matchers for examples.
- New error message format
- Workaround for a bug in gedit 2.28.0 which caused stack traces to be sometimes non-clickable
- Improved the stack traces to hide GoSpec internals also for root specs
- Upgraded to Go release.2010-08-25
UPGRADE NOTES: In your spec suite, replace
r.AddSpec("SomeSpec", SomeSpec) with
- Recover from panics in specs and report their stack traces
- Retrieve the spec function names using reflection, to avoid some boilerplate in the spec suite
- Changes to error messages: function names and full file paths are now shown in the stack traces
- Improved documentation and provided a hello world project template
- Removed the deprecated
- Upgraded to Go release.2010-04-13
UPGRADE NOTES: In all your specs, replace
gospec.Context in the spec's parameters. Add
import . "gospec" to the imports and change every assertion of the old
c.Then(x).Should.Equal(y) syntax to use the new
c.Expect(x, Equals, y) syntax.
- New expectation syntax. The old
c.Then()syntax is deprecated and will be removed later.
- New matchers: IsSame, IsNil, IsTrue, IsFalse, ContainsAll, ContainsAny, ContainsExactly, ContainsInOrder, ContainsInPartialOrder
- Added Fibonacci numbers example
- Added instructions about the style of naming and organizing specs
- Minor changes to the print format of error messages
- Upgraded to Go release.2010-02-04
- Initial release
The following are a must, because they enable using specification-style the way I prefer:
Unlimited Nesting - The specs can be organized into a nested hierarchy. This makes it possible to apply One Assertion Per Test which isolates the reason for a failure, because the specs are very fine-grained. Many unit testing tools allow only 2 levels of nesting (e.g. JUnit) and a few only 1 level (e.g. gotest), but for specification-style at least 3 levels are needed (e.g. JDave), and once you have 3 levels you might as well implement unlimited levels with the same abstraction.
Isolated Execution - The specs must be isolated from the side-effects of their sibling specs. Each spec will see only the side-effects of its parent specs. In effect, the parent specs work similar to the "before" (and "after") test code in many test frameworks, and by default none of the specs can see its siblings (there will be a way to override the default). Without this isolation, it would be harder to write reliable side-effect free specs, which in turn would force the specs to be organized differently than what was desired.
No Forced Words - Getting the words right was the starting point for BDD, so it is absurd that almost all of the BDD frameworks force the programmer to use fixed words (describe, it, should, given, when, then etc.) which incline the programmer to write spec names as sentences which begin or end with those words. You should be able to choose yourself the best possible words that fit a situation. GoSpec uses the syntax
c.Specify("name", ...)for all levels in the specs, which leads to the word
Specifybecoming background noise, so that you ignore it and it does not force you to start your sentences with any particular word (using a meaningless word such as "Spec" would also be a good choice, as long as it is easy to pronounce when communicating with others).
The following are nice-to-haves, which make it more pleasant to use the framework:
Plain Text Names - You can use any Unicode characters in the spec names, because they are declared as strings. Using only those characters that are allowed in method names would be too limiting and hard to read.
Fluent API - The syntax for writing specs should be easily readable. It should be obvious that what an assert does, and which is the expected and which the actual value. Also writing the specs should be easy, requiring as little syntax as possible, but readability has always higher priority than writability.
Parallel Execution - Running the specs quickly (i.e. less than 10-20 seconds) is a must for using TDD, so being able to take advantage of all processing power is important, and multiple CPU cores is the only way to go fast in the foreseen future. GoSpec executes the specs using as much parallelism as possible (one goroutine for each leaf spec), so that it would be possible to utilize all available CPU cores (just remember to set GOMAXPROCS).