Go Testing By Example (GopherCon Australia 2023)

Показать описание

Russ Cox

Рекомендации по теме

Комментарии

Thanks for re-recording and sharing, I really appreciate it.

Anuragntnx

05:02 Tip #01: Make it easy to add new test cases.
06:05 Tip #02: Use test coverage to find untested code.
07:26 Tip #03: Coverage is no substitute for thought.
09:21 Tip #04: Write exhaustive tests.
11:39 Tip #05: Separate test cases from test logic.
12:01 Tip #06: Look for special cases.
13:30 Tip #07: If you didn’t add a test, you didn’t fix the bug.
15:26 Tip #08: Not everything fits in a table.
17:28 Tip #09: Test cases can be in testdata files.
17:57 Tip #10: Compare against other implementations.
19:46 Tip #11: Make test failures readable.
20:57 Tip #12: If the answer can change, write code to update them.
21:41 Tip #13: Use txtar for multi-file test cases.
24:56 Tip #14: Annotate existing formats to create testing mini-languages.
26:38 Tip #15: Write parsers and printers to simplify tests.
28:36 Tip #16: Code quality is limited by test quality.
30:14 Tip #17: Scripts make good tests.
30:53 Tip #18: Try rsc.io/script for your own script-based test cases.
32:00 Tip #19: Improve your tests over time.
33:14 Tip #20: Aim for continuous deployment.

something

That's good food for thought! Thank you for re-recording and sharing

VictorBreder

Awesome presentation, your Script tool seems very useful. Thanks Russ!

ncfr

I kinda like *and* dislike the advise for the DSL. Sometimes an internal DSL is really nicer b/c of the IDE integration and completion. Then again, maybe a DSL as shown should be so KISS that its usage should be obvious.

ytdlgandalf

Great stuff! Though one thing I've noticed, syntax on 16:42 is missing "range"

nitroflap

Great content, but the loud buzzing sound is a turnoff. Too bad.

jubbs

4:16 "If they want to make a change, ... they just *mail* the change."
What do you mean by "mail" the change? Why are you mailing changes?

ash

Nice presentation, thanks for that.
I would add that following TDD is able to solve many of the issues you raised but I understand that it's not everyone cup of tea :)

bhdasne

I like to write my tests with random data using Gofakeit

BrianVoelker

Go Testing By Example (GopherCon Australia 2023)

Go Testing By Example (GopherCon Australia 2023)

GopherCon 2017: Advanced Testing with Go - Mitchell Hashimoto

GopherCon UK 2021: Eleni Fragkiadaki - Test coverage in Go, the whole package

A hands-on guide for proper Unit Testing in Go!

Writing Microservice Integration Tests in Go (Finally) - GopherCon SG 2019

GopherCon UK 2018: Sean Kelly - Go Test: Under the Hood

GopherCon 2022: Test Go Service Integration Using Contracts - Aparna Chaudhari

Golang UK Conference 2016 - Marcel van Lohuizen - Advanced Testing Concepts

GopherCon 2019: Optimizing Go Code Without a Blindfold - Daniel Marti

GopherCon 2020: Build and Test Caching in Go - Kevin Burke

GopherCon 2015: Go Dynamic Tools - Dmitry Vyukov

GopherCon 2017: Forward Compatible Go Code - Joe Tsai

GopherCon 2021: How we Go at Zillow - Arish Labroo

GopherCon UK 2021: Riya Dattani & Chris James - Acceptance Tests, BDD & GO

GopherCon 2019: Get Going with WebAssembly - Johan Brandhorst

GopherCon 2022: Secure Coding in Go: Avoiding Common Vulnerabilities - Benji Vesterby

Optimizing Go code without a blindfold - GopherCon SG 2019

GopherCon 2021: Writing Mocks for Good Unit Tests - Gabriel Mateus Bussolo Ferreira

GopherCon 2022: Go, the Data Engineer's Missing Tool? - Juan Brandao

GopherCon 2019: Tracking Inter-process Dependencies - Mike Seplowitz

19. Rob Pike - What We Got Right, What We Got Wrong | GopherConAU 2023

GopherCon 2017: Writing a Go Tool to Parse and Modify Struct Tags - Fatih Arslan

GopherCon 2017: Go Reliability and Durability at Dropbox - Tammy Butow

GopherCon 2019: Go, pls stop breaking my editor - Rebecca Stambler