# Testing only changed Go packages

DevFeed: [Testing only changed Go packages](<https://devfeed.tech/articles/testing-only-changed-go-packages-37735.md>)

Original publisher: [Read original article](<https://carlosbecker.com/posts/go-test-changed/>)

Author: Carlos Alexandro Becker

Published: 2024-12-30T00:00:00Z

Content type: tutorial

Language: en

Sources: [Carlos Becker](<https://devfeed.tech/sources/carlos-becker.md>)

Topics: [Go Language](<https://devfeed.tech/topics/go-language.md>), [Testing](<https://devfeed.tech/topics/testing.md>), [go test](<https://devfeed.tech/topics/go-test.md>), [Shell](<https://devfeed.tech/topics/shell.md>), [Caching](<https://devfeed.tech/topics/caching.md>), [Command-line interface](<https://devfeed.tech/topics/cli.md>)

Tags: [caching](<https://devfeed.tech/tags/caching.md>), [go](<https://devfeed.tech/tags/go.md>), [go-test](<https://devfeed.tech/tags/go-test.md>), [shell-script](<https://devfeed.tech/tags/shell-script.md>), [testing](<https://devfeed.tech/tags/testing.md>)

## 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.