test_execution_log (view) Content
- Start Row: 0
- Rows per Page: 50
- Total Rows: 51
- Current Page: 1
- Total Pages: 2
| TC-0012 | 1 | Send a **GET** request to the `/dashboard` endpoint. | passed | 15-12-2024 08:45:11 | 15-12-2024 08:45:13 |
| TC-0012 | 2 | Review the JSON response from the server response to ensure the fields for System and Dashboard are of integer value. | passed | 15-12-2024 08:45:13 | 15-12-2024 08:45:13 |
| TC-0005 | 1 | Send a GET request to the `/dashboard` API endpoint. | passed | 15-12-2024 08:45:11 | 15-12-2024 08:45:13 |
| TC-0005 | 2 | Check the response to verify that the `Daily_Cycle_Count_Url` is present in the `extension` section of the returned JSON data. | passed | 15-12-2024 08:45:13 | 15-12-2024 08:45:13 |
| TC-0005 | 3 | Ensure that the corresponding value of `valueInteger` is 3 under the `Daily_Cycle_Count_Url` | passed | 15-12-2024 08:45:13 | 15-12-2024 08:45:13 |
| TC-0010 | 1 | Send a **GET** request to the `/dashboard` endpoint. | passed | 15-12-2024 08:45:11 | 15-12-2024 08:45:13 |
| TC-0010 | 2 | Review the JSON response from the server response contains the `extension` field, which should include a `Dashboard_Count_Url` entry and the `valueInteger` should be greater than 0. | passed | 15-12-2024 08:45:13 | 15-12-2024 08:45:13 |
| TC-0006 | 1 | Send a **GET** request to the `/dashboard` endpoint. | passed | 15-12-2024 08:45:11 | 15-12-2024 08:45:13 |
| TC-0006 | 2 | Inspect the response to check if the Dashboard Count field is included inside the extension array in the returned JSON data. | passed | 15-12-2024 08:45:13 | 15-12-2024 08:45:13 |
| TC-0011 | 1 | Send a **GET** request to the `/dashboard` endpoint. | passed | 15-12-2024 08:45:11 | 15-12-2024 08:45:13 |
| TC-0011 | 2 | Review the JSON response from the server response contains the `extension` field, which should include a `Dashboard_Count_Url` and `system_Count_Url` value. | passed | 15-12-2024 08:45:13 | 15-12-2024 08:45:13 |
| TC-0007 | 1 | Send a **GET** request to the `/dashboard` endpoint. | passed | 15-12-2024 08:45:11 | 15-12-2024 08:45:13 |
| TC-0007 | 2 | Review the JSON response from the server that the `valueInteger` field under the `System_count_Url` extension contains a value that is not an integer (e.g., contains special characters, decimals, or leading zeros). | failed | 15-12-2024 08:45:13 | 15-12-2024 08:45:13 |
| TC-0009 | 1 | Send a **GET** request to the `/dashboard` endpoint. | passed | 15-12-2024 08:45:11 | 15-12-2024 08:45:13 |
| TC-0009 | 2 | Review the JSON response from the server response contains the `extension` field, which should include a `System_Count_Url` entry and the `valueInteger` should be greater than 0. | passed | 15-12-2024 08:45:13 | 15-12-2024 08:45:13 |
| TC-0008 | 1 | Send a **GET** request to the `/dashboard` endpoint. | passed | 15-12-2024 08:45:11 | 15-12-2024 08:45:13 |
| TC-0008 | 2 | Review the JSON response from the server that the valueInteger field under the Dashboard_Count_Url extension contains a value that is not an integer (e.g., contains special characters, decimals, or leading zeros). | passed | 15-12-2024 08:45:13 | 15-12-2024 08:45:13 |
| TC-0003 | 1 | Send a login request to the API with the username field populated but the password field missing. | passed | 15-12-2024 08:45:11 | 15-12-2024 08:45:13 |
| TC-0003 | 2 | Check if the login attempt is blocked, and an appropriate error message is returned (e.g., Password is required) | passed | 15-12-2024 08:45:13 | 15-12-2024 08:45:13 |
| TC-0001 | 1 | Send a POST request to the login API endpoint with valid credentials (username and password) | passed | 15-12-2024 08:45:11 | 15-12-2024 08:45:13 |
| TC-0001 | 2 | Verify that the request returns a 200 HTTP status code indicating success. | passed | 15-12-2024 08:45:13 | 15-12-2024 08:45:13 |
| TC-0001 | 3 | Verify that the response contains a valid authentication token in the response body | passed | 15-12-2024 08:45:13 | 15-12-2024 08:45:13 |
| TC-0004 | 1 | Send a POST request to the API's login endpoint with an empty payload (`{}`). | passed | 15-12-2024 08:45:11 | 15-12-2024 08:45:13 |
| TC-0004 | 2 | Verify the status code of the response is 400 | failed | 15-12-2024 08:45:13 | 15-12-2024 08:45:13 |
| TC-0004 | 3 | Check the response message for appropriate error handling (e.g., Invalid input or Payload cannot be empty) | failed | 15-12-2024 08:45:13 | 15-12-2024 08:45:13 |
| TC-0002 | 1 | Send a POST request to the API login endpoint without including the credentials in fields of the request body. | passed | 15-12-2024 08:45:11 | 15-12-2024 08:45:13 |
| TC-0002 | 2 | Observe the response from the API after submitting the request. | failed | 15-12-2024 08:45:13 | 15-12-2024 08:45:13 |
| TC-0014 | 1 | Send a **GET** request to the `/search` endpoint. | passed | 15-12-2024 08:45:11 | 15-12-2024 08:45:13 |
| TC-0014 | 2 | Review the JSON response from the server response should include the `PerformedDateTime` field with the correct date and time. | passed | 15-12-2024 08:45:13 | 15-12-2024 08:45:13 |
| TC-0016 | 1 | Send a **GET** request to the `/search` endpoint. | passed | 15-12-2024 08:45:11 | 15-12-2024 08:45:13 |
| TC-0016 | 2 | Review the JSON response from the server response data contains the 'Result'field exists within the response data. | passed | 15-12-2024 08:45:13 | 15-12-2024 08:45:13 |
| TC-0013 | 1 | Send a **GET** request to the `/search` endpoint. | passed | 15-12-2024 08:45:11 | 15-12-2024 08:45:13 |
| TC-0013 | 2 | Review the JSON response from the server response should include a JSON object with a resourceType of Bundle, containing an array of entries with relevant details about each procedure performed. The procedures should have accurate performedDateTime, outcome, status, and associated references. | passed | 15-12-2024 08:45:13 | 15-12-2024 08:45:13 |
| TC-0015 | 1 | Send a **GET** request to the `/search` endpoint. | passed | 15-12-2024 08:45:11 | 15-12-2024 08:45:13 |
| TC-0015 | 2 | Review the JSON response from the server response data contains the `MRC result` object with the expected attributes. | passed | 15-12-2024 08:45:13 | 15-12-2024 08:45:13 |
| TC-0024 | 1 | Send a request to the API endpoint using a REST client like Postman or playwright script. | passed | 15-12-2024 08:45:11 | 15-12-2024 08:45:13 |
| TC-0024 | 2 | Observe and record the response from the client/application. | passed | 15-12-2024 08:45:13 | 15-12-2024 08:45:13 |
| TC-0024 | 3 | Verify if the error code and message align with the expected format (e.g., `503 Service Unavailable` or `Connection Refused`). | passed | 15-12-2024 08:45:13 | 15-12-2024 08:45:13 |
| TC-0025 | 1 | Send a GET request to an incorrect endpoint (e.g., `/logins`). | passed | 15-12-2024 08:45:11 | 15-12-2024 08:45:13 |
| TC-0025 | 2 | Observe the response status code and verify it matches the expected error code (e.g., `404 Not Found`) and Confirm that the error message does not reveal sensitive server or API information. | passed | 15-12-2024 08:45:13 | 15-12-2024 08:45:13 |
| TC-0023 | 1 | Send a request (GET/POST/PUT depending on the API) to the target endpoint. | passed | 15-12-2024 08:45:11 | 15-12-2024 08:45:13 |
| TC-0023 | 2 | Capture the JSON response from the API. | passed | 15-12-2024 08:45:13 | 15-12-2024 08:45:13 |
| TC-0023 | 3 | Compare the response body against the schema defined in the IG using a schema validation tool. | passed | 15-12-2024 08:45:13 | 15-12-2024 08:45:13 |
| TC-0023 | 4 | Verify that all required fields are present and adhere to the expected data types and formats. | passed | 15-12-2024 08:45:13 | 15-12-2024 08:45:13 |
| TC-0021 | 1 | Launch the Chrome browser on the Linux system. | passed | 15-12-2024 08:45:11 | 15-12-2024 08:45:13 |
| TC-0021 | 2 | Enter the URL for the all API endpoint and press Enter. | passed | 15-12-2024 08:45:13 | 15-12-2024 08:45:13 |
| TC-0021 | 3 | Observe the response and validate it matches the expected output. | passed | 15-12-2024 08:45:13 | 15-12-2024 08:45:13 |
| TC-0021 | 4 | Repeat steps 1-3 using Firefox browsers. | passed | 15-12-2024 08:45:13 | 15-12-2024 08:45:13 |
| TC-0022 | 1 | Start the API server by connecting the tailscale connection. | passed | 15-12-2024 08:45:11 | 15-12-2024 08:45:13 |
| TC-0022 | 2 | Open the automation script and send a GET request to the API endpoint. | passed | 15-12-2024 08:45:13 | 15-12-2024 08:45:13 |
Error We are sorry, but an error occurred while generating this page. You should contact the site's administrator.
Error in query number 6:
Parsing failed: SQLPage couldn't understand the SQL file. Please check for syntax errors:
SELECT 'text' AS component,
(SELECT CASE WHEN $current_page > 1 THEN '[Previous](?limit=' || $limit || '&offset=' || ($offset - $limit) || ')' ELSE ' END) || ' ' ||
⬆️
'(Page ' || $current_page || ' of ' || $total_pages || ') ' ||
Backtrace
sql parser error: Expected: END, found: ' ||
' at Line: 42, Column: 149"console/content/view/test_execution_log.auto.sql" contains a syntax error preventing SQLPage from parsing and preparing its SQL statements.You can hide error messages like this one from your users by setting the 'environment' configuration option to 'production'.