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.

Sign up for GitHub

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

Jump to bottom

Notebook test automation #6

Open

planetf1 opened this issue Mar 27, 2020 · 7 comments

Labels

build-improvement notebooks pinned testing

Member

planetf1 commented Mar 27, 2020

We have a few issues relating to automated testing:
See odpi/egeria#353 odpi/egeria#426

A precursor step is to automatically deploy an Egeria environment after a build

An initial attempt was made in .azure-pipelines/test . This used an existing k8s cluster but was not successful as the cluster in question wasn't funded.

We need to get this automation in place so that we can run tests more quickly and reliably.

Will look at one of

establishing a permanent capability to run a k8s cluster
running a mini cluster (single node) with a pipeline, ie using microk8s/k3s or similar

planetf1 self-assigned this

planetf1 added the testing label

planetf1 added the build-improvement label

Member Author

planetf1 commented Jul 31, 2020

odpi/egeria#426 added FVT tests to the build - which run with a single server (though could be more).
odpi/egeria#353 refers to adding CTS to build.

Both are specific actions with well defined test results.

A simple 'deployment' is too vague.

A sensible target here would be to automatically test our notebooks to avoid having to do this manually (even though it is fairly quick).

planetf1 changed the title ~~Deploy Egeria environment automatically after build~~ Notebook test automation

github-actions bot commented Sep 30, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 20 days if no further activity occurs. Thank you for your contributions.

github-actions bot added the no-issue-activity label

planetf1 removed the no-issue-activity label

github-actions bot commented Dec 2, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 20 days if no further activity occurs. Thank you for your contributions.

github-actions bot added the no-issue-activity label

planetf1 removed the no-issue-activity label

github-actions bot commented Feb 8, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 20 days if no further activity occurs. Thank you for your contributions.

github-actions bot added the no-issue-activity label

planetf1 removed the no-issue-activity label

github-actions bot commented Apr 10, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 20 days if no further activity occurs. Thank you for your contributions.

github-actions bot added the no-issue-activity label

planetf1 removed the no-issue-activity label

github-actions bot commented Jun 13, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 20 days if no further activity occurs. Thank you for your contributions.

github-actions bot added the no-issue-activity label

Member Author

planetf1 commented Jun 14, 2021

The intent of this test should be to validate our notebooks, not to run FVTs or similar.
At a minimum, ensuring the images are good, and that the key notebooks can at least be launched would be useful

planetf1 added pinned and removed no-issue-activity labels

planetf1 added the notebooks label

planetf1 transferred this issue from odpi/egeria

planetf1 mentioned this issue

standard models - asset consumer more-information moved from common to framework services #52

Closed

planetf1 removed their assignment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment