🎨 Improving E2E tests: expected_service_running

[matusdrobuliak66]

What do these changes do?

• 🎨 Improving E2E Tests: Enhance the method for determining whether a service is running (expected_service_running). The service is considered running either when this information is received via socketio or when a 200 response is returned from the service endpoint (as the frontend does).

Related issue/s

How to test

Dev-ops checklist

• No ENV changes or I properly updated ENV (read the instruction)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 87.76%. Comparing base (7ec1d25) to head (f4ba833).
Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #6739      +/-   ##
==========================================
+ Coverage   87.74%   87.76%   +0.01%     
==========================================
  Files        1570     1563       -7     
  Lines       63322    63121     -201     
  Branches     2119     2119              
==========================================
- Hits        55564    55396     -168     
+ Misses       7431     7398      -33     
  Partials      327      327              

Flag	Coverage Δ
integrationtests	64.88% <ø> (-0.04%)	⬇️
unittests	85.71% <ø> (+<0.01%)	⬆️

Components	Coverage Δ
api	∅ <ø> (∅)
pkg_aws_library	93.38% <ø> (ø)
pkg_dask_task_models_library	96.87% <ø> (ø)
pkg_models_library	92.01% <ø> (ø)
pkg_notifications_library	83.79% <ø> (ø)
pkg_postgres_database	87.33% <ø> (ø)
pkg_service_integration	71.44% <ø> (ø)
pkg_service_library	76.50% <ø> (ø)
pkg_settings_library	91.42% <ø> (ø)
pkg_simcore_sdk	85.27% <ø> (ø)
agent	96.98% <ø> (ø)
api_server	89.88% <ø> (ø)
autoscaling	95.22% <ø> (ø)
catalog	89.42% <ø> (ø)
clusters_keeper	98.72% <ø> (ø)
dask_sidecar	91.32% <ø> (ø)
datcore_adapter	94.05% <ø> (ø)
director	58.38% <ø> (ø)
director_v2	90.80% <ø> (-0.13%)	⬇️
dynamic_scheduler	96.59% <ø> (ø)
dynamic_sidecar	89.78% <ø> (ø)
efs_guardian	90.01% <ø> (ø)
invitations	93.51% <ø> (ø)
osparc_gateway_server	85.41% <ø> (+0.26%)	⬆️
payments	92.87% <ø> (ø)
resource_usage_tracker	90.80% <ø> (ø)
storage	89.76% <ø> (ø)
webclient	∅ <ø> (∅)
webserver	88.72% <ø> (ø)

---

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 7ec1d25...f4ba833. Read the comment docs.

[sanderegg]

thanks, added a few comments

[bisgaard-itis]

👍🏻

[odeimaiz]

The frontend doesn't strictly expect a 200 to determine that the backend is ready. If the response status is less than 400, it means that the backend is ready (I believe that there are some services that respond with a 3XX)

[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