Record · corpus.blog/posts/01a0b877-b1f1-7159-9ad7-c6d512a322fa

Test Failures Should Be Actionable

testing.googleblog.com · published 6 May 2024

A record is what was published and who pointed at it. The text of the post is not held here: read it at the source, or at its Wayback capture.

Read the post at testing.googleblog.com Wayback capture

1blogs citing

First cited: 17 May 2024
Most recent: 17 May 2024
Rank this month: not ranked
Links from this post: 17
Words captured: 430

Cited by

Blog

In the post

Date

seroter.com

Daily Reading List – May 17, 2024 (#321) Read at the source ↗

17 May 2024

Links from this post

Link

Host

http://googletesting.blogspot.com/2007/01/introducing-testing-on-toilet.html

googletesting.blogspot.com

https://docs.google.com/document/d/1YdwFRS4UEMlDVc3cUtVF9wB9xKODgcMCf7vYGKNdKTU/edit

docs.google.com

https://abseil.io/resources/swe-book

abseil.io

https://abseil.io/resources/swe-book/html/ch12.html

abseil.io

https://junit.org/

junit.org

https://truth.dev/

truth.dev

https://docs.pytest.org/en/8.0.x/

docs.pytest.org

https://google.github.io/googletest/

google.github.io

How I Learned To Stop Writing Brittle Tests and Love Expressive APIs Read at the source ↗

testing.googleblog.com

https://sre.google/sre-book/monitoring-distributed-systems/

sre.google

https://abseil.io/

abseil.io

https://google.github.io/googletest/reference/matchers.html

google.github.io

Testing on the Toilet: Writing Descriptive Test Names Read at the source ↗

testing.googleblog.com

Testing on the Toilet: Keep Tests Focused Read at the source ↗

testing.googleblog.com

Prefer Narrow Assertions in Unit Tests Read at the source ↗

testing.googleblog.com

https://protobuf.dev/

protobuf.dev

Testing on the Toilet: Keep Cause and Effect Clear Read at the source ↗

testing.googleblog.com