Explore >> Select a destination
|
You are here 
|
markphelps.me | ||
| | | | |
atilaoncode.blog
|
|
| | | | | D has built-in unit tests, and unittest is even a keyword. This has been fantastically successful for the language, since there is no need to use an external framework to write tests, it comes with the compiler. Just as importantly, a unittest after a function can be used as documentation, with the test(s) showing up... | |
| | | | |
threedots.tech
|
|
| | | | | In this guide, we share our pragmatic approach to Clean Architecture in Go, refined through years of real-world experimentation. We demonstrate refactoring techniques on a live project, showing how to extract application logic, define interfaces, and improve testability. You'll learn how to apply Clean Architecture principles in an idiomatic Go way, balancing theory with practical implementation. Our battle-tested methods help you create loosely coupled, highly cohesive code that's easier to maintain and extend over time. | |
| | | | |
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: | |
| | | | |
openjsf.org
|
|
| | | OpenJS Foundation and 7ASecurity collaborated on the nvm security audit with the Open Source Technology Improvement Fund (OSTIF) as a result of the latest funding from the Sovereign Tech Fund. | ||
