comments"
- - link: "/continuous_integration/static_analysis/rules/typescript-code-style/ban-tslint-comment"
+ - link: "/static_analysis/rules/typescript-code-style/ban-tslint-comment"
tag: "ban-tslint-comment"
text: "Avoid using TSLint comments"
- - link: "/continuous_integration/static_analysis/rules/typescript-code-style/class-name"
+ - link: "/static_analysis/rules/typescript-code-style/class-name"
tag: "class-name"
text: "Class name should be PascalCase"
- - link: "/continuous_integration/static_analysis/rules/typescript-code-style/eqeqeq"
+ - link: "/static_analysis/rules/typescript-code-style/eqeqeq"
tag: "eqeqeq"
text: "Enforce the use of === and !=="
- - link: "/continuous_integration/static_analysis/rules/typescript-code-style/func-name-matching"
+ - link: "/static_analysis/rules/typescript-code-style/func-name-matching"
tag: "func-name-matching"
text: "Function names must match the name of the assignation"
- - link: "/continuous_integration/static_analysis/rules/typescript-code-style/func-names"
+ - link: "/static_analysis/rules/typescript-code-style/func-names"
tag: "func-names"
text: "Enforce named function expressions"
- - link: "/continuous_integration/static_analysis/rules/typescript-code-style/function-naming"
+ - link: "/static_analysis/rules/typescript-code-style/function-naming"
tag: "function-naming"
text: "Function name should use camelCase or PascalCase"
- - link: "/continuous_integration/static_analysis/rules/typescript-code-style/max-class-lines"
+ - link: "/static_analysis/rules/typescript-code-style/max-class-lines"
tag: "max-class-lines"
text: "Classes must be less than 100 lines"
- - link: "/continuous_integration/static_analysis/rules/typescript-code-style/max-function-lines"
+ - link: "/static_analysis/rules/typescript-code-style/max-function-lines"
tag: "max-function-lines"
text: "Functions must be less than 200 lines"
- - link: "/continuous_integration/static_analysis/rules/typescript-code-style/max-params"
+ - link: "/static_analysis/rules/typescript-code-style/max-params"
tag: "max-params"
text: "Enforce a maximum number of parameters in a function"
- - link: "/continuous_integration/static_analysis/rules/typescript-code-style/method-name"
+ - link: "/static_analysis/rules/typescript-code-style/method-name"
tag: "method-name"
text: "Method name should use camelCase"
- - link: "/continuous_integration/static_analysis/rules/typescript-code-style/no-array-constructor"
+ - link: "/static_analysis/rules/typescript-code-style/no-array-constructor"
tag: "no-array-constructor"
text: "Avoid Array constructors"
- - link: "/continuous_integration/static_analysis/rules/typescript-code-style/no-confusing-non-null-assertion"
+ - link: "/static_analysis/rules/typescript-code-style/no-confusing-non-null-assertion"
tag: "no-confusing-non-null-assertion"
text: "Avoid non-null assertion in confusing locations"
- - link: "/continuous_integration/static_analysis/rules/typescript-code-style/no-div-regex"
+ - link: "/static_analysis/rules/typescript-code-style/no-div-regex"
tag: "no-div-regex"
text: "Avoid equal signs explicitly at the beginning of regex"
- - link: "/continuous_integration/static_analysis/rules/typescript-code-style/no-duplicate-imports"
+ - link: "/static_analysis/rules/typescript-code-style/no-duplicate-imports"
tag: "no-duplicate-imports"
text: "Avoid duplicate module imports"
- - link: "/continuous_integration/static_analysis/rules/typescript-code-style/no-empty-interface"
+ - link: "/static_analysis/rules/typescript-code-style/no-empty-interface"
tag: "no-empty-interface"
text: "Avoid the declaration of empty interfaces"
- - link: "/continuous_integration/static_analysis/rules/typescript-code-style/no-floating-decimal"
+ - link: "/static_analysis/rules/typescript-code-style/no-floating-decimal"
tag: "no-floating-decimal"
text: "Avoid leading or trailing decimal points in numbers"
- - link: "/continuous_integration/static_analysis/rules/typescript-code-style/no-inferrable-types"
+ - link: "/static_analysis/rules/typescript-code-style/no-inferrable-types"
tag: "no-inferrable-types"
text: "Avoid explicit type declarations for variables and params"
- - link: "/continuous_integration/static_analysis/rules/typescript-code-style/no-lonely-if"
+ - link: "/static_analysis/rules/typescript-code-style/no-lonely-if"
tag: "no-lonely-if"
text: "Avoid if statements as the only statement in else blocks"
- - link: "/continuous_integration/static_analysis/rules/typescript-code-style/no-multi-assign"
+ - link: "/static_analysis/rules/typescript-code-style/no-multi-assign"
tag: "no-multi-assign"
text: "Avoid the use of chained assignment expressions"
- - link: "/continuous_integration/static_analysis/rules/typescript-code-style/no-new"
+ - link: "/static_analysis/rules/typescript-code-style/no-new"
tag: "no-new"
text: "Avoid new operators outside of assignments or comparisons"
- - link: "/continuous_integration/static_analysis/rules/typescript-code-style/no-new-func"
+ - link: "/static_analysis/rules/typescript-code-style/no-new-func"
tag: "no-new-func"
text: "Avoid new operators with the Function object"
- - link: "/continuous_integration/static_analysis/rules/typescript-code-style/no-new-object"
+ - link: "/static_analysis/rules/typescript-code-style/no-new-object"
tag: "no-new-object"
text: "Avoid Object constructors"
- - link: "/continuous_integration/static_analysis/rules/typescript-code-style/no-return-assign"
+ - link: "/static_analysis/rules/typescript-code-style/no-return-assign"
tag: "no-return-assign"
text: "Avoid assignment operators in return statements"
- - link: "/continuous_integration/static_analysis/rules/typescript-code-style/no-self-compare"
+ - link: "/static_analysis/rules/typescript-code-style/no-self-compare"
tag: "no-self-compare"
text: "Avoid comparisons where both sides are exactly the same"
- - link: "/continuous_integration/static_analysis/rules/typescript-code-style/no-useless-empty-export"
+ - link: "/static_analysis/rules/typescript-code-style/no-useless-empty-export"
tag: "no-useless-empty-export"
text: "Avoid empty exports that don't change anything"
- - link: "/continuous_integration/static_analysis/rules/typescript-code-style/no-var"
+ - link: "/static_analysis/rules/typescript-code-style/no-var"
tag: "no-var"
text: "Require let or const instead of var"
- - link: "/continuous_integration/static_analysis/rules/typescript-code-style/parameter-name"
+ - link: "/static_analysis/rules/typescript-code-style/parameter-name"
tag: "parameter-name"
text: "Parameter name should use camelCase"
- - link: "/continuous_integration/static_analysis/rules/typescript-code-style/radix"
+ - link: "/static_analysis/rules/typescript-code-style/radix"
tag: "radix"
text: "Consistent use of the radix argument using parseInt"
typescript_common_security_data:
- - link: "/continuous_integration/static_analysis/rules/typescript-common-security/axios-avoid-insecure-http"
+ - link: "/static_analysis/rules/typescript-common-security/axios-avoid-insecure-http"
tag: "axios-avoid-insecure-http"
text: "Avoid insecure HTTP requests with Axios"
- - link: "/continuous_integration/static_analysis/rules/typescript-common-security/unique-function-arguments"
+ - link: "/static_analysis/rules/typescript-common-security/unique-function-arguments"
tag: "unique-function-arguments"
text: "Function argument names should be unique"
- - link: "/continuous_integration/static_analysis/rules/typescript-common-security/xml-no-external-entities"
+ - link: "/static_analysis/rules/typescript-common-security/xml-no-external-entities"
tag: "xml-no-external-entities"
text: "Do not use external XML entities"
typescript_express_data:
- - link: "/continuous_integration/static_analysis/rules/typescript-express/access-restriction"
+ - link: "/static_analysis/rules/typescript-express/access-restriction"
tag: "access-restriction"
text: "Limit exposure to sensitive directories and files"
- - link: "/continuous_integration/static_analysis/rules/typescript-express/default-session-config"
+ - link: "/static_analysis/rules/typescript-express/default-session-config"
tag: "default-session-config"
text: "Enforce overriding default config"
- - link: "/continuous_integration/static_analysis/rules/typescript-express/external-filename-upload"
+ - link: "/static_analysis/rules/typescript-express/external-filename-upload"
tag: "external-filename-upload"
text: "Avoid using unsanitized user input with sendFile"
- - link: "/continuous_integration/static_analysis/rules/typescript-express/external-resource"
+ - link: "/static_analysis/rules/typescript-express/external-resource"
tag: "external-resource"
text: "Avoid rendering resource based on unsanitized user input"
- - link: "/continuous_integration/static_analysis/rules/typescript-express/hardcoded-secret"
+ - link: "/static_analysis/rules/typescript-express/hardcoded-secret"
tag: "hardcoded-secret"
text: "Avoid using a hard-coded secret"
- - link: "/continuous_integration/static_analysis/rules/typescript-express/https-protocol-missing"
+ - link: "/static_analysis/rules/typescript-express/https-protocol-missing"
tag: "https-protocol-missing"
text: "Use `https` protocol over `http`"
- - link: "/continuous_integration/static_analysis/rules/typescript-express/insecure-allow-origin"
+ - link: "/static_analysis/rules/typescript-express/insecure-allow-origin"
tag: "insecure-allow-origin"
text: "Avoid using an insecure Access-Control-Allow-Origin header"
- - link: "/continuous_integration/static_analysis/rules/typescript-express/insecure-cookie"
+ - link: "/static_analysis/rules/typescript-express/insecure-cookie"
tag: "insecure-cookie"
text: "Avoid setting insecure cookie settings"
- - link: "/continuous_integration/static_analysis/rules/typescript-express/jwt-not-revoked"
+ - link: "/static_analysis/rules/typescript-express/jwt-not-revoked"
tag: "jwt-not-revoked"
text: "Ensure an isRevoked method is used for tokens"
- - link: "/continuous_integration/static_analysis/rules/typescript-express/missing-helmet"
+ - link: "/static_analysis/rules/typescript-express/missing-helmet"
tag: "missing-helmet"
text: "Express application should use Helmet"
- - link: "/continuous_integration/static_analysis/rules/typescript-express/path-traversal"
+ - link: "/static_analysis/rules/typescript-express/path-traversal"
tag: "path-traversal"
text: "Avoid allowing access to unintended directories or files"
- - link: "/continuous_integration/static_analysis/rules/typescript-express/reduce-server-fingerprinting"
+ - link: "/static_analysis/rules/typescript-express/reduce-server-fingerprinting"
tag: "reduce-server-fingerprinting"
text: "Server fingerprinting misconfiguration"
- - link: "/continuous_integration/static_analysis/rules/typescript-express/xss-vulnerability"
+ - link: "/static_analysis/rules/typescript-express/xss-vulnerability"
tag: "xss-vulnerability"
text: "Avoid sending unsanitized user input in response"
typescript_inclusive_data:
- - link: "/continuous_integration/static_analysis/rules/typescript-inclusive/comments"
+ - link: "/static_analysis/rules/typescript-inclusive/comments"
tag: "comments"
text: "Check comments for wording issues"
- - link: "/continuous_integration/static_analysis/rules/typescript-inclusive/declarations"
+ - link: "/static_analysis/rules/typescript-inclusive/declarations"
tag: "declarations"
text: "Check declaration names for wording issues"
- - link: "/continuous_integration/static_analysis/rules/typescript-inclusive/formal-parameters"
+ - link: "/static_analysis/rules/typescript-inclusive/formal-parameters"
tag: "formal-parameters"
text: "Check parameter names for wording issues"
- - link: "/continuous_integration/static_analysis/rules/typescript-inclusive/identifiers"
+ - link: "/static_analysis/rules/typescript-inclusive/identifiers"
tag: "identifiers"
text: "Check identifier names for wording issues"
typescript_node_security_data:
- - link: "/continuous_integration/static_analysis/rules/typescript-node-security/argon2"
+ - link: "/static_analysis/rules/typescript-node-security/argon2"
tag: "argon2"
text: "Use strong security mechanisms with argon2"
- - link: "/continuous_integration/static_analysis/rules/typescript-node-security/avoid-crypto-rc4"
+ - link: "/static_analysis/rules/typescript-node-security/avoid-crypto-rc4"
tag: "avoid-crypto-rc4"
text: "Avoid RC4"
- - link: "/continuous_integration/static_analysis/rules/typescript-node-security/avoid-crypto-sha1"
+ - link: "/static_analysis/rules/typescript-node-security/avoid-crypto-sha1"
tag: "avoid-crypto-sha1"
text: "Avoid SHA1 security protocol"
- - link: "/continuous_integration/static_analysis/rules/typescript-node-security/avoid-des"
+ - link: "/static_analysis/rules/typescript-node-security/avoid-des"
tag: "avoid-des"
text: "Avoid DES and 3DES"
- - link: "/continuous_integration/static_analysis/rules/typescript-node-security/chmod-permissions"
+ - link: "/static_analysis/rules/typescript-node-security/chmod-permissions"
tag: "chmod-permissions"
text: "Do not give 777 permissions to a file"
- - link: "/continuous_integration/static_analysis/rules/typescript-node-security/command-injection"
+ - link: "/static_analysis/rules/typescript-node-security/command-injection"
tag: "command-injection"
text: "Avoid command injection"
- - link: "/continuous_integration/static_analysis/rules/typescript-node-security/crypto-avoid-weak-hash"
+ - link: "/static_analysis/rules/typescript-node-security/crypto-avoid-weak-hash"
tag: "crypto-avoid-weak-hash"
text: "Avoid weak hash algorithm from CryptoJS"
- - link: "/continuous_integration/static_analysis/rules/typescript-node-security/detect-buffer-noassert"
+ - link: "/static_analysis/rules/typescript-node-security/detect-buffer-noassert"
tag: "detect-buffer-noassert"
text: "Avoid calls to 'buffer' with 'noAssert' flag set"
- - link: "/continuous_integration/static_analysis/rules/typescript-node-security/detect-child-process"
+ - link: "/static_analysis/rules/typescript-node-security/detect-child-process"
tag: "detect-child-process"
text: "Avoid instances of 'child_process' and non-literal 'exec()'"
- - link: "/continuous_integration/static_analysis/rules/typescript-node-security/detect-eval-with-expression"
+ - link: "/static_analysis/rules/typescript-node-security/detect-eval-with-expression"
tag: "detect-eval-with-expression"
text: "Avoid `eval` with expressions"
- - link: "/continuous_integration/static_analysis/rules/typescript-node-security/detect-new-buffer"
+ - link: "/static_analysis/rules/typescript-node-security/detect-new-buffer"
tag: "detect-new-buffer"
text: "Avoid Buffer(argument) with non-literal values"
- - link: "/continuous_integration/static_analysis/rules/typescript-node-security/detect-non-literal-fs-filename"
+ - link: "/static_analysis/rules/typescript-node-security/detect-non-literal-fs-filename"
tag: "detect-non-literal-fs-filename"
text: "Avoid variables in 'fs' calls filename argument"
- - link: "/continuous_integration/static_analysis/rules/typescript-node-security/detect-non-literal-regexp"
+ - link: "/static_analysis/rules/typescript-node-security/detect-non-literal-regexp"
tag: "detect-non-literal-regexp"
text: "Detects non-literal values in regular expressions"
- - link: "/continuous_integration/static_analysis/rules/typescript-node-security/detect-non-literal-require"
+ - link: "/static_analysis/rules/typescript-node-security/detect-non-literal-require"
tag: "detect-non-literal-require"
text: "Avoid require with non-literal values"
- - link: "/continuous_integration/static_analysis/rules/typescript-node-security/detected-jwt-token"
+ - link: "/static_analysis/rules/typescript-node-security/detected-jwt-token"
tag: "detected-jwt-token"
text: "Detects hardcoded JWT tokens within the codebase"
- - link: "/continuous_integration/static_analysis/rules/typescript-node-security/hardcoded-hmac-key"
+ - link: "/static_analysis/rules/typescript-node-security/hardcoded-hmac-key"
tag: "hardcoded-hmac-key"
text: "Detects hardcoded HMAC keys"
- - link: "/continuous_integration/static_analysis/rules/typescript-node-security/insecure-hash"
+ - link: "/static_analysis/rules/typescript-node-security/insecure-hash"
tag: "insecure-hash"
text: "Do not use weak hash functions"
- - link: "/continuous_integration/static_analysis/rules/typescript-node-security/insecure-jwt-secret-usage"
+ - link: "/static_analysis/rules/typescript-node-security/insecure-jwt-secret-usage"
tag: "insecure-jwt-secret-usage"
text: "Insecure Usage of a Static Secret in JWT Signing"
- - link: "/continuous_integration/static_analysis/rules/typescript-node-security/jwt-hardcoded-secret"
+ - link: "/static_analysis/rules/typescript-node-security/jwt-hardcoded-secret"
tag: "jwt-hardcoded-secret"
text: "Do not use hardcoded secret with a JWT"
- - link: "/continuous_integration/static_analysis/rules/typescript-node-security/jwt-sensitive-data"
+ - link: "/static_analysis/rules/typescript-node-security/jwt-sensitive-data"
tag: "jwt-sensitive-data"
text: "Do not put sensitive data in objects"
- - link: "/continuous_integration/static_analysis/rules/typescript-node-security/jwt-weak-encryption"
+ - link: "/static_analysis/rules/typescript-node-security/jwt-weak-encryption"
tag: "jwt-weak-encryption"
text: "Use default encryption from the JWT library"
- - link: "/continuous_integration/static_analysis/rules/typescript-node-security/log-sensitive-data"
+ - link: "/static_analysis/rules/typescript-node-security/log-sensitive-data"
tag: "log-sensitive-data"
text: "Avoid logging sensitive data"
- - link: "/continuous_integration/static_analysis/rules/typescript-node-security/oauth2-hardcoded-secret"
+ - link: "/static_analysis/rules/typescript-node-security/oauth2-hardcoded-secret"
tag: "oauth2-hardcoded-secret"
text: "Do not use hardcoded secret for OAuth2 providers"
- - link: "/continuous_integration/static_analysis/rules/typescript-node-security/sql-injection"
+ - link: "/static_analysis/rules/typescript-node-security/sql-injection"
tag: "sql-injection"
text: "Avoid SQL injection"
further_reading:
- - link: "/continuous_integration/static_analysis/"
+ - link: "/static_analysis/"
tag: "Documentation"
text: "Learn about Datadog Static Analysis"
---
@@ -1518,4 +1520,4 @@ Rules to identify potential security hotspots in Node. This may include false po
{{< partial name="whats-next/whats-next.html" >}}
-[1]: /continuous_integration/static_analysis
+[1]: /static_analysis
diff --git a/content/en/continuous_integration/tests/_index.md b/content/en/tests/_index.md
similarity index 83%
rename from content/en/continuous_integration/tests/_index.md
rename to content/en/tests/_index.md
index cc31070efef57..c1cab620eaed0 100644
--- a/content/en/continuous_integration/tests/_index.md
+++ b/content/en/tests/_index.md
@@ -5,6 +5,7 @@ aliases:
- /continuous_integration/explore_tests/
- /continuous_integration/guides/test_configurations/
- /continuous_integration/integrate_tests/
+ - /continuous_integration/tests/
further_reading:
- link: "/monitors/types/ci/"
tag: "Documentation"
@@ -38,17 +39,17 @@ cascade:
## Setup
{{< whatsnext desc="Choose a language to set up Test Visibility in Datadog:" >}}
- {{< nextlink href="continuous_integration/tests/setup/dotnet" >}}.NET{{< /nextlink >}}
- {{< nextlink href="continuous_integration/tests/setup/java" >}}Java{{< /nextlink >}}
- {{< nextlink href="continuous_integration/tests/setup/javascript" >}}JavaScript{{< /nextlink >}}
- {{< nextlink href="continuous_integration/tests/setup/python" >}}Python{{< /nextlink >}}
- {{< nextlink href="continuous_integration/tests/setup/ruby" >}}Ruby{{< /nextlink >}}
- {{< nextlink href="continuous_integration/tests/setup/swift" >}}Swift{{< /nextlink >}}
- {{< nextlink href="continuous_integration/tests/junit_upload" >}}Uploading JUnit test report files to Datadog{{< /nextlink >}}
- {{< nextlink href="continuous_integration/tests/containers" >}}Tests running in containers{{< /nextlink >}}
+ {{< nextlink href="tests/setup/dotnet" >}}.NET{{< /nextlink >}}
+ {{< nextlink href="tests/setup/java" >}}Java{{< /nextlink >}}
+ {{< nextlink href="tests/setup/javascript" >}}JavaScript{{< /nextlink >}}
+ {{< nextlink href="tests/setup/python" >}}Python{{< /nextlink >}}
+ {{< nextlink href="tests/setup/ruby" >}}Ruby{{< /nextlink >}}
+ {{< nextlink href="tests/setup/swift" >}}Swift{{< /nextlink >}}
+ {{< nextlink href="tests/setup/junit_xml" >}}Uploading JUnit test report files to Datadog{{< /nextlink >}}
+ {{< nextlink href="tests/containers" >}}Tests running in containers{{< /nextlink >}}
{{< /whatsnext >}}
-In addition to tests, CI Visibility provides visibility over the whole testing phase of your project (except for Ruby).
+In addition to tests, Test Visibility provides visibility over the whole testing phase of your project (except for Ruby).
### Supported features
@@ -73,13 +74,13 @@ In addition to tests, CI Visibility provides visibility over the whole testing p
Tests evaluate the behavior of code for a set of given conditions. Some of those conditions are related to the environment where the tests are run, such as the operating system or the runtime used. The same code executed under different sets of conditions can behave differently, so developers usually configure their tests to run in different sets of conditions and validate that the behavior is the expected for all of them. This specific set of conditions is called a *configuration*.
-In CI Visibility, a test with multiple configurations is treated as multiple tests with a separate test for each configuration. In the case where one of the configurations fails but the others pass, only that specific test and configuration combination is marked as failed.
+In Test Visibility, a test with multiple configurations is treated as multiple tests with a separate test for each configuration. In the case where one of the configurations fails but the others pass, only that specific test and configuration combination is marked as failed.
For example, suppose you're testing a single commit and you have a Python test that runs against three different Python versions. If the test fails for one of those versions, that specific test is marked as failed, while the other versions are marked as passed. If you retry the tests against the same commit and now the test for all three Python versions pass, the test with the version that previously failed is now marked as both passed and flaky, while the other two versions remain passed, with no flakiness detected.
### Test configuration attributes
-When you run your tests with CI Visibility, the library detects and reports information about the environment where tests are run as test tags. For example, the operating system name, such as `Windows` or `Linux`, and the architecture of the platform, such as `arm64` or `x86_64`, are added as tags on each test. These values are shown in the commit and on branch overview pages when a test fails or is flaky for a specific configuration but not others.
+When you run your tests with Test Visibility, the library detects and reports information about the environment where tests are run as test tags. For example, the operating system name, such as `Windows` or `Linux`, and the architecture of the platform, such as `arm64` or `x86_64`, are added as tags on each test. These values are shown in the commit and on branch overview pages when a test fails or is flaky for a specific configuration but not others.
The following tags are automatically collected to identify test configurations, and some may only apply to specific platforms:
@@ -101,7 +102,7 @@ The following tags are automatically collected to identify test configurations,
## Custom configurations
-There are some configurations that cannot be directly identified and reported automatically because they can depend on environment variables, test run arguments, or other approaches that developers use. For those cases, you must provide the configuration details to the library so CI Visibility can properly identify them.
+There are some configurations that cannot be directly identified and reported automatically because they can depend on environment variables, test run arguments, or other approaches that developers use. For those cases, you must provide the configuration details to the library so Test Visibility can properly identify them.
Define these tags as part of the `DD_TAGS` environment variable using the `test.configuration` prefix.
@@ -122,10 +123,10 @@ In order to filter using these configurations tags, [you must create facets for
### Integrations
{{< whatsnext desc="Learn about the following integrations with Test Visibility:" >}}
-{{< nextlink href="/continuous_integration/tests/developer_workflows" >}}Enhancing Developer Workflows with Datadog{{< /nextlink >}}
-{{< nextlink href="/continuous_integration/tests/code_coverage" >}}Code Coverage{{< /nextlink >}}
-{{< nextlink href="/continuous_integration/tests/browser_tests" >}}Instrument Cypress Browser Tests with Browser RUM{{< /nextlink >}}
-{{< nextlink href="/continuous_integration/tests/swift_tests" >}}Instrument Swift Tests with Browser RUM{{< /nextlink >}}
+{{< nextlink href="/tests/developer_workflows/" >}}Enhancing Developer Workflows with Datadog{{< /nextlink >}}
+{{< nextlink href="/tests/code_coverage" >}}Code Coverage{{< /nextlink >}}
+{{< nextlink href="/tests/browser_tests" >}}Instrument Cypress Browser Tests with Browser RUM{{< /nextlink >}}
+{{< nextlink href="/tests/swift_tests" >}}Instrument Swift Tests with Browser RUM{{< /nextlink >}}
{{< /whatsnext >}}
If [Intelligent Test Runner][13] is enabled for .NET, JavaScript, or Swift, [code coverage information][12], including file names and line numbers covered by each test, are collected from your projects.
@@ -146,5 +147,5 @@ When you evaluate failed or flaky tests, or the performance of a CI test on the
[9]: https://app.datadoghq.com/notebook/list
[10]: https://app.datadoghq.com/ci/test-runs
[11]: /monitors/types/ci/
-[12]: /continuous_integration/guides/code_coverage/
-[13]: /continuous_integration/intelligent_test_runner/
+[12]: /tests/code_coverage/
+[13]: /intelligent_test_runner/
diff --git a/content/en/continuous_integration/tests/browser_tests.md b/content/en/tests/browser_tests.md
similarity index 95%
rename from content/en/continuous_integration/tests/browser_tests.md
rename to content/en/tests/browser_tests.md
index 3839ad51ad99f..8147e44fd2e60 100644
--- a/content/en/continuous_integration/tests/browser_tests.md
+++ b/content/en/tests/browser_tests.md
@@ -5,6 +5,7 @@ description: Learn how to use CI Visibility and RUM to connect your test results
aliases:
- /continuous_integration/guides/rum_integration
- /continuous_integration/integrate_tests/browser_tests
+- /continuous_integration/tests/browser_tests
further_reading:
- link: "/continuous_integration/tests"
tag: "Documentation"
@@ -52,6 +53,6 @@ The RUM session has all the data that [RUM normally collects][3] so you can debu
{{< partial name="whats-next/whats-next.html" >}}
-[1]: /continuous_integration/tests/javascript/?tab=cypress#instrument-your-tests
+[1]: /tests/setup/javascript/?tab=cypress#instrument-your-tests
[2]: /real_user_monitoring/browser/
[3]: /real_user_monitoring/browser/data_collected/
diff --git a/content/en/continuous_integration/tests/code_coverage.md b/content/en/tests/code_coverage.md
similarity index 99%
rename from content/en/continuous_integration/tests/code_coverage.md
rename to content/en/tests/code_coverage.md
index 112ba92241441..79215fd47b7d4 100644
--- a/content/en/continuous_integration/tests/code_coverage.md
+++ b/content/en/tests/code_coverage.md
@@ -5,8 +5,9 @@ description: Learn how to report and use code coverage in Datadog.
aliases:
- /continuous_integration/guides/code_coverage/
- /continuous_integration/integrate_tests/code_coverage/
+- /continuous_integration/tests/code_coverage/
further_reading:
-- link: "/continuous_integration/tests"
+- link: "/tests"
tag: "Documentation"
text: "Learn about Test Visibility"
- link: "/monitors/types/ci"
@@ -234,7 +235,7 @@ Get alerted whenever code coverage for your service drops below a certain thresh
{{< partial name="whats-next/whats-next.html" >}}
-[1]: /continuous_integration/tests/
+[1]: /tests/
[2]: /dashboards
[3]: /notebooks
[4]: /monitors
diff --git a/content/en/continuous_integration/tests/containers.md b/content/en/tests/containers.md
similarity index 95%
rename from content/en/continuous_integration/tests/containers.md
rename to content/en/tests/containers.md
index b4ad6c074d746..bcdeee06867e5 100644
--- a/content/en/continuous_integration/tests/containers.md
+++ b/content/en/tests/containers.md
@@ -3,10 +3,15 @@ title: Tests in Containers
kind: documentation
aliases:
- /continuous_integration/setup_tests/containers
+ - /continuous_integration/tests/containers
+further_reading:
+- link: "/tests"
+ tag: "Documentation"
+ text: "Learn about Test Visibility"
---
{{< site-region region="gov" >}}
-CI Visibility is not available in the selected site ({{< region-param key="dd_site_name" >}}) at this time.
+Test Visibility is not available in the selected site ({{< region-param key="dd_site_name" >}}) at this time.
{{< /site-region >}}
## Overview
@@ -295,6 +300,10 @@ Additionally, you need to pass in the environment variables required to configur
{{% /tab %}}
{{< /tabs >}}
+## Further reading
+
+{{< partial name="whats-next/whats-next.html" >}}
+
[1]: https://docs.docker.com/engine/reference/run/
[2]: https://docs.docker.com/compose/reference/
-[3]: /continuous_integration/tests/
+[3]: /tests/
diff --git a/content/en/continuous_integration/tests/developer_workflows.md b/content/en/tests/developer_workflows.md
similarity index 94%
rename from content/en/continuous_integration/tests/developer_workflows.md
rename to content/en/tests/developer_workflows.md
index 43e58bdd31f38..60502c8150f2c 100644
--- a/content/en/continuous_integration/tests/developer_workflows.md
+++ b/content/en/tests/developer_workflows.md
@@ -6,6 +6,7 @@ aliases:
- /continuous_integration/guides/developer_workflows
- /continuous_integration/guides/pull_request_comments
- /continuous_integration/integrate_tests/developer_workflows
+- /continuous_integration/tests/developer_workflows
further_reading:
- link: "https://www.datadoghq.com/blog/datadog-github-actions-ci-visibility/"
tag: "Blog"
@@ -18,10 +19,10 @@ further_reading:
## Overview
{{< site-region region="gov" >}}
-CI Visibility is not available in the selected site ({{< region-param key="dd_site_name" >}}) at this time.
+Test Visibility is not available in the selected site ({{< region-param key="dd_site_name" >}}) at this time.
{{< /site-region >}}
-[CI Test Visibility][5] integrates with other developer-oriented Datadog products as well as external partners such as GitHub to streamline developer workflows with features including being able to:
+[Test Visibility][5] integrates with other developer-oriented Datadog products as well as external partners such as GitHub to streamline developer workflows with features including being able to:
- [Create and open GitHub issues](#create-and-open-github-issues)
- [Open tests in GitHub and your IDE](#open-tests-in-github-and-your-ide)
diff --git a/content/en/tests/guides/_index.md b/content/en/tests/guides/_index.md
new file mode 100644
index 0000000000000..16726d79bddc5
--- /dev/null
+++ b/content/en/tests/guides/_index.md
@@ -0,0 +1,16 @@
+---
+title: Test Visibility Guides
+kind: guide
+private: true
+disable_toc: true
+cascade:
+ algolia:
+ rank: 20
+ category: Guide
+ subcategory: Test Visibility Guides
+---
+
+{{< whatsnext desc="Test Visibility Guides:" >}}
+ {{< nextlink href="/tests/guides/flaky_test_management" >}}Flaky Test Management{{< /nextlink >}}
+ {{< nextlink href="/tests/guides/add_custom_metrics" >}}Add Custom Metrics to Your Tests{{< /nextlink >}}
+{{< /whatsnext >}}
diff --git a/content/en/continuous_integration/guides/add_custom_metrics.md b/content/en/tests/guides/add_custom_metrics.md
similarity index 98%
rename from content/en/continuous_integration/guides/add_custom_metrics.md
rename to content/en/tests/guides/add_custom_metrics.md
index 49af329c3dd4f..7766bd1e28347 100644
--- a/content/en/continuous_integration/guides/add_custom_metrics.md
+++ b/content/en/tests/guides/add_custom_metrics.md
@@ -2,6 +2,8 @@
title: Add Custom Metrics To Your Tests
kind: guide
description: Learn how to use custom metrics (measures) in your tests.
+aliases:
+- /continuous_integration/guides/add_custom_metrics/
further_reading:
- link: "/continuous_integration/tests"
tag: "Documentation"
diff --git a/content/en/continuous_integration/guides/flaky_test_management.md b/content/en/tests/guides/flaky_test_management.md
similarity index 98%
rename from content/en/continuous_integration/guides/flaky_test_management.md
rename to content/en/tests/guides/flaky_test_management.md
index d4e7bb9514718..9af73ecc4c4a2 100644
--- a/content/en/continuous_integration/guides/flaky_test_management.md
+++ b/content/en/tests/guides/flaky_test_management.md
@@ -3,6 +3,7 @@ title: Flaky Test Management
kind: guide
aliases:
- /continuous_integration/guides/find_flaky_tests/
+- /continuous_integration/guides/flaky_test_management/
further_reading:
- link: "/continuous_integration/tests/"
tag: "Documentation"
diff --git a/content/en/tests/search/_index.md b/content/en/tests/search/_index.md
new file mode 100644
index 0000000000000..0714e8fba887e
--- /dev/null
+++ b/content/en/tests/search/_index.md
@@ -0,0 +1,93 @@
+---
+title: Search and Manage CI Tests
+description: Learn how to search for your CI tests.
+algolia:
+ rank: 70
+ tags: ['flaky test', 'flaky tests', 'test regression', 'test regressions', 'test service', 'test services']
+further_reading:
+- link: "/continuous_integration/explorer"
+ tag: "Documentation"
+ text: "Search and filter test runs"
+- link: "/continuous_integration/guides/flaky_test_management"
+ tag: "Documentation"
+ text: "Learn how to manage flaky tests"
+---
+
+{{< site-region region="gov" >}}
+CI Visibility is not available in the selected site ({{< region-param key="dd_site_name" >}}) at this time.
+{{< /site-region >}}
+
+## Overview
+
+The [Tests page][1] is useful for developers who want to keep an eye on their test results.
+
+{{< img src="/continuous_integration/tests.png" text="CI Tests page" style="width:100%" >}}
+
+You can access low-level and immediate insights:
+
+- See what tests are failing and why.
+- See your last commit's test results.
+- View the wall time of your tests in your feature branch and compare it to the default branch, to identify if you're about to introduce a performance regression.
+- Find out if your commit introduces a new [flaky test][5] that wasn't flaky before, indicating that your code change is what's making it flaky. This gives you the opportunity to fix the problem before proceeding rather than contributing to the number of flaky tests in your CI.
+
+You can also access high-level accumulation and trends:
+
+- See the effects that changed code, added tests, and increased complexity have on your test suite performance over time.
+- See which tests have become slower over time and identify the commit that introduced the regression.
+- Take advantage of Datadog's automatic test flakiness detection and tracking, which shows you which tests are becoming more or less unreliable over time.
+
+## Search for tests
+
+To see your tests, navigate to [**CI** > **Tests**][1] and select between the [**Branches**](#branches-view) or [**Default Branches** view](#default-branches-view).
+
+### Branches view
+
+The [Branches][2] view of the Tests page lists all branches from all [test services][3] that have reported test results. This tab is useful for individual developers to quickly see the status of tests that run on their code branches and troubleshoot test failures.
+
+In this page, you can filter the list by name, test service, or commit SHA, or to show only your branches (branches that contain at least one commit authored by you), enable the **My branches** toggle and add the email addresses you use in your Git configuration.
+
+#### Test results
+
+For each branch, you can see the test service, the number of failed, passed, and skipped tests, test regressions, wall time, the percentage of change compared to the default branch, when the commit was last updated, and the avatar of the author of the commit.
+
+Click on a branch to explore the test details page, which includes information about the branch's latest commits, flaky tests, test performance, common error types, and all test runs.
+
+{{< img src="continuous_integration/test_details.png" alt="Test Details page for a single branch" style="width:100%;">}}
+
+#### Test suite performance
+
+There is also information about the [wall time][4] of the most recent test suite run, and a comparison to the average wall time of the default branch. The comparison of your branch's wall time to the default branch's wall time can help you determine if your commit is introducing performance [regressions][6] to your test suite.
+
+Hovering over the commit author avatar shows detailed information about the latest commit.
+
+#### Test regressions
+
+[Test regressions][6] are evaluated per commit in an effort to tie performance regressions to specific code changes.
+
+#### Investigate for more details
+
+Click on the row to see test suite run details such as test results for the last commit on this branch (or you can switch branches), failing tests and the most common errors, slow tests, flaky tests, and a complete list of test runs over the time frame selected. You can filter this list of test runs by facet to get to the information you want to see most.
+
+Click into one of the test runs to see the test trace as a flame graph or a span list. The _Runs (n)_ list on the left lets you quickly access traces for each retry of the test for the same commit.
+
+#### Explore connections to services, resources, logs, and network events
+
+Click the CI provider link to examine the Resource, Service, or Analytics page for the test. You can also find complete tags information and links to related log events and network monitoring events.
+
+### Default Branches view
+
+The [Default Branches][7] view of the Tests page shows aggregated health metrics for the _default_ branch of each test service. This view is useful for teams to understand the overall health of the service over time.
+
+The Default Branches view shows similar information to the Branches view, but applied to the default branch. It compares the current wall time with the average default branch wall time to give you an indication of how your test suite performance is trending over time.
+
+## Further reading
+
+{{< partial name="whats-next/whats-next.html" >}}
+
+[1]: https://app.datadoghq.com/ci/test-services
+[2]: https://app.datadoghq.com/ci/test-services?view=branches
+[3]: /glossary/#test-service
+[4]: /glossary/#wall-time
+[5]: /glossary/#flaky-test
+[6]: /glossary/#test-regression
+[7]: https://app.datadoghq.com/ci/test-services?view=default-branches
\ No newline at end of file
diff --git a/content/en/continuous_integration/tests/setup/_index.md b/content/en/tests/setup/_index.md
similarity index 85%
rename from content/en/continuous_integration/tests/setup/_index.md
rename to content/en/tests/setup/_index.md
index 68e70780a043c..8277d84b53b01 100644
--- a/content/en/continuous_integration/tests/setup/_index.md
+++ b/content/en/tests/setup/_index.md
@@ -2,6 +2,8 @@
title: Configure Test Visibility
kind: documentation
type: multi-code-lang
+aliases:
+- continuous_integration/tests/setup/
---
For information about configuration options for [Test Visibility][1], choose your language:
diff --git a/content/en/continuous_integration/tests/setup/dotnet.md b/content/en/tests/setup/dotnet.md
similarity index 99%
rename from content/en/continuous_integration/tests/setup/dotnet.md
rename to content/en/tests/setup/dotnet.md
index a436c17eca070..6e0e0be6bcaa2 100644
--- a/content/en/continuous_integration/tests/setup/dotnet.md
+++ b/content/en/tests/setup/dotnet.md
@@ -7,6 +7,7 @@ code_lang_weight: 0
aliases:
- /continuous_integration/setup_tests/dotnet
- /continuous_integration/tests/dotnet
+ - continuous_integration/tests/setup/dotnet
further_reading:
- link: "/continuous_integration/tests/containers/"
tag: "Documentation"
diff --git a/content/en/continuous_integration/tests/setup/java.md b/content/en/tests/setup/java.md
similarity index 99%
rename from content/en/continuous_integration/tests/setup/java.md
rename to content/en/tests/setup/java.md
index 5e681773bc9ea..a19206c03cb53 100644
--- a/content/en/continuous_integration/tests/setup/java.md
+++ b/content/en/tests/setup/java.md
@@ -7,6 +7,7 @@ code_lang_weight: 10
aliases:
- /continuous_integration/setup_tests/java
- /continuous_integration/tests/java
+ - continuous_integration/tests/setup/java
further_reading:
- link: "/continuous_integration/tests/containers/"
tag: "Documentation"
diff --git a/content/en/continuous_integration/tests/setup/javascript.md b/content/en/tests/setup/javascript.md
similarity index 99%
rename from content/en/continuous_integration/tests/setup/javascript.md
rename to content/en/tests/setup/javascript.md
index 9a1908e583bf7..4d9dd0b31ed08 100644
--- a/content/en/continuous_integration/tests/setup/javascript.md
+++ b/content/en/tests/setup/javascript.md
@@ -7,6 +7,7 @@ code_lang_weight: 20
aliases:
- /continuous_integration/setup_tests/javascript
- /continuous_integration/tests/javascript
+ - continuous_integration/tests/setup/javascript
further_reading:
- link: "/continuous_integration/tests/containers/"
tag: "Documentation"
diff --git a/content/en/continuous_integration/tests/setup/junit_xml.md b/content/en/tests/setup/junit_xml.md
similarity index 99%
rename from content/en/continuous_integration/tests/setup/junit_xml.md
rename to content/en/tests/setup/junit_xml.md
index 3260ae8082bfc..ca4521272e8c4 100644
--- a/content/en/continuous_integration/tests/setup/junit_xml.md
+++ b/content/en/tests/setup/junit_xml.md
@@ -7,6 +7,7 @@ code_lang_weight: 60
aliases:
- /continuous_integration/setup_tests/junit_upload
- /continuous_integration/tests/junit_upload
+ - continuous_integration/tests/setup/junit_xml
further_reading:
- link: "/continuous_integration/tests"
tag: "Documentation"
diff --git a/content/en/continuous_integration/tests/setup/python.md b/content/en/tests/setup/python.md
similarity index 99%
rename from content/en/continuous_integration/tests/setup/python.md
rename to content/en/tests/setup/python.md
index 52e95596e4789..b74d4fd2f6038 100644
--- a/content/en/continuous_integration/tests/setup/python.md
+++ b/content/en/tests/setup/python.md
@@ -7,6 +7,7 @@ code_lang_weight: 30
aliases:
- /continuous_integration/setup_tests/python
- /continuous_integration/tests/python
+ - continuous_integration/tests/setup/python
further_reading:
- link: "/continuous_integration/tests/containers/"
tag: "Documentation"
diff --git a/content/en/continuous_integration/tests/setup/ruby.md b/content/en/tests/setup/ruby.md
similarity index 99%
rename from content/en/continuous_integration/tests/setup/ruby.md
rename to content/en/tests/setup/ruby.md
index 67efd96ef7da2..8fe5f6dc18f62 100644
--- a/content/en/continuous_integration/tests/setup/ruby.md
+++ b/content/en/tests/setup/ruby.md
@@ -7,6 +7,7 @@ code_lang_weight: 40
aliases:
- /continuous_integration/setup_tests/ruby
- /continuous_integration/tests/ruby
+ - continuous_integration/tests/setup/ruby
further_reading:
- link: "/continuous_integration/tests/containers/"
tag: "Documentation"
diff --git a/content/en/continuous_integration/tests/setup/swift.md b/content/en/tests/setup/swift.md
similarity index 99%
rename from content/en/continuous_integration/tests/setup/swift.md
rename to content/en/tests/setup/swift.md
index 26cb10e92ff54..32cdca6920c29 100644
--- a/content/en/continuous_integration/tests/setup/swift.md
+++ b/content/en/tests/setup/swift.md
@@ -7,6 +7,7 @@ code_lang_weight: 50
aliases:
- /continuous_integration/setup_tests/swift
- /continuous_integration/tests/swift
+ - continuous_integration/tests/setup/swift
further_reading:
- link: "/continuous_integration/tests"
tag: "Documentation"
diff --git a/content/en/continuous_integration/tests/swift_tests.md b/content/en/tests/swift_tests.md
similarity index 97%
rename from content/en/continuous_integration/tests/swift_tests.md
rename to content/en/tests/swift_tests.md
index 557719c591aca..8a8cfe5b386d5 100644
--- a/content/en/continuous_integration/tests/swift_tests.md
+++ b/content/en/tests/swift_tests.md
@@ -5,6 +5,7 @@ description: Learn how to use CI Visibility and RUM to connect your Swift test r
aliases:
- /continuous_integration/guides/rum_swift_integration
- /continuous_integration/integrate_tests/swift_tests
+- continuous_integration/tests/swift_tests
further_reading:
- link: "/continuous_integration/tests"
tag: "Documentation"
diff --git a/content/en/tests/troubleshooting/_index.md b/content/en/tests/troubleshooting/_index.md
new file mode 100644
index 0000000000000..1141ded83ab5e
--- /dev/null
+++ b/content/en/tests/troubleshooting/_index.md
@@ -0,0 +1,175 @@
+---
+title: Test Visibility Troubleshooting
+kind: documentation
+further_reading:
+ - link: "/continuous_integration/tests"
+ tag: "Documentation"
+ text: "Learn how to monitor your CI tests"
+---
+
+{{< site-region region="gov" >}}
+CI Visibility is not available in the selected site ({{< region-param key="dd_site_name" >}}) at this time.
+{{< /site-region >}}
+
+## Overview
+
+This page provides information to help you troubleshot issues with Test Visibility. If you need additional help, contact [Datadog Support][2].
+
+## Your tests are instrumented, but Datadog isn't showing any data
+
+1. Go to the [**Tests**][3] page for the language you're instrumenting and check that the testing framework you are using is supported in the **Compatibility** section.
+2. Check if you see any test results in the [**Test Runs**][4] section. If you do see results there, but not in the [**Tests**][5] section, Git information is missing. See [Data appears in Test Runs but not Tests](#data-appears-in-test-runs-but-not-tests) to troubleshoot it.
+3. If you are reporting the data through the Datadog Agent, make sure it is running on the host where tests are run (accessible at `localhost:8126`), or if accessible on another hostname or port, make sure you run your tests with the appropriate Agent hostname set in the `DD_AGENT_HOST` and the appropriate port in `DD_TRACE_AGENT_PORT` environment variables. You can activate [debug mode][6] in the tracer to check if it's able to connect to the Agent.
+4. If you still don't see any results, [contact Support][2] for troubleshooting help.
+
+## You are uploading JUnit test reports with `datadog-ci` but some or all tests are missing
+If you are uploading JUnit test report files with `datadog-ci` CLI and you do not see the tests, it is likely the tests are being discarded because the report is considered incorrect.
+
+The following aspects make a JUnit test report incorrect:
+* A timestamp of the reported tests that is older than **71 hours** before the moment the report is uploaded.
+* A testsuite without a name.
+
+## Data appears in test runs but not tests
+
+If you can see test results data in the **Test Runs** tab, but not the **Tests** tab, Git metadata (repository, commit, or branch) is probably missing. To confirm this is the case, open a test execution in the [**Test Runs**][4] section, and check that there is no `git.repository_url`, `git.commit.sha`, or `git.branch`. If these tags are not populated, nothing shows in the [**Tests**][5] section.
+
+1. Tracers first use the environment variables, if any, set by the CI provider to collect Git information. See [Running tests inside a container][7] for a list of environment variables that the tracer attempts to read for each supported CI provider. At a minimum, this populates the repository, commit hash, and branch information.
+2. Next, tracers fetch Git metadata using the local `.git` folder, if present, by executing `git` commands. This populates all Git metadata fields, including commit message, author, and committer information. Ensure the `.git` folder is present and the `git` binary is installed and in `$PATH`. This information is used to populate attributes not detected in the previous step.
+3. You can also provide Git information manually using environment variables, which override information detected by any of the previous steps.
+
+ The supported environment variables for providing Git information are:
+
+ `DD_GIT_REPOSITORY_URL` **(required)**
+ : URL of the repository where the code is stored. Both HTTP and SSH URLs are supported.
+ **Example**: `git@github.com:MyCompany/MyApp.git`, `https://github.com/MyCompany/MyApp.git`
+
+ `DD_GIT_COMMIT_SHA` **(required)**
+ : Full (40-character long SHA1) commit hash.
+ **Example**: `a18ebf361cc831f5535e58ec4fae04ffd98d8152`
+
+ `DD_GIT_BRANCH`
+ : Git branch being tested. Leave empty if providing tag information instead.
+ **Example**: `develop`
+
+ `DD_GIT_TAG`
+ : Git tag being tested (if applicable). Leave empty if providing branch information instead.
+ **Example**: `1.0.1`
+
+ `DD_GIT_COMMIT_MESSAGE`
+ : Commit message.
+ **Example**: `Set release number`
+
+ `DD_GIT_COMMIT_AUTHOR_NAME`
+ : Commit author name.
+ **Example**: `John Smith`
+
+ `DD_GIT_COMMIT_AUTHOR_EMAIL`
+ : Commit author email.
+ **Example**: `john@example.com`
+
+ `DD_GIT_COMMIT_AUTHOR_DATE`
+ : Commit author date in ISO 8601 format.
+ **Example**: `2021-03-12T16:00:28Z`
+
+ `DD_GIT_COMMIT_COMMITTER_NAME`
+ : Commit committer name.
+ **Example**: `Jane Smith`
+
+ `DD_GIT_COMMIT_COMMITTER_EMAIL`
+ : Commit committer email.
+ **Example**: `jane@example.com`
+
+ `DD_GIT_COMMIT_COMMITTER_DATE`
+ : Commit committer date in ISO 8601 format.
+ **Example**: `2021-03-12T16:00:28Z`
+
+4. If no CI provider environment variables are found, tests results are sent with no Git metadata.
+
+## The tests wall time is empty
+
+If you cannot see the tests wall time it is likely that the CI provider metadata is missing. To confirm this is the case, open a test execution in the [**Test Runs**][4] section, and check if the `ci.pipeline.id`, `ci.pipeline.name`, `ci.pipeline.number`, or `ci.job.url` tags are missing. If these tags are not populated, then nothing shows in the wall time column.
+
+1. Tracers use the environment variables set by the CI provider to collect this information. See [Running tests inside a container][7] for a list of environment variables that the tracer attempts to read for each supported CI provider. Make sure that the environment variables have the expected values set.
+2. Check that you are running your tests in a supported CI provider. For a list of supported CI providers, see [Running tests inside a container][7]. Only these CI providers can extract the information to enrich the test metadata with CI information.
+3. If you still don't see the wall time, contact [Datadog support][2] for help.
+
+## The tests wall time is not what is expected
+
+### How wall time is calculated
+The wall time is defined as the time difference between the start time of the first test and the end time of the last test for the given pipeline.
+
+This is done using the following algorithm:
+
+1. Compute a hash based on CI information to group the tests.
+ 1. If the tests include `ci.job.url`, use this tag to calculate the hash.
+ 2. If the tests don't include `ci.job.url`, use `ci.pipeline.id` + `ci.pipeline.name` + `ci.pipeline.number` to calculate the hash.
+2. The calculated wall time is associated to a given hash. **Note**: If there are multiple jobs that execute tests, the wall time is calculated for each job, and the maximum from all calculated wall times is shown.
+
+### Possible issues with wall time calculation
+If you're using a library for testing time-dependent code, like [timecop][8] for Ruby or [FreezeGun][9] for Python, it is possible that test timestamps are wrong, and therefore calculated wall times. If this is the case, make sure that modifications to time are rolled back before finishing your tests.
+
+## The test status numbers are not what is expected
+
+The test status numbers are calculated based on the unique tests that were collected. The uniqueness of a test is defined not only by its suite and name, but by its test parameters and test configurations as well.
+
+### The numbers are lower than expected
+
+If the numbers are lower than expected, it is likely that either the library or the tool you are using to collect test data cannot collect test parameters and/or some test configurations.
+
+1. If you are uploading JUnit test report files:
+ 1. If you are running the same tests in different environment configurations, [make sure you are setting those configuration tags during the upload][10].
+ 2. If you are running parameterized tests, it's very likely that the JUnit report does not have that information. [Try using a native library to report test data][3].
+2. If you still don't see the expected results, [contact Datadog support][2] for troubleshooting help.
+
+### The passed/failed/skipped numbers are different than expected
+
+If the same test is collected several times for the same commit but with different status, the aggregated result follows the algorithm in the table below:
+
+| **Test Status - First Try** | **Test Status - Retry #1** | **Result** |
+|-----------------------------|----------------------------|------------|
+| `Passed` | `Passed` | `Passed` |
+| `Passed` | `Failed` | `Passed` |
+| `Passed` | `Skipped` | `Passed` |
+| `Failed` | `Passed` | `Passed` |
+| `Failed` | `Failed` | `Failed` |
+| `Failed` | `Skipped` | `Failed` |
+| `Skipped` | `Passed` | `Passed` |
+| `Skipped` | `Failed` | `Failed` |
+| `Skipped` | `Skipped` | `Skipped` |
+
+## The default branch is not correct
+
+### How it impacts the product
+
+The default branch is used to power some features of the products, namely:
+
+- Default branches list on the Tests page: This list only displays default branches. Setting the wrong default branch can result in missing or incorrect data in the default branches list.
+
+- Wall time comparison for non-default branches: On the Tests page, in the Branches view, the **VS Default** column is calculated by comparing wall time for the current branch against wall time for the default branch.
+
+- New flaky tests: Tests that are not currently classified as flaky in the default branch. If the default branch is not properly set, this could lead to a wrong number of detected new flaky tests.
+
+- Pipelines list: The pipelines list only displays default branches. Setting the wrong default branch can result in missing or incorrect data in the pipelines list.
+
+### How to fix the default branch
+
+If you have admin access, you can update it from the [Repository Settings Page][11].
+
+
+
+## Further reading
+
+{{< partial name="whats-next/whats-next.html" >}}
+
+[1]: https://www.jenkins.io/doc/book/system-administration/viewing-logs/
+[2]: /help/
+[3]: /continuous_integration/tests/
+[4]: https://app.datadoghq.com/ci/test-runs
+[5]: https://app.datadoghq.com/ci/test-services
+[6]: /tracing/troubleshooting/tracer_debug_logs
+[7]: /continuous_integration/tests/containers/
+[8]: https://github.com/travisjeffery/timecop
+[9]: https://github.com/spulec/freezegun
+[10]: /continuous_integration/tests/junit_upload/?tabs=linux#collecting-environment-configuration-metadata
+[11]: https://app.datadoghq.com/ci/settings/repository
+[12]: /continuous_integration/intelligent_test_runner/
\ No newline at end of file
diff --git a/local/bin/py/build/configurations/pull_config.yaml b/local/bin/py/build/configurations/pull_config.yaml
index 006e138e8b4ad..51cba83ee0ad4 100644
--- a/local/bin/py/build/configurations/pull_config.yaml
+++ b/local/bin/py/build/configurations/pull_config.yaml
@@ -343,13 +343,15 @@
globs:
- 'README.md'
options:
- dest_path: '/continuous_integration/static_analysis/'
+ dest_path: '/static_analysis/'
file_name: 'circleci_orbs.md'
front_matters:
dependencies: ["https://github.com/DataDog/datadog-static-analyzer-circleci-orb/blob/main/README.md"]
title: Static Analysis and CircleCI Orbs
kind: documentation
description: Use Datadog and CircleCI to run Static Analysis jobs in a CI pipeline.
+ aliases:
+ - /continuous_integration/static_analysis/circleci_orbs
- repo_name: datadog-static-analyzer-github-action
contents:
@@ -358,13 +360,15 @@
globs:
- 'README.md'
options:
- dest_path: '/continuous_integration/static_analysis/'
+ dest_path: '/static_analysis/'
file_name: 'github_actions.md'
front_matters:
dependencies: ["https://github.com/DataDog/datadog-static-analyzer-github-action/blob/main/README.md"]
title: Static Analysis and GitHub Actions
kind: documentation
description: Use Datadog and GitHub to run Static Analysis jobs in a CI pipeline.
+ aliases:
+ - /continuous_integration/static_analysis/github_actions
- repo_name: datadog-static-analyzer-rule-docs
contents:
@@ -373,7 +377,7 @@
globs:
- rulesets/**/*.md
options:
- dest_dir: '/continuous_integration/static_analysis/rules/'
+ dest_dir: '/static_analysis/rules/'
path_to_remove: 'rulesets/'
front_matters:
disable_edit: true
diff --git a/local/bin/py/build/configurations/pull_config_preview.yaml b/local/bin/py/build/configurations/pull_config_preview.yaml
index 4e01a7f401c27..ade397a4fbe1f 100644
--- a/local/bin/py/build/configurations/pull_config_preview.yaml
+++ b/local/bin/py/build/configurations/pull_config_preview.yaml
@@ -344,13 +344,15 @@
globs:
- 'README.md'
options:
- dest_path: '/continuous_integration/static_analysis/'
+ dest_path: '/static_analysis/'
file_name: 'circleci_orbs.md'
front_matters:
dependencies: ["https://github.com/DataDog/datadog-static-analyzer-circleci-orb/blob/main/README.md"]
title: Static Analysis and CircleCI Orbs
kind: documentation
description: Use Datadog and CircleCI to run Static Analysis jobs in a CI pipeline.
+ aliases:
+ - /continuous_integration/static_analysis/circleci_orbs
- repo_name: datadog-static-analyzer-github-action
contents:
@@ -359,13 +361,15 @@
globs:
- 'README.md'
options:
- dest_path: '/continuous_integration/static_analysis/'
+ dest_path: '/static_analysis/'
file_name: 'github_actions.md'
front_matters:
dependencies: ["https://github.com/DataDog/datadog-static-analyzer-github-action/blob/main/README.md"]
title: Static Analysis and GitHub Actions
kind: documentation
description: Use Datadog and GitHub to run Static Analysis jobs in a CI pipeline.
+ aliases:
+ - /continuous_integration/static_analysis/github_actions
- repo_name: datadog-static-analyzer-rule-docs
contents:
@@ -374,7 +378,7 @@
globs:
- rulesets/**/*.md
options:
- dest_dir: '/continuous_integration/static_analysis/rules/'
+ dest_dir: '/static_analysis/rules/'
path_to_remove: 'rulesets/'
front_matters:
disable_edit: true