-
Notifications
You must be signed in to change notification settings - Fork 26
Task: Replace mocha with vitest for SVelte tests #1659
Copy link
Copy link
Open
Labels
CIIssues related to CI workflowsIssues related to CI workflowsTDMLIssues related to TDMLIssues related to TDMLbuildIssues related to building of the codeIssues related to building of the codeconfigurationissues related to configurationissues related to configurationdata editorIssues related to the Data Editor capabilityIssues related to the Data Editor capabilitydebuggerIssues related to the DFDL debugger capabilityIssues related to the DFDL debugger capabilitydependenciesPull requests that update a dependency filePull requests that update a dependency filedocumentationImprovements or additions to documentationImprovements or additions to documentationextensionIssues releated to the VSCode ExtensionIssues releated to the VSCode ExtensiontestingUpdates to test suiteUpdates to test suite
Milestone
Metadata
Metadata
Assignees
Labels
CIIssues related to CI workflowsIssues related to CI workflowsTDMLIssues related to TDMLIssues related to TDMLbuildIssues related to building of the codeIssues related to building of the codeconfigurationissues related to configurationissues related to configurationdata editorIssues related to the Data Editor capabilityIssues related to the Data Editor capabilitydebuggerIssues related to the DFDL debugger capabilityIssues related to the DFDL debugger capabilitydependenciesPull requests that update a dependency filePull requests that update a dependency filedocumentationImprovements or additions to documentationImprovements or additions to documentationextensionIssues releated to the VSCode ExtensionIssues releated to the VSCode ExtensiontestingUpdates to test suiteUpdates to test suite
Type
Fields
Give feedbackNo fields configured for Task.
Projects
Status
No status
Task: Replace
mochawithvitestfor Svelte TestsDescription
mochaas the testsuite is no longer compatible for executing tests when the updated Svelte 5 runes exist within a testable source.Using
vitestwould be a complete, and compatible, solution as it is used alongsidevite. I feel that this would be the best solution given thatviteis now being used as a packaging dependency.Acceptance Criteria
vitestis successfully replaced formocha/chaiand all of the SVelte tests that exist and can execute while accurately reporting test case results.Additional Information
I have tested this locally and all of the test files execute withvitest, even the non Svelte files.Update
I originally had all tests executing and reporting correct results but upon inspecting under the hood of the native VSCode Test Explorer I found that it was smart enough to pull in mocha to run those tests within the
./src/tests/directory.vitestdoes not have to capability to provide the VSCode API due runtime dependency issues.mochawill still have to be used for those tests