|
1 | | ---- |
| 1 | +--- |
2 | 2 | id: analytics-modules-test-intelligence-command-logs-analytics |
3 | 3 | title: Command Logs Analytics with Test Intelligence |
4 | 4 | sidebar_label: Command Errors |
@@ -50,7 +50,7 @@ TestMu AI Analytics help you intelligently analyze your test execution steps on |
50 | 50 | ### Prerequisites for using Command Logs Analytics |
51 | 51 | The following are the steps to use Command Logs Analytics: |
52 | 52 | 1. You should have a <BrandName /> account. If you don't have one, you can sign up <a href="https://accounts.lambdatest.com/register" onClick={CookieTrackingSignup}>here</a>. |
53 | | -2. You should have access to the `Test Intelligence` subscription plan. You can join the waitlist [here](https://www.lambdatest.com/test-intelligence). |
| 53 | +2. You should have access to the `Test Intelligence` subscription plan. You can join the waitlist [here](https://www.testmuai.com/test-intelligence). |
54 | 54 | 3. Go to `Analytics` from the left navigation menu and create a new Dashboard by clicking on the `Create New Dashboard` button. |
55 | 55 | 4. Select the `Create Custom Dashboard` option from the `Create New Dashboard` dropdown. |
56 | 56 | 5. Select the `Command Logs` option from the `Analytics Modules` section. |
@@ -85,7 +85,7 @@ The following are the steps to use Command Logs Analytics: |
85 | 85 |
|
86 | 86 | A line or bar chart is displayed with the x-axis representing the timestamp of the tests run and the y-axis representing the total number of unique errors in tests with command logs of respective response statuses. |
87 | 87 |
|
88 | | - <img loading="lazy" src="https://www.lambdatest.com/resources/images/errorAi.png" alt="cmd" width="768" height="373" className="doc_img"/> |
| 88 | + <img loading="lazy" src="https://www.testmuai.com/resources/images/errorAi.png" alt="cmd" width="768" height="373" className="doc_img"/> |
89 | 89 |
|
90 | 90 | **Use Cases** |
91 | 91 | 1. Tracking response status trends over time |
@@ -121,7 +121,7 @@ The following are the steps to use Command Logs Analytics: |
121 | 121 |
|
122 | 122 | A table displays unique error messages, occurrences dots, the percentage of occurrences, the timestamp of the last error message, and tests with the error message command logs. |
123 | 123 |
|
124 | | - <img loading="lazy" src="https://www.lambdatest.com/resources/images/commandaifold.webp" alt="cmd" width="768" height="373" className="doc_img"/> |
| 124 | + <img loading="lazy" src="https://www.testmuai.com/resources/images/commandaifold.webp" alt="cmd" width="768" height="373" className="doc_img"/> |
125 | 125 |
|
126 | 126 | **Use Cases** |
127 | 127 | 6. Identifying common error messages for prioritizing bug fixes |
|
0 commit comments