Explore >> Select a destination
|
You are here 
|
ted.dev | ||
| | | | |
konradreiche.com
|
|
| | | | | There are different ways of separating integration tests from your unit tests in Go. After discovering too many issues with some of the approaches I have settled with the following. func TestDatabase(t *testing.T) { integrationTest(t) // ... } func integrationTest(t *testing.T) { t.Helper() if os.Getenv("INTEGRATION") == "" { t.Skip("skipping integration tests, set environment variable INTEGRATION") } } Integration tests are marked as such at the top of the test function, similar to using t.Helper(). A test helper function is used to skip the test unless the environment variable is set. All tests, including integration tests, can be run with: | |
| | | | |
higher-order-logic.github.io
|
|
| | | | | I've been reading James Shore's pattern language, Testing without Mocks with interest. It has some interesting ideas and, for me, some points of disagreement. | |
| | | | |
www.devjoy.com
|
|
| | | | | Site template made by devcows using hugo | |
| | | | |
www.preemptive.com
|
|
| | | This introduction to SaaS application security explores how a proper security posture can protect software companies, and the attacks it prevents. | ||
