Skip to content
📖 Release (stage)

Merge pull request #235 from RedisInsight/fix/s3_path #8

Sign in to view logs

Merge pull request #235 from RedisInsight/fix/s3_path

Merge pull request #235 from RedisInsight/fix/s3_path #8

GitHub Actions / Test results: E2E (linux) 2th node succeeded Dec 20, 2024 in 0s

20 passed, 4 failed and 0 skipped

Tests failed

❌ tests/e2e/mochawesome-report/junit-report.xml

24 tests were completed in 585s with 20 passed, 4 failed and 0 skipped.

Test suite Passed Failed Skipped Time
CLI critical 1❌ 20s
Edit Key values verification 5✅ 1❌ 215s
Set TTL for Key 1✅ 1❌ 164s
Tree view verifications for big database 1✅ 1❌ 37s

❌ CLI critical

"before all" hook for "Verify that Redis returns error if command is not correct when user works with CLI"
  ❌ CLI critical "before all" hook for "Verify that Redis returns error if command is not correct when user works with CLI"
	TimeoutError: Workbench was not loaded properly after 20000 ms.

❌ Edit Key values verification

Verify that user can edit Hash Key field
  ✅ Edit Key values verification Verify that user can edit Hash Key field
Verify that user can edit Zset Key member
  ✅ Edit Key values verification Verify that user can edit Zset Key member
Verify that user can edit List Key element
  ✅ Edit Key values verification Verify that user can edit List Key element
Verify that user can edit String value
  ❌ Edit Key values verification Verify that user can edit String value
	StaleElementReferenceError: stale element reference: stale element not found in the current frame
Verify that user can edit JSON Key value
  ✅ Edit Key values verification Verify that user can edit JSON Key value
Verify that user can see the message that data type not currently supported when open any of the unsupported data types
  ✅ Edit Key values verification Verify that user can see the message that data type not currently supported when open any of the unsupported data types

❌ Set TTL for Key

Verify that user can specify TTL for Key
  ✅ Set TTL for Key Verify that user can specify 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
	TimeoutError: Waiting for element to be located By(xpath, //vscode-button[@data-testid='refresh-keys'])

❌ 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 total number of keys, the number of keys scanned, the “Scan more” control displayed at the top of Tree view
	AssertionError: incorrect count is displayed: expected false to deeply equal true
Verify that when user deletes the key he can see the key is removed from the folder
  ✅ Tree view verifications for big database Verify that when user deletes the key he can see the key is removed from the folder

Annotations

Check failure on line 0 in tests/e2e/mochawesome-report/junit-report.xml

See this annotation in the file changed.

@github-actions github-actions / Test results: E2E (linux) 2th node

CLI critical ► "before all" hook for "Verify that Redis returns error if command is not correct when user works with CLI" ► CLI critical "before all" hook for "Verify that Redis returns error if command is not correct when user works with CLI" 

Failed test found in:
  tests/e2e/mochawesome-report/junit-report.xml
Error:
  TimeoutError: Workbench was not loaded properly after 20000 ms.
Raw output 
TimeoutError: Workbench was not loaded properly after 20000 ms.
Wait timed out after 20062ms
    at /home/runner/work/Redis-for-VS-Code/Redis-for-VS-Code/tests/e2e/node_modules/selenium-webdriver/lib/webdriver.js:913:22
    at processTicksAndRejections (node:internal/process/task_queues:95:5)

Check failure on line 0 in tests/e2e/mochawesome-report/junit-report.xml

See this annotation in the file changed.

@github-actions github-actions / Test results: E2E (linux) 2th node

Edit Key values verification ► Verify that user can edit String value ► Edit Key values verification Verify that user can edit String value 

Failed test found in:
  tests/e2e/mochawesome-report/junit-report.xml
Error:
  StaleElementReferenceError: stale element reference: stale element not found in the current frame
Raw output 
StaleElementReferenceError: stale element reference: stale element not found in the current frame
  (Session info: chrome=128.0.6613.186)
    at Object.throwDecodedError (node_modules/selenium-webdriver/lib/error.js:521:15)
    at parseHttpResponse (node_modules/selenium-webdriver/lib/http.js:514:13)
    at Executor.execute (node_modules/selenium-webdriver/lib/http.js:446:28)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Driver.execute (node_modules/selenium-webdriver/lib/webdriver.js:742:17)

Check failure on line 0 in tests/e2e/mochawesome-report/junit-report.xml

See this annotation in the file changed.

@github-actions github-actions / Test results: E2E (linux) 2th node

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 

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='refresh-keys'])
Raw output 
TimeoutError: Waiting for element to be located By(xpath, //vscode-button[@data-testid='refresh-keys'])
Wait timed out after 5140ms
    at /home/runner/work/Redis-for-VS-Code/Redis-for-VS-Code/tests/e2e/node_modules/selenium-webdriver/lib/webdriver.js:913:22
    at processTicksAndRejections (node:internal/process/task_queues:95:5)

Check failure on line 0 in tests/e2e/mochawesome-report/junit-report.xml

See this annotation in the file changed.

@github-actions github-actions / Test results: E2E (linux) 2th node

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 ... 

Failed test found in:
  tests/e2e/mochawesome-report/junit-report.xml
Error:
  AssertionError: incorrect count is displayed: expected false to deeply equal true
Raw output 
AssertionError: incorrect count is displayed: expected false to deeply equal true
    at Context.<anonymous> (src/tests/tree-view/tree-view-big-db.e2e.ts:40:78)
    at Generator.next (<anonymous>)
    at fulfilled (dist/tests/tree-view/tree-view-big-db.e2e.js:5:58)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)

      + expected - actual

      -false
      +true
View more details on GitHub Actions