# go test Published articles for go test. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Testing only changed Go packages DevFeed: [Testing only changed Go packages]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2024-12-30T00:00:00Z Content type: tutorial Language: en Sources: [Carlos Becker]() Topics: [Go Language](), [Testing](), [go test](), [Shell](), [Caching](), [Command-line interface]() Tags: [caching](), [go](), [go-test](), [shell-script](), [testing]() ### AI overview A practical shell script tip for running tests only in changed Go packages, with an additional file-watching workflow for rerunning tests when files change. The article explains that this approach can be faster but is less correct than running the full test suite, which should always run in CI. ### Source excerpt Sometimes, working on big projects, running all tests locally take too much time. ## Contextual logging in Kubernetes 1.29: Better troubleshooting and enhanced logging DevFeed: [Contextual logging in Kubernetes 1.29: Better troubleshooting and enhanced logging]() Original publisher: [Read original article]() Author: The Kubernetes Authors Published: 2023-12-20T17:30:00Z Content type: release Language: en Sources: [Kubernetes Contributors Blog]() Topics: [Kubernetes](), [Logging](), [Instrumentation](), [telemetry]() Tags: [go-test](), [instrumentation](), [kubernetes](), [logging](), [logs](), [tests](), [troubleshooting](), [unit-tests]() ### AI overview The article announces that Kubernetes contextual logging, introduced in Kubernetes v1.24, has been migrated to kube-scheduler, kube-controller-manager, and some directories. Based on the go-logr API, the feature passes logger instances through callers to support structured logs with additional context, improving troubleshooting and test output in parallel applications. ### Source excerpt On behalf of the Structured Logging Working Group and SIG Instrumentation , we are pleased to announce that the contextual logging feature introduced in Kubernetes v1.24 has now been successfully migrated to two components (kube-scheduler and kube-controller-manager) as well as some directories. This feature aims to provide more useful logs for better troubleshooting of Kubernetes and to empower developers to enhance Kubernetes. What is contextual logging? Contextual logging is based on the go-logr API. The key idea is that libraries are passed a logger instance by their caller and use that for logging instead of accessing a global logger. The binary decides the logging implementation, not the libraries. The go-logr API is designed around structured logging and supports attaching additional information to a logger. This enables additional use cases: The caller can attach additional information to a logger: WithName adds a "logger" key with the names concatenated by a dot as value WithValues adds key/value pairs When passing this extended logger into a function, and the function uses it instead of the global logger, the additional information is then included in all log entries, without having to modify the code that generates the log entries. This is useful in highly parallel applications where it can become hard to identify all log entries for a certain operation, because the output from different operations gets interleaved. When running unit tests, log output can be associated with the current test. Then, when a test fails, only the log output of the failed test gets shown by go test. That output can also be more verbose by default because it will not get shown for successful tests. Tests can be run in parallel without interleaving their output. One of the design decisions for contextual logging was to allow attaching a logger as value to a context.Context. Since the logger encapsulates all aspects of the intended logging for the call, it is part of the context, ## Table driven tests in Go DevFeed: [Table driven tests in Go]() Original publisher: [Read original article]() Published: 2023-01-19T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Go Language](), [test]() Tags: [documentation](), [go](), [go-test](), [golang](), [how-to](), [learn](), [table-driven-tests](), [tests](), [tips](), [unit-tests](), [video]() ### AI overview A video tutorial explains table-driven tests in Go and shows how sub-tests can make failing cases easier to identify when testing many inputs. ### Source excerpt Introduction Table tests are a great way to test different inputs and associated outputs for a function in Go. To write a table test, you define a slice of some data struct with fields of the input data you'll need and the expected outcome. Then you can loop through this slice and pass the data stored for each element to your function. One disadvantage of table tests is as the data set in your slice grows, the harder it is to find the failing case. Luckily, Miki will share some tips to manage this with the Go test suite. ## go test -v streaming output DevFeed: [go test -v streaming output]() Original publisher: [Read original article]() Author: Dave Cheney Published: 2020-03-10T07:03:03Z Content type: article Language: en Sources: [Dave Cheney]() Topics: [Go Language](), [Streaming](), [Testing](), [Unit testing]() Tags: [go](), [go-test](), [integration](), [programming](), [retry](), [standard-library](), [streaming](), [testing](), [unit-test](), [unit-testing]() ### AI overview The article explains that Go 1.14 streams test output as it is produced when using -v, instead of buffering output until the test finishes. This improves visibility when debugging long-running or retrying integration tests. ### Source excerpt The testing package is one of my favourite packages in the Go standard library, not just because of its low noise approach to unit testing, but, over the lifetime of Go, it has received a steady stream of quality of life improvements driven by real world usage. The most recent example of this is, in [...] ## Write Your Go Programs Using GEdit DevFeed: [Write Your Go Programs Using GEdit]() Original publisher: [Read original article]() Published: 2013-11-23T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Go Language](), [Development](), [Tooling](), [Python](), [Linux]() Tags: [ardan-labs](), [blog](), [build](), [go](), [go-development](), [go-programming](), [go-test](), [golang](), [linux](), [programming](), [python](), [tooling](), [ubuntu]() ### AI overview This guest post describes using GEdit for Go development and introduces GoBuild, a Python plug-in for GEdit 3.x that runs go build when Go source files are saved and runs go test for test files. ### Source excerpt This is a guest post from Tad Vizbaras from Etasoft in South Florida. There are a number of editors and IDEs for Go development. LiteIde, Vim, Emacs and GEdit just to name a few. Each developer has their own favorite editor for each language they work with. Some like full featured IDE environments while others prefer speed over features. My personal favorite editors for Go development at the moment are Vim and GEdit. GEdit comes as part of many Linux distros. If you use Ubuntu, it is part of the operating system. GEdit has some decent features like: * Syntax Highlighting * Split Windows * Word Wrapping Advanced features are left to be handled by external plug-ins. I prefer project-less development. That means there are no formal project files and projects are preserved via a workspace bound to a directory structure. Go has excellent support for project-less development. When building and installing your projects, the Go tooling, in conjunction with the way Go packages code, can minimize the need for external scripts and makefiles. GEdit is a decent editor but I could not find any good Plug-ins that would allow me to perform a Go build right from the editor. The "External Tools" Plug-in has worked for me. I was able to set up shortcuts and get "go build" to execute. When you click on errors, displayed in the bottom pane of GEdit, the cursor jumps to exact error location. When I started programming in Go, the "External Tools" Plug-in worked for me for quite some time. But after awhile, I started to wish that "go build" would run similar to how Linters ran. With Linters, you can run a command after the file is saved. Since Go usually takes only few seconds to build, the Plug-in could execute a "go build" on save and then jump to the error location if there were any. I wrote a GEdit Plug-in that is developed in Python. Depending on the version of Python you have installed, you may require some small adjustments. This is covered in the Known Issues section below. Ops, I