✅ Add e2e tests for metamodeling

[alexpargon]

What do these changes do?

Added test for the Meta Modeling services:

• SUMO: Surrogate Model
• UQ: Uncertainty Quantification
• MOGA: Multi Objective Genetic Algorithms

to this end, mmux-testids where added to the meta modeling service.

Related issue/s

• resolves E2E testing of MMUX services mmux_vite#232

How to test

The changes include a new test phase which executes e2e playwright tests on the osparc service, by creating a project with JSONIFIER, creating a function from this proyect, and then launching MMuX to populate the function with jobs and use them to test each of the tools MMuX enables

Dev-ops

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 88.72%. Comparing base (87a16bc) to head (6ff83b3).
⚠️ Report is 4 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #8457      +/-   ##
==========================================
+ Coverage   87.13%   88.72%   +1.58%     
==========================================
  Files        2010     1802     -208     
  Lines       79007    71413    -7594     
  Branches     1377      863     -514     
==========================================
- Hits        68844    63359    -5485     
+ Misses       9764     7835    -1929     
+ Partials      399      219     -180     

Flag	Coverage Δ		*Carryforward flag
integrationtests	63.86% <ø> (-0.11%)	⬇️
unittests	87.93% <ø> (+1.74%)	⬆️	Carriedforward from 749d00b

*This pull request uses carry forward flags. Click here to find out more.

Components	Coverage Δ
pkg_aws_library	95.30% <ø> (ø)
pkg_celery_library	83.43% <ø> (ø)
pkg_dask_task_models_library	79.37% <ø> (ø)
pkg_models_library	92.83% <ø> (ø)
pkg_notifications_library	85.20% <ø> (ø)
pkg_postgres_database	88.03% <ø> (ø)
pkg_service_integration	72.76% <ø> (ø)
pkg_service_library	∅ <ø> (∅)
pkg_settings_library	90.21% <ø> (ø)
pkg_simcore_sdk	84.45% <ø> (-0.14%)	⬇️
agent	93.44% <ø> (ø)
api_server	91.37% <ø> (ø)
autoscaling	95.83% <ø> (ø)
catalog	92.06% <ø> (ø)
clusters_keeper	99.14% <ø> (ø)
dask_sidecar	91.72% <ø> (ø)
datcore_adapter	97.95% <ø> (ø)
director	75.68% <ø> (ø)
director_v2	90.73% <ø> (-0.59%)	⬇️
dynamic_scheduler	96.66% <ø> (ø)
dynamic_sidecar	82.00% <ø> (ø)
efs_guardian	89.83% <ø> (ø)
invitations	90.90% <ø> (ø)
payments	92.70% <ø> (ø)
resource_usage_tracker	92.22% <ø> (+0.05%)	⬆️
storage	86.42% <ø> (-0.20%)	⬇️
webclient	∅ <ø> (∅)
webserver	86.44% <ø> (-0.28%)	⬇️

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 87a16bc...6ff83b3. Read the comment docs.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[mergify]

🧪 CI Insights

Here's what we observed from your CI run for 6ff83b3.

✅ Passed Jobs With Interesting Signals

Pipeline	Job	Signal	Health on master	Retries	🔍 CI Insights	📄 Logs
CI	unit-tests	Base branch is broken, but the job passed. Looks like this might be a real fix 💪		0	View	View

[pcrespov]

Thanks for the PR!

We usually like to include a bit more context to help us track changes, connect related issues, and coordinate work more easily. It shouldn’t take much time.

A few suggestions:

• Assign yourself to the issue (I went ahead and did that for you this time).
• Add the relevant project and labels.
• Include a short description — you can even use AI for that — and fill out the PR template sections where applicable (e.g. enumerate related PO issues )

[sanderegg]

This looks good, there are a few things I would suggest:

• no need to wait so much everywhere with timeouts in the production test (it shall run as fast as possible) if there is no functional need (click already has an integrated 30 seconds default timeout)
• mmux-testid this is very nice! please check the locations where you do not use it as this is fragile and will for sure break as soon as you modify the UI
• ideally after the test everything should be deleted and cleaned so we do not accumulate e2e data (and actually pay for it)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[pcrespov]

thx

[sanderegg]

thanks!

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud