potential bug: RAD_HOME in linux

.github/workflows/e2e-testing.yaml

@@ -8,8 +8,10 @@ on:
 jobs:
   test-e2e:
     strategy:
+      fail-fast: false
       matrix:
         os: [macos-latest, ubuntu-latest]
+        # os: [macos-latest]
     runs-on: ${{ matrix.os }}
     steps:
 

test/e2e/helpers/actions.ts

@@ -13,3 +13,13 @@ export async function openRadicleViewContainer(workbench: Workbench) {
 
   await radicleViewControl?.openView()
 }
+
+export async function closeRadicleViewContainer(workbench: Workbench) {
+  const activityBar = workbench.getActivityBar()
+  await activityBar.wait()
+
+  const radicleViewControl = await activityBar.getViewControl('Radicle')
+  await radicleViewControl?.wait()
+
+  await radicleViewControl?.closeView()
+}

test/e2e/helpers/assertions.ts

@@ -23,6 +23,11 @@ export async function expectStandardSidebarViewsToBeVisible(workbench: Workbench
         return false
       }
     },
-    { timeoutMsg: 'expected the standard sidebar views to be visible' },
+    {
+      timeoutMsg: 'expected the standard sidebar views to be visible',
+      // TODO: zac fine tune these (globally?)
+      timeout: 20000,
+      interval: 500,
+    },
   )
 }

test/e2e/specs/httpd.spec.ts

@@ -0,0 +1,79 @@
+import { browser } from '@wdio/globals'
+import type { OutputView, Setting } from 'wdio-vscode-service'
+import { Key } from 'webdriverio'
+import { $ } from 'zx'
+import { nodeHomePath } from '../constants/config'
+
+describe('Httpd', () => {
+  it('finds and uses radicle identity', async () => {
+    const workbench = await browser.getWorkbench()
+    await workbench.executeCommand('Show Everything Logged in the Output Panel')
+    const outputView = await workbench.getBottomBar().openOutputView()
+
+    const settings = await workbench.openSettings()
+    const pathToNodeHomeSetting = await settings.findSetting(
+      'Path To Node Home',
+      'Radicle',
+      'Advanced',
+    )
+
+    await browser.waitUntil(async () => {
+      await setTextSettingValue(pathToNodeHomeSetting, nodeHomePath ?? '')
+
+      return (await getTextSettingValue(pathToNodeHomeSetting)) === nodeHomePath
+    })
+
+    const radSelf = await $`rad self`
+    console.log({ radSelf })
+
+    await expectOutputToContain(outputView, 'Using already unsealed Radicle identity')
+  })
+})
+
+async function expectOutputToContain(outputView: OutputView, expected: string) {
+  await browser.waitUntil(
+    async () => {
+      /**
+       * The text in the output console is split by newlines, which can be affected by the size
+       * of the window. To avoid this, we join the text into a single string.
+       */
+      const joinedText = (await outputView.getText()).join('')
+      console.log({ joinedText })
+
+      return joinedText.includes(expected)
+    },
+    {
+      timeoutMsg: `expected the output text to contain "${expected}"`,
+    },
+  )
+}
+
+/**
+ * Workaround to get the value of a `TextSetting`.
+ * The `getValue` method of a `TextSetting` seems to be wrongly implemented and returns null.
+ */
+async function getTextSettingValue(setting: Setting) {
+  return await setting.textSetting$.getValue()
+}
+
+async function setTextSettingValue(setting: Setting, value: string) {
+  await clearTextSetting(setting)
+  await setting.setValue(value)
+}
+
+async function clearTextSetting(setting: Setting) {
+  /**
+   * `.setValue('')` updates the value of the input but does not trigger an
+   * update in the extension. Not sure if this is a bug in the extension, vscode, or
+   * webdriverio.
+   *
+   * The following is a workaround that does trigger an update in the extension.
+   */
+  if ((await getTextSettingValue(setting)) === '') {
+    return
+  }
+
+  await setting.textSetting$.click()
+  await browser.keys([Key.Ctrl, 'a'])
+  await browser.keys(Key.Backspace)
+}

test/e2e/wdio.conf.ts

@@ -29,7 +29,7 @@ export const config: Options.Testrunner = {
       transpileOnly: true,
     },
   },
-  specs: ['./specs/**/*.ts'],
+  specs: ['./specs/httpd.spec.ts'],
   maxInstances: 10,
   capabilities: [
     {