Skip to content

Commit

Permalink
.
Browse files Browse the repository at this point in the history
  • Loading branch information
lihaoyi committed Dec 31, 2024
1 parent 02ea79d commit f14e983
Show file tree
Hide file tree
Showing 2 changed files with 7 additions and 2 deletions.
4 changes: 2 additions & 2 deletions blog/modules/ROOT/pages/3-selective-testing.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -14,8 +14,8 @@ or monorepo: picking which tests to run to validate a change or pull-request, be
running every test every time is costly and slow. This blog post will explore what
selective testing is all about, the different approaches you can take with selective
testing, based on my experience working on developer tooling and CI for the last decade at
Dropbox and Databricks. Lastly, we will discuss how selective testing is supported by
the Mill build tool.
Dropbox and Databricks. Lastly, we will discuss
xref:mill::large/selective-execution.adoc[how the Mill build tool supports selective testing].

// end::header[]

Expand Down
5 changes: 5 additions & 0 deletions blog/modules/ROOT/pages/4-flaky-tests.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -154,6 +154,11 @@ mitigate them:
4. Mock out external services: e.g. AWS and Azure can be mocked using https://www.localstack.cloud/[LocalStack], parts of Azure
Kubernetes can be mocked using https://kind.sigs.k8s.io/[KIND], etc..
5. xref:3-selective-testing.adoc[Selective Testing], e.g. via
xref:mill::large/selective-execution.adoc[Mill's Selective Test Execution], reduces the
number of tests you run
and thus the impact of flakiness,
However, although you can mitigate the flakiness, you should not expect to make it go away
entirely.

Expand Down

0 comments on commit f14e983

Please sign in to comment.