[GSK-1476] introducing debug_description in test decorator#1290
[GSK-1476] introducing debug_description in test decorator#1290rabah-khalek merged 36 commits intomainfrom
Conversation
|
@Googleton, I introduced the default message, What's left is to propagate it for every test with a custom message. |
|
Kudos, SonarCloud Quality Gate passed! |
…-1476-debug-description
…-1476-debug-description
…-1476-debug-description
Improve codestyle in websocket/utils.py
…-1476-debug-description
* performance * adjusted bold rendering * added bold to default message * statistic * metamorhpic * drift * calibration * adjusted frontend * implemented @jmsquare's feedback * fixed tests
Inokinoki
left a comment
There was a problem hiding this comment.
Nice work @rabah-khalek for the debug description messages!
Could you plz test to start a new instance without existing DB from main and connect an internal ML worker (so that the test function does not contain debug description), and then restart both DB and worker from this branch, to see whether the debug descriptions are updated or not.
I tested locally, it seems to be working now.
|
@Inokinoki @Googleton the backend build seems to be failing, could you please have a look? I hope it's an easy fix. |
Checked, it seems to be random network issue in the last CI. This one passes |
|
Kudos, SonarCloud Quality Gate passed! |












The idea is to describe what the debug does for every test when a user clicks on the button