You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/guides/modules/test/pages/adaptive-testing.adoc
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ Adaptive testing reduces test execution time while maintaining test confidence.
20
20
21
21
The following list shows some examples of where adaptive testing can be most beneficial:
22
22
23
-
* Unit and integration tests that exercise code within the same repository.
23
+
* Tests that exercise code within the same repository.
24
24
* Projects with comprehensive test coverage. The more thorough your tests, the more precisely adaptive testing can identify which tests are impacted by changes.
25
25
* Test frameworks with built-in coverage support (Jest, pytest, Go test, Vitest) where generating coverage reports is straightforward.
26
26
+
@@ -29,8 +29,8 @@ TIP: In codebases with sparse test coverage, adaptive testing cannot accurately
29
29
== Limitations
30
30
31
31
* Generating code coverage data is essential for determining how tests are related to code. If tests are run in a way that makes generating and accessing code coverage data tricky then adaptive testing may not be a good fit.
32
+
* Adaptive testing works best when testing a single deployable artifact. For example, a monorepo with integration tests that span multiple packages/services, especially when services run in separate container, makes coverage generation and consolidation difficult.
32
33
* Adaptive testing needs to be configured with commands to discover all available tests and run a subset of those tests. If you cannot run commands to discover tests and run a subset of tests on the CLI then adaptive testing may not be a good fit.
33
-
* Adaptive testing works best when testing a single deployable unit. A monorepo which performs integration tests across many packages at once may not be a good fit.
. Upgrade your Nomad clients and servers (if externalized) Terraform modules to the link:https://github.com/CircleCI-Public/server-terraform/releases/tag/4.8.0[4.8 release]. Follow the documentation to plan and apply the Terraform changes for your xref:phase-3-aws-execution-environments.adoc#create-your-cluster-with-terraform[AWS] or xref:phase-3-gcp-execution-environments.adoc#create-your-cluster-with-terraform[GCP] environment.
47
+
. Upgrade your Nomad clients and servers (if externalized) Terraform modules to the link:https://github.com/CircleCI-Public/server-terraform/releases/tag/{serverversion48}[4.8 release]. Follow the documentation to plan and apply the Terraform changes for your xref:phase-3-aws-execution-environments.adoc#create-your-cluster-with-terraform[AWS] or xref:phase-3-gcp-execution-environments.adoc#create-your-cluster-with-terraform[GCP] environment.
0 commit comments