Explore >> Select a destination
|
You are here 
|
blog.nuculabs.de | ||
| | | | |
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: | |
| | | | |
testandanalysis.home.blog
|
|
| | | | | The SIGiST Committee at the conference The SIGiST Summer 2024 Conference was a great success. The British Computer Society hosted the conference at its London office. We had nearly 200 delegates, which is more than at previous conferences. Over twenty speakers gave interesting and inspiring talks. It was great to have speakers for whom this... | |
| | | | |
arne-mertz.de
|
|
| | | | | Contents Inmy last post I have written about the main and secondary usesof unit tests and how they compare to other kinds of automated tests. This time I will explore [...] | |
| | | | |
regulargeek.com
|
|
| | | Kubernetes starts our day with a post about Minikube, their way to run Kubernetes locally. It is not entirely standalone since it requires VirtualBox, but at least it is a step in the right direction. At the morning paper we get an excellent introduction into Goods, Google's tool for organizing datasets. This is one of... | ||
