Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Spike] Investigate how to test the JS part of the extension #20

Open
noklam opened this issue Jun 10, 2024 · 1 comment
Open

[Spike] Investigate how to test the JS part of the extension #20

noklam opened this issue Jun 10, 2024 · 1 comment
Assignees
Labels
DevOps Making sure the extension work, testing

Comments

@noklam
Copy link
Contributor

noklam commented Jun 10, 2024

Context:
There are only very few tests implemented at the moment since the features are changed and tested manually all the time. As it starts to stabilised we should aim at setting up test regularly.

Current test folder:

Instead of aiming at 100% coverage, it will be more beneficial to test certain behavior in a blackbox manner.

  • The extension is not a library, so risk of breaking a production codebase is low
  • Most people would upgrade it to the latest version (similar to most people upgrade kedro-viz to latest version because it's an application)
@jitu5 jitu5 added the DevOps Making sure the extension work, testing label Sep 24, 2024
@astrojuanlu astrojuanlu changed the title Automated test and improve test coverage [Spike] Investigate how to test the JS part of the extension Feb 3, 2025
@astrojuanlu
Copy link
Member

Possible inspiration:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DevOps Making sure the extension work, testing
Projects
Status: To Do
Development

No branches or pull requests

3 participants