ci: initial test pipeline UI

[frank-bee]

fixes #107

[github-actions]

Code Coverage Report

Project	Statements Rate	Branch Rate	Indicator
packages/autopilot-utils	96.71%	90.08%	💚
dist/coverage/python	96.71%	90.08%	💚
apps/splunk-fetcher	92.51%	82.00%	💚
apps/sharepoint-fetcher	84.83%	76.62%	💚
apps/sharepoint-evaluator	94.09%	90.48%	💚
apps/sharepoint	84.06%	67.24%	💚
apps/security-scanner	0.00%	0.00%	💔
apps/pex-tool	93.07%	78.05%	💚
apps/pdf-signature-evaluator	67.48%	48.80%	💛
apps/papsr	98.28%	94.74%	💚
apps/filecheck	98.53%	96.30%	💚
apps/excel-tools	78.37%	62.89%	💛
apps/artifactory-fetcher	98.51%	92.86%	💚
Total	87.16%	75.59%	💚

[frank-bee]

@fbufler @FlorianZieglerBosch I think this is rather a general issue with the test execution than actual errors

[fbufler]

indeed, so i ran the tests out from the yaku-ui folder could that be the difference?

[frank-bee]

@fbufler what do you mean , you run it inside the folder in your screen capture, not?

[fbufler]

@fbufler what do you mean , you run it inside the folder in your screen capture, not?

Yes I do.

cd yaku-ui
npm install -ws --include-workspace-root
npm run build
npm run test

(Unsure if it works without the build as I cant really test it well)

[fbufler]

Not sure but isn't the build part missing?
We stop at testing but based on the workflow name I would assume that we also run npm run build.
If that's not the case LGTM

[frank-bee]

npm run build is done in the docker build here , I can refactor this later