Explore >> Select a destination
|
You are here 
|
filipnikolovski.com | ||
| | | | |
anthonysciamanna.com
|
|
| | | | | This is the second post in my series about writing effective unit tests. This series covers questions and challenges that typically arise when teams begin... | |
| | | | |
www.philosophicalhacker.com
|
|
| | | | | ||
| | | | |
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: | |
| | | | |
blog.sanctum.geek.nz
|
|
| | | [AI summary] The provided text is a collection of various technical topics and articles, including: 1) A guide on using command-line tools for development, covering debugging, profiling, and performance analysis with tools like GDB, Valgrind, and others. 2) An in-depth look at version control systems, from early systems like RCS and CVS to modern ones like Git and Mercurial. 3) A discussion on shell scripting, including Bash, custom commands, and automation. 4) A series of articles on Vim, covering configuration, diffing, and debugging within the editor. 5) Miscellaneous topics such as terminal usage, shell configuration, and system administration practices. The content is written in a technical style, suitable for developers and system administrators workin... | ||
