Russ Cox: Go Testing by Example

1. gobyexample

   1 114 7,468 7.6 Go

   Go by Example

   

   Some similar resources I like:

   "Learn Go with Tests" book: https://quii.gitbook.io/learn-go-with-tests

   "Go by Example": https://gobyexample.com/

2. CodeRabbit

   coderabbit.ai featured

   CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.

   

3. testy

   2 3 46 6.3 Go

   typesafe (generics) helpers for better golang tests

   

   Agreed with most of this but I’m skeptical of the rsc.io/script dsl approach. I’ll try it, though, because Russ is often right.

   shameless advert: do you wish testify was implemented with generics and go-cmp, and had a more understandable surface area? Check out my small zero-dep library, Testy https://github.com/peterldowns/testy

   shameless advert: do you want to write tests against your postgres database, but each new test adds seconds to your test suite? Check out pgtestdb, the marginal cost of each test is measured in tens of milliseconds, and each test gets a unique and isolated postgres instance — with all your migrations applied. https://github.com/peterldowns/pgtestdb

4. pgtestdb

   3 3 262 7.0 Go

   quickly run tests in their own temporary, isolated, postgres databases

   

   Agreed with most of this but I’m skeptical of the rsc.io/script dsl approach. I’ll try it, though, because Russ is often right.

   shameless advert: do you wish testify was implemented with generics and go-cmp, and had a more understandable surface area? Check out my small zero-dep library, Testy https://github.com/peterldowns/testy

   shameless advert: do you want to write tests against your postgres database, but each new test adds seconds to your test suite? Check out pgtestdb, the marginal cost of each test is measured in tens of milliseconds, and each test gets a unique and isolated postgres instance — with all your migrations applied. https://github.com/peterldowns/pgtestdb

5. gotests

   4 10 5,014 0.0 Go

   Automatically generate Go test boilerplate from your source code.

   

   A huge time-saver for me when generating table-driven test boilerplate in Go has been using gotests[0] to generate the template.

   If you use VSCode with the Go extension it's already available there as a command "Go: Generate Unit Tests for Function/Package".

   [0] https://github.com/cweill/gotests

6. dotfiles

   5 8 344 8.4 Shell

   My dotfiles, managed with https://chezmoi.io. (by twpayne)

   

   chezmoi (<https://chezmoi.io> or <https://github.com/twpayne/chezmoi>) has a couple dozen txtar tests. They are both amazing and completely frustrating to use, but I don't think that there would be a better way to test most of what chezmoi does without them.

   Tom Payne (the creator and primary developer of chezmoi) has added some extra commands to the txtar context which makes things easier for certain classes of testing.

7. chezmoi

   6 60 14,377 9.8 Go

   Manage your dotfiles across multiple diverse machines, securely.

   

   chezmoi (<https://chezmoi.io> or <https://github.com/twpayne/chezmoi>) has a couple dozen txtar tests. They are both amazing and completely frustrating to use, but I don't think that there would be a better way to test most of what chezmoi does without them.

   Tom Payne (the creator and primary developer of chezmoi) has added some extra commands to the txtar context which makes things easier for certain classes of testing.

8. Txtar

   7 1 0 10.0 Swift

   Swift implementation of a txtar parser and formatter.

   

9. SaaSHub

   www.saashub.com featured

   SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

   

10. skeema

    8 8 1,297 8.5 Go

    Declarative pure-SQL schema management for MySQL and MariaDB

    

    Using tmpfs for MySQL/MariaDB's data directory helps tremendously. If you're using Docker natively on Linux, use `docker run --tmpfs /var/lib/mysql ...` and that'll do the trick. Only downside is each container restart is slightly slower due to having to re-init the database instance from scratch.

    Tuning the database server settings can help a lot too. You can add overrides to the very end of your `docker run` command-line, so that they get sent as command-line args to the database server. For example, use --skip-performance-schema to avoid the overhead of performance_schema if you don't need it in your test/CI environment.

    For MySQL 8 in particular, I've found a few additional options help quite a lot: --skip-innodb-adaptive-hash-index --innodb-log-writer-threads=off --skip-log-bin

    A lot of other options may be workload-specific. My product Skeema [1] can optionally use ephemeral containerized databases [2] for testing DDL and linting database objects, so the workload is very DDL-heavy, which means the settings can be tuned pretty differently than a typical DML-based workload.

    [1] https://github.com/skeema/skeema/

    [2] https://www.skeema.io/docs/options/#workspace

Suggest a related project