Implemented Data Editor Svelte Test Structure

[stricklandrbls]

• Added yarn script to run data editor tests using Mocha.
• Added example function and Svelte store tests.

This is a simple directory structure and test suite setup that utilizes the mocha test suite that's currently a utilized dependency. The test:svelte script should be ran manually during development and is not currently implemented to be ran during packaging of the extension.

With the mocha -w option, it does not currently support traditional sourcing of the directory due a discrepancy with with node. ¹ Typing r s <Enter>, while the test:svelte script is watching, will manually source the directory structure and re-run the tests. ²

Closes #915

Footnotes

1. https://mochajs.org/#nodejs-native-esm-support ↩

2. https://mochajs.org/#-watch-w ↩

[shanedell]

I would say that either before or after node ./out/tests/runTest.js you want to run the svelte tests. So either,

"test": "sbt test && yarn test:svelte && node ./out/tests/runTest.js",

or

"test": "sbt test && node ./out/tests/runTest.js && yarn test:svelte",

I personally prefer the first option but either way is fine with me also. Once that is updated I think this is good to go.

[stricklandrbls]

I initially did not have the tests being ran during the projects tests because there were a lot of compilation errors within the svelte tests. This is because of #878

Although, I found out that there are only compilation errors when mocha is trying to compile the files with the errors. The example tests that I have do not have any so I went ahead and implemented your changes to the test scripts.

[stricklandrbls]

@shanedell I added a new script & modified 2 existing scripts:

• Added watch:svelte-tests - For having only the svelte tests watched during development.
• Changed test:svelte to not have the -w option for watching.
• Changed test to your first suggestion.

[stricklandrbls]

@shanedell I added a new script & modified 2 existing scripts:

* Added `watch:svelte-tests` - For having only the svelte tests watched during development.

* Changed `test:svelte` to not have the `-w` option for watching.

* Changed `test` to your first suggestion.

Looks like the mocha side is still failing on the CI side due to the same compilation errors I mentioned before. I'm not entirely sure why though because running mocha -r ts-node/register ./src/svelte/tests/**/*.test.ts or yarn test:svelte does not throw those errors on my machine.

Even running the full yarn test does not have any errors.

[nlewis05]

My local build is passing

[scholarsmate]

So far so good for me:

➜  daffodil-vscode-ctc-oss git:(setup-svelte-test-env) yarn test:svelte
yarn run v1.22.19
warning [email protected]: The engine "vscode" appears to be invalid.
$ mocha -r ts-node/register ./src/svelte/tests/**/*.test.ts


  Data Editor Stores ( Derived )
    regularSizedFile
      ✔ should return true on regular computed sized viewports
      ✔ should return false on non-regular computed sized viewports
    saveable
      ✔ should report boolean value derived from fileMetrics.changeCount

  Display Functions
    radixBytePad
      ✔ should return the appropriate text length per radix value given
    radixToString
      ✔ should return the correct radix index string from RadixValue


  5 passing (9ms)

✨  Done in 2.69s.

[shanedell]

+1