Open planetf1 opened 4 years ago
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).
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.
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.
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.
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.
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.
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
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