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/kane-ai-command-guide.md
+82-6Lines changed: 82 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -133,14 +133,90 @@ You can add maximum of 300 seconds timeout for an operation.
133
133
134
134
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.
135
135
136
-
## Assertions and Queries
137
-
### Assert Element Text
138
-
-`assert if red button text is "subscribe"`
136
+
## Assertions
137
+
KaneAI supports a range of assertions to make test validations more seamless and effective. Here are the types of assertions currently supported:
139
138
140
-
### Assert Element Presence
141
-
-`assert if KaneAI is present on the "viewport"`
139
+
### Driver Assertions
140
+
Driver assertions rely on the web driver to validate browser url, page & window properties and dimensions.
142
141
143
-
### Query Information
142
+
**Examples:**
143
+
- Assert if the current browser URL is "https://example.com".
144
+
- Validate if the client height and width match the expected values.
145
+
146
+
### Text Assertions
147
+
Text assertions validate the presence or absence of specific text on the screen.
148
+
149
+
**Examples:**
150
+
- Assert if the text "Welcome Back!" is visible.
151
+
- Check if the error message "Invalid password" appears on failed login.
152
+
153
+
### Visual Assertions
154
+
Visual assertions ensure the visibility of images on the screen.
155
+
156
+
**Examples:**
157
+
- Assert if the company logo is displayed in the header.
158
+
- Verify the visibility of a product image on the product page.
159
+
160
+
### Relative Assertions
161
+
Relative assertions check the visibility of one element in relation to another.
162
+
163
+
**Examples:**
164
+
- Assert if the login button is in same column as the username field.
165
+
- Check if the submit button and cancel button are in the same row.
166
+
167
+
### Mathematical Assertions
168
+
Mathematical assertions verify numerical operations or calculations.
169
+
170
+
**Examples:**
171
+
- Verify if the sum of 3 and 4 equals 7.
172
+
173
+
## Unsupported Assertions
174
+
There are some assertions that KaneAI does not support at this moment. However the support for these kind of assertions is currently under development.
175
+
Below are examples of unsupported assertions along with examples.
176
+
177
+
### Element State Assertions (To be available soon)
178
+
These assertions check for state of elements like being disabled or enabled.
179
+
180
+
**Examples:**
181
+
- Assert if the submit button is disabled.
182
+
- Assert if text input field is enabled.
183
+
- Assert if a dropdown is expanded.
184
+
185
+
### Element Property Assertions (To be available soon)
186
+
Property assertions involve checking styles or attributes of an element.
187
+
188
+
**Examples:**
189
+
- Assert if the font size of a header is "16px".
190
+
- Assert if the padding of a button is "10px".
191
+
192
+
### Spatial Assertions (To be available soon)
193
+
Spatial assertions validate the position or arrangement of elements.
194
+
195
+
**Examples:**
196
+
- Assert that the 5th column of a table contains "Jordan.Mathews".
197
+
198
+
### Logical Assertions (To be available soon)
199
+
Logical assertions are used to combine multiple conditions.
200
+
201
+
**Examples:**
202
+
- Assert if the user is an admin **and** is logged in.
203
+
- Assert if either username or email is filled.
204
+
205
+
### Assertions for Actions Being Performed (To be available soon)
206
+
These assertions aim to check the state after an action, which is not supported directly.
207
+
208
+
**Examples:**
209
+
- Assert if the page is scrolled to the bottom.
210
+
- Assert if a tooltip appears after hovering over an info icon.
211
+
- Currently, you can break this into two steps: Hover on the info icon, then assert if the tooltip is visible.
212
+
213
+
### Nested Assertions (To be available soon)
214
+
Nested assertions involve multiple layers of validation within a single assertion.
215
+
216
+
**Examples:**
217
+
- Assert if both the login button is enabled and the welcome message is visible.
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.
45
45
46
-
1. In the Project's dashboard, click on **Settings** in the top right hand side.
46
+
To access the System & Custom Fields settings, click on **Settings** in the top right hand side in the Project's dashboard.
2.You will be able to view the **System Fields** and **Custom Fields**.
50
+
You can manage your **System** and **Custom Fields** in this Fields page.
51
51
52
-
- 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**.
52
+
### System Fields
53
+
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, test runs or instances. 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**.
Custom field values can be set for System Field but for Test Runs this customization is only applicatble for the `Status` field.
57
+
:::
55
58
56
-
- 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.
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.
Test Manager now provides Audit Logs for test instance execution. Audit Logs bring visibility into the **who, what, and when** for every test execution. This is critical for teams working in regulated environments, or those needing high accountability in their QA processes.
40
+
41
+
With Audit logs you can store the execution history of your tests and even run parallel execution sessions without losing the context on individual executions as every action will be logged with clear indication of time stamps & executor.
42
+
43
+
## Details captured in Audit Logs
44
+
45
+
- Test Instance & Steps `Status` changes.
46
+
- Test Instance & Steps `Remarks or attachment` changes.
47
+
- Test Instance Assignee changes.
48
+
49
+
You can view the Audit Logs by clicking on the `View Execution Log`.
When you delete a configuration or a test case, all associated audit logs are removed. This is because the action deletes the entire instance. If you then add the same test case and configuration again, it creates a brand new instance with no prior audit history.
0 commit comments