fix for api and remove button #103
tests.yml
on: push
Approve E2E tests
3s
frontend-tests
/
Frontend tests
Matrix: e2e-linux-test / E2E tests
e2e-linux-test
/
merge-artifacts
0s
Deployment protection rules
Reviewers, timers, and other rules protecting deployments in this run
Event | Environments |
---|---|
vlad-dargel
approved
|
e2e-approve |
Annotations
26 errors and 6 warnings
Actions with Key List ► Verify that key deleted properly from the list ► Actions with Key List Verify that key deleted properly from the list:
tests/e2e/mochawesome-report/junit-report.xml#L0
Failed test found in:
tests/e2e/mochawesome-report/junit-report.xml
Error:
TimeoutError: Waiting for element to be located By(xpath, //vscode-button[starts-with(@data-testid, 'remove-key-gehwosiane')])
|
Format switcher functionality ► "before each" hook for "Formatters saved selection" ► Format switcher functionality "before each" hook for "Formatters saved selection":
tests/e2e/mochawesome-report/junit-report.xml#L0
Failed test found in:
tests/e2e/mochawesome-report/junit-report.xml
Error:
AssertionError: The creation of new list key request failed: expected 400 to deeply equal 201
|
List Key verification ► "before each" hook for "Verify that user can search List element by index" ► List Key verification "before each" hook for "Verify that user can search List element by index":
tests/e2e/mochawesome-report/junit-report.xml#L0
Failed test found in:
tests/e2e/mochawesome-report/junit-report.xml
Error:
TimeoutError: Waiting for element to be located By(xpath, //*[@data-testid="key-nokavcuhip"])
|
List Key verification for db with version <6.2 ► Verify that user can remove only one element for List for Redis v. <6.2 ► List Key verification for db with version <6.2 Verify that user can remove only one element for List for Redis v. <6.2:
tests/e2e/mochawesome-report/junit-report.xml#L0
Failed test found in:
tests/e2e/mochawesome-report/junit-report.xml
Error:
TimeoutError: Waiting for element to be located By(xpath, //vscode-button[@data-testid='add-key-button'])
|
e2e-linux-test / E2E tests (0)
Process completed with exit code 1.
|
Edit Databases ► Verify that user can edit Standalone DB ► Edit Databases Verify that user can edit Standalone DB:
tests/e2e/mochawesome-report/junit-report.xml#L0
Failed test found in:
tests/e2e/mochawesome-report/junit-report.xml
Error:
AssertionError: CA certificate is incorrect: the given combination of arguments (null and string) is invalid for this assertion. You can use an array, a map, an object, a set, a string, or a weakset instead of a string
|
Formatters ► Verify that user can see highlighted key details in JSON format ► Formatters Verify that user can see highlighted key details in JSON format:
tests/e2e/mochawesome-report/junit-report.xml#L0
Failed test found in:
tests/e2e/mochawesome-report/junit-report.xml
Error:
AssertionError: The creation of new list key request failed: expected 400 to deeply equal 201
|
Formatters ► Verify that user can see highlighted key details in PHP serialized format ► Formatters Verify that user can see highlighted key details in PHP serialized format:
tests/e2e/mochawesome-report/junit-report.xml#L0
Failed test found in:
tests/e2e/mochawesome-report/junit-report.xml
Error:
AssertionError: The creation of new list key request failed: expected 400 to deeply equal 201
|
Formatters ► Verify that user can see highlighted key details in Msgpack format ► Formatters Verify that user can see highlighted key details in Msgpack format:
tests/e2e/mochawesome-report/junit-report.xml#L0
Failed test found in:
tests/e2e/mochawesome-report/junit-report.xml
Error:
AssertionError: The creation of new list key request failed: expected 400 to deeply equal 201
|
Formatters ► Verify that user can see highlighted key details in Protobuf format ► Formatters Verify that user can see highlighted key details in Protobuf format:
tests/e2e/mochawesome-report/junit-report.xml#L0
Failed test found in:
tests/e2e/mochawesome-report/junit-report.xml
Error:
AssertionError: The creation of new list key request failed: expected 400 to deeply equal 201
|
Formatters ► Verify that user can see highlighted key details in Java serialized format ► Formatters Verify that user can see highlighted key details in Java serialized format:
tests/e2e/mochawesome-report/junit-report.xml#L0
Failed test found in:
tests/e2e/mochawesome-report/junit-report.xml
Error:
AssertionError: The creation of new list key request failed: expected 400 to deeply equal 201
|
Formatters ► Verify that user can see highlighted key details in Pickle format ► Formatters Verify that user can see highlighted key details in Pickle format:
tests/e2e/mochawesome-report/junit-report.xml#L0
Failed test found in:
tests/e2e/mochawesome-report/junit-report.xml
Error:
AssertionError: The creation of new list key request failed: expected 400 to deeply equal 201
|
Formatters ► Verify that user can see highlighted key details in Vector 32-bit format ► Formatters Verify that user can see highlighted key details in Vector 32-bit format:
tests/e2e/mochawesome-report/junit-report.xml#L0
Failed test found in:
tests/e2e/mochawesome-report/junit-report.xml
Error:
AssertionError: The creation of new list key request failed: expected 400 to deeply equal 201
|
Formatters ► Verify that user can see highlighted key details in Vector 64-bit format ► Formatters Verify that user can see highlighted key details in Vector 64-bit format:
tests/e2e/mochawesome-report/junit-report.xml#L0
Failed test found in:
tests/e2e/mochawesome-report/junit-report.xml
Error:
AssertionError: The creation of new list key request failed: expected 400 to deeply equal 201
|
Formatters ► Verify that user can edit the values in the key regardless if they are valid in JSON format or not ► Formatters Verify that user can edit the values in the key regardless if they are valid in JSON format or not:
tests/e2e/mochawesome-report/junit-report.xml#L0
Failed test found in:
tests/e2e/mochawesome-report/junit-report.xml
Error:
AssertionError: The creation of new list key request failed: expected 400 to deeply equal 201
|
Formatters ► Verify that user can edit the values in the key regardless if they are valid in Msgpack format or not ► Formatters Verify that user can edit the values in the key regardless if they are valid in Msgpack format or not:
tests/e2e/mochawesome-report/junit-report.xml#L0
Failed test found in:
tests/e2e/mochawesome-report/junit-report.xml
Error:
AssertionError: The creation of new list key request failed: expected 400 to deeply equal 201
|
e2e-linux-test / E2E tests (1)
Process completed with exit code 1.
|
Hash Key fields verification ► Verify that tab is closed if Hash was deleted from keys list ► Hash Key fields verification Verify that tab is closed if Hash was deleted from keys list:
tests/e2e/mochawesome-report/junit-report.xml#L0
Failed test found in:
tests/e2e/mochawesome-report/junit-report.xml
Error:
TimeoutError: Waiting for element to be located By(xpath, //vscode-button[starts-with(@data-testid, 'remove-key-lusbosjidi')])
|
Large key details verification ► Verify that user can download String key value as txt file when it has > 5000 characters ► Large key details verification Verify that user can download String key value as txt file when it has > 5000 characters:
tests/e2e/mochawesome-report/junit-report.xml#L0
Failed test found in:
tests/e2e/mochawesome-report/junit-report.xml
Error:
AssertionError: Edit key value button not disabled: expected true to deeply equal false
|
Set TTL for Key ► Verify that user can set ttl for Hash fields ► Set TTL for Key Verify that user can set ttl for Hash fields:
tests/e2e/mochawesome-report/junit-report.xml#L0
Failed test found in:
tests/e2e/mochawesome-report/junit-report.xml
Error:
TimeoutError: Waiting for element to be located By(xpath, //div[@data-testid="hash-ttl_content-value-Field1WithTtl"])
|
Tree view verifications for big database ► Verify that user can see the total number of keys, the number of keys scanned, the “Scan more” control displayed at the top of Tree view ► Tree view verifications for big database Verify that user can see the ...:
tests/e2e/mochawesome-report/junit-report.xml#L0
Failed test found in:
tests/e2e/mochawesome-report/junit-report.xml
Error:
AssertionError: incorrect count is displayed: expected false to deeply equal true
|
e2e-linux-test / E2E tests (2)
Process completed with exit code 1.
|
Add database ► Verify that user can add SSH tunnel with Password for Standalone database ► Add database Verify that user can add SSH tunnel with Password for Standalone database:
tests/e2e/mochawesome-report/junit-report.xml#L0
Failed test found in:
tests/e2e/mochawesome-report/junit-report.xml
Error:
ElementClickInterceptedError: element click intercepted: Element <iframe name="3bcab0d1-fba5-48b2-88f0-eab5cc828885" class="webview ready" sandbox="allow-scripts allow-same-origin allow-forms allow-pointer-lock allow-downloads" allow="cross-origin-isolated; autoplay; clipboard-read; clipboard-write" src="vscode-webview://0i8u8irvr256h7nmuisheotqfsrld9k2k25q2l38mgt8qusnk76d/index.html?id=3bcab0d1-fba5-48b2-88f0-eab5cc828885&origin=ec16d797-2e27-41d3-b309-0013b6b2beca&swVersion=4&extensionId=Redis.redis-for-vscode&platform=electron&vscode-resource-base-authority=vscode-resource.vscode-cdn.net&parentOrigin=vscode-file%3A%2F%2Fvscode-app" style="border: none; width: 100%; height: 100%; pointer-events: auto;" cd_frame_id_="1c1fb4d8399a9eefac0f4c2bbf6ad615"></iframe> is not clickable at point (900, 702). Other element would receive the click: <div class="notification-list-item-message" custom-hover="true">...</div>
|
Filtering per key name ► Verify that user can filter keys per data type ► Filtering per key name Verify that user can filter keys per data type:
tests/e2e/mochawesome-report/junit-report.xml#L0
Failed test found in:
tests/e2e/mochawesome-report/junit-report.xml
Error:
AssertionError: The creation of new list key request failed: expected 400 to deeply equal 201
|
Filtering per key name in DB with 10 millions of keys ► Verify that user can filter per key name using patterns in DB with 10-50 millions of keys ► Filtering per key name in DB with 10 millions of keys Verify that user can filter per key name using pat...:
tests/e2e/mochawesome-report/junit-report.xml#L0
Failed test found in:
tests/e2e/mochawesome-report/junit-report.xml
Error:
AssertionError: Keys filtered incorrectly by key type after scanning more: expected 'device_eu-central-1_12_set' to include 'hash'
|
e2e-linux-test / E2E tests (3)
Process completed with exit code 1.
|
Approve E2E tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
build-linux / Build linux
This extension consists of 1269 files, out of which 571 are JavaScript files. For performance reasons, you should bundle your extension: https://aka.ms/vscode-bundle-extension. You should also exclude unnecessary files by adding them to your .vscodeignore: https://aka.ms/vscode-vscodeignore.
|
e2e-linux-test / E2E tests (0)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
e2e-linux-test / E2E tests (1)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
e2e-linux-test / E2E tests (2)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
e2e-linux-test / E2E tests (3)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
linux-build
Expired
|
10.3 MB |
|
mocha-report-linux-node-0
Expired
|
376 KB |
|
mocha-report-linux-node-1
Expired
|
384 KB |
|
mocha-report-linux-node-2
Expired
|
383 KB |
|
mocha-report-linux-node-3
Expired
|
386 KB |
|