question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Increase coverage of frontend unit tests

See original GitHub issue

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

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

UI Components

  • Test error dialogs - linked to issue #687
    • Pipeline Runtime (#2870)

Services

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

Issue Analytics

  • State:open
  • Created 2 years ago
  • Comments:6 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
kusamkaur16commented, Feb 22, 2022

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.

0reactions
vhada7commented, Jul 15, 2022

Hi Could I work on this ! Thanks

Read more comments on GitHub >

github_iconTop Results From Across the Web

Code Coverage Best Practices for Frontend Apps - TestProject
Focus on test quality instead of quantity · Work on improving code coverage across the board · Make sure that frequently changing code...
Read more >
Code Coverage & Frontend Testing - Muhammad Rehan Saeed
Policies describe 80% plus unit test coverage and our React devs are pushing back a lot, arguing there is little logic in React...
Read more >
Frontend Unit Testing Best Practices - Meticulous
A guide on some of the best practices for frontend unit testing, including covering libraries like Jest with various code examples.
Read more >
Improving Test Coverage - Semantic Designs
The usual way to increase covered code answer is "code more tests" that exercise additional code. To minimize test coding effort, you want...
Read more >
Improve your component test coverage with this one weird trick
This type of test is very effective in terms of improving coverage numbers with only a small amount of effort. You can also...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found