vdk-jupyter: add testing to CI/CD

[yonitoo]

What:
Add test stage to the .plugin-ci.yml file of the vdk-jupyter plugin.

Why:
Right now, there is a build and release stage but we would want to run the tests every time to ensure code robustness.

Testing Done:
The Gitlab pipeline is green.

Signed-off-by: Yoan Salambashev [email protected]

[murphp15]

It is very important to test this with failing cases and make sure the report makes it obvious which tests have failed.

[antoniivanov]

It is very important to test this with failing cases and make sure the report makes it obvious which tests have failed.

That's a very good point. Let us get into practice for tests to verify the "failing" logs, we should link a fail CI or uploaded failed logs in the Testing Done section so other people can see if they find it easy to understand the problem (since what is easy to see to me often it is not so to someone else).

[antoniivanov]

It is very important to test this with failing cases and make sure the report makes it obvious which tests have failed.

That's a very good point. Let us get into practice for tests to verify the "failing" logs, we should link a fail CI or uploaded failed logs in the Testing Done section so other people can see if they find it easy to understand the problem (since what is easy to see to me often it is not so to someone else).

Can you please add in testing done links to "failed" (even if faked) runs of gitlab tests so that we can see how easy it is to find the issue. Sort of like testing the error scenario for the CICD.

[antoniivanov]

I clicked to update your branch becasue there were some unrelated tests getting started. But it did not work properly.
You need to do git pull --rebase --autostash origin main locally and force push

The frontend tests are missing from the test report: https://gitlab.com/vmware-analytics/versatile-data-kit/-/pipelines/978573326/test_report

[yonitoo]

Addressed. The Frontend tests are not showing up in the test report.

[antoniivanov]

Looks good . Thanks!