Increase coverage of frontend unit tests

[karlaspuldaro]

Currently the only packages containing front-end unit tests are pipeline-editor and services. It would be helpful to expand the unit test coverage across all other packages in Elyra, as well as add more tests to existing extensions.

This is an umbrella issue - subtasks can be delivered in separate PRs.

Pipeline Editor

• [ ] Test Pipeline Service (runtime types, runtimes, runtime images, runtime schema, node types, node paths)
• [ ] Test runtime utils (runtime data, config details)
• [ ] Test pipeline dialogs ( submit, export, version, migration, unsupported, clear - linked to issue #687)

Metadata Common (on hold)

Metadata Editor (on hold)

Code Snippets (on hold - metadata related)

• Test Code Snippet Widget (sorting, search, editor preview, language verification on insert)
• Test Code Snippet Service (find by language, delete)

Script Editor

• [x] Test Script Controller (available kernels) (#2576)
• [x] Test Script Runner (session connection, kernel status/messages, code output/errors)(#2576)

UI Components

• [ ] Test error dialogs - linked to issue #687

Services

• [x] Rename outdated test file application.spec.ts(#2523)
• [ ] Test ContentParser

[samali0996]

I'm interested in taking a look at this! I've added a file for PipelineService testing here (#2449), so I can build out that testing first

[samali0996]

Would also provide me with a good opportunity to understand the frontend components :)

[karlaspuldaro]

Thank you @samali0996 that would be great!

[kusamkaur16]

I'm interested in taking a look at the Rename outdated test file application.spec.ts subtask. It shouldn't interfere with Sam's work on PipelineService testing.

[karlaspuldaro]

Since this is an umbrella issue we probably won't complete all subtasks for 3.7 but we can continue the work on the next milestone.

@samali0996 Would you be able to open a PR for the Pipeline Service tests even if it's still in progress?

[vhada7]

Hi Could I work on this ! Thanks