Audit Logs + Custom Status + Assertions Doc

docs/kane-ai-command-guide.md

@@ -133,14 +133,94 @@ You can add maximum of 300 seconds timeout for an operation.
 
 If your element is not visible in the viewport, you can use the `scroll until` command to go to that particular element if that is present currently in the DOM. This can be used in vertical scrollable pages & even on the scrollable sub-sections. 
 
-## Assertions and Queries
-### Assert Element Text
-- `assert if red button text is "subscribe"`
+## Assertions
+KaneAI supports a range of assertions to make test validations more seamless and effective. Here are the types of assertions currently supported:
 
-### Assert Element Presence
-- `assert if KaneAI is present on the "viewport"`
+### Driver Assertions
+Driver assertions rely on the web driver to validate browser url, page & window properties and dimensions. 
 
-### Query Information
+**Examples:**
+- Assert if the current browser URL is "https://example.com".
+- Validate if the client height and width match the expected values.
+
+### Text Assertions
+Text assertions validate the presence or absence of specific text on the screen.
+
+**Examples:**
+- Assert if the text "Welcome Back!" is visible.
+- Check if the error message "Invalid password" appears on failed login.
+
+### Visual Assertions
+Visual assertions ensure the visibility of images on the screen.
+
+**Examples:**
+- Assert if the company logo is displayed in the header.
+- Verify the visibility of a product image on the product page.
+
+### Relative Assertions
+Relative assertions check the visibility of one element in relation to another.
+
+**Examples:**
+- Assert if the login button is in same column as the username field.
+- Check if the submit button and cancel button are in the same row.
+
+### Mathematical Assertions
+Mathematical assertions verify numerical operations or calculations.
+
+**Examples:**
+- Verify if the sum of 3 and 4 equals 7.
+
+:::note
+ By default any assertion used has a failure condition set to fail test immediately if assertion fails. This change has been implemented since July, 20, 2025. Any tests which were authored or edited before this date, would have a failure condition set to warn, but continue by default. Existing tests would keep running as it is until you edit in KaneAI agent, post which the new failure conditions will get set. More details about failure conditions are available [here](https://www.lambdatest.com/support/docs/kaneai-failure-conditions)
+:::
+
+## Unsupported Assertions
+There are some assertions that KaneAI does not support at this moment. However the support for these kind of assertions is currently under development.
+Below are examples of unsupported assertions along with examples.
+
+### Element State Assertions (To be available soon)
+These assertions check for state of elements like being disabled or enabled.
+
+**Examples:**
+- Assert if the submit button is disabled.
+- Assert if text input field is enabled.
+- Assert if a dropdown is expanded.
+
+### Element Property Assertions (To be available soon)
+Property assertions involve checking styles or attributes of an element.
+
+**Examples:**
+- Assert if the font size of a header is "16px".
+- Assert if the padding of a button is "10px".
+
+### Spatial Assertions (To be available soon)
+Spatial assertions validate the position or arrangement of elements.
+
+**Examples:**
+- Assert that the 5th column of a table contains "Jordan.Mathews".
+
+### Logical Assertions (To be available soon)
+Logical assertions are used to combine multiple conditions.
+
+**Examples:**
+- Assert if the user is an admin **and** is logged in.
+- Assert if either username or email is filled.
+
+### Assertions for Actions Being Performed (To be available soon)
+These assertions aim to check the state after an action, which is not supported directly.
+
+**Examples:**
+- Assert if the page is scrolled to the bottom.
+- Assert if a tooltip appears after hovering over an info icon.
+  - Currently, you can break this into two steps: Hover on the info icon, then assert if the tooltip is visible.
+
+### Nested Assertions (To be available soon)
+Nested assertions involve multiple layers of validation within a single assertion.
+
+**Examples:**
+- Assert if both the login button is enabled and the welcome message is visible.
+
+## Query Information
 - `query the current url`
 - `query the time mentioned in the poster`
 

docs/system-and-custom-fields.md

@@ -43,29 +43,44 @@ slug: system-and-custom-fields/
 
 Explore the structured organization of your test projects through the use of Fields and Values, accessible via the Project's dashboard. Dive into System Fields for essential categorizations or enhance your project's flexibility with Custom Fields to improve your testing workflows.
 
-1. In the Project's dashboard, click on **Settings** in the top right hand side.
+To access the System & Custom Fields settings, click on **Settings** in the top right hand side in the Project's dashboard.
 
-<img loading="lazy" src={require('../assets/images/mobile-app-testing/project-dashboard.webp').default} alt="Real "  className="doc_img" width="1366" height="629"/>
+<img loading="lazy" src={require('../assets/images/mobile-app-testing/field-settings.png').default} alt="Real "  className="doc_img" width="1366" height="629"/>
 
-2. You will be able to view the **System Fields** and **Custom Fields**.
+You can manage your **System** and **Custom Fields** in this Fields page.
 
-- System Fields is a default feature provided by LambdaTest that includes standard fields like **Priority**, **Status**, and **Type**. These fields help organize and track your test cases. They can be seamlessly integrated into your test management process and customized by adding values. To do so, simply click on any field and select **Add Value**.
+### System Fields
+Are default fields present in the Test Manager. These fields help organize and track your test cases, test runs or instances. They can be seamlessly integrated into your test management process and customized by adding values. Test Cases & Test Runs have their separate System Fields. 
 
-<img loading="lazy" src={require('../assets/images/mobile-app-testing/system-fields.webp').default} alt="Real "  className="doc_img" width="1366" height="629"/>
+- Test Cases have these pre defined fields: **Priority**, **Status**, and **Type**. 
+- Test Runs can have only one System Field that is the `Status`. 
 
-- Custom Fields allow you to store additional information beyond what System Fields offer. To create a new field, enter the required details and choose the appropriate data type from the **Type** function. Available types include String, Textarea, Number, Dropdown (Single Select), Dropdown (Multi Select), Boolean (Checkbox), Date, User, and URL.
+To manage these fields, navigate to the System Fields tab, where you'll see dedicated sections for both Test Case and Test Runs fields.
+
+<img loading="lazy" src={require('../assets/images/mobile-app-testing/system-fields.png').default} alt="Real "  className="doc_img" width="1366" height="629"/>
+
+These System Fields can have Custom Values which can be added by simply selecting any field and clicking on **Add Value**.
+
+<img loading="lazy" src={require('../assets/images/mobile-app-testing/edit-system-fields.png').default} alt="Real "  className="doc_img" width="1366" height="629"/>
+
+:::tip
+ Every new Status value of Test Runs will have a unique random color defined to it on creation. 
+:::
+
+### Custom Fields 
+Allow you to store additional information beyond what System Fields offer. To create a new field, enter the required details and choose the appropriate data type from the **Type** function. Available types include String, Textarea, Number, Dropdown (Single Select), Dropdown (Multi Select), Boolean (Checkbox), Date, User, and URL.
 
 <img loading="lazy" src={require('../assets/images/mobile-app-testing/create-new-fields.webp').default} alt="Real "  className="doc_img" width="1366" height="629"/>
 
-- For Dropdown types (Single Select and Multi Select), you also have the option to add values.
+For Dropdown types (Single Select and Multi Select), you also have the option to add values.
 
 <img loading="lazy" src={require('../assets/images/mobile-app-testing/dropdown-types.webp').default} alt="Real "  className="doc_img" width="1366" height="629"/>
 
-- Enter the name, placeholder, mark the field, apply it to all future projects if required and click create.
+Enter the name, placeholder, mark the field, apply it to all future projects if required and click create.
 
 <img loading="lazy" src={require('../assets/images/mobile-app-testing/custom-fields.webp').default} alt="Real "  className="doc_img" width="1366" height="629"/>
 
-3. You can also link a single or multiple projects of your choice to the custom fields and click on **Save changes**.
+You can also link a single or multiple projects of your choice to the custom fields and click on **Save changes**.
 
 <img loading="lazy" src={require('../assets/images/mobile-app-testing/link-projects.webp').default} alt="Real "  className="doc_img" width="1366" height="629"/>