You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
currently, grafana-client employs testing solely by mocking HTTP conversations. Because this does not cover real integration tests with Grafana, it is easy to miss regressions, like those which recently happened here.
On the other hand, both grafana-wtf, and Kotori, already feature such an integration test suite with Grafana. In this manner, the grafana-wtf test harness was able to catch this issue.
So, grafana-client will need to adopt that test suite soon, in order to improve compatibility and QA on different versions of Grafana, by adding them to a test matrix.
grafana-wtf/tests can be an inspiration for this. While being at it, we may split this off into a generic pytest-grafana package, in the same spirit like the recently conceived pytest-mqtt package.
With kind regards,
Andreas.
The text was updated successfully, but these errors were encountered:
Hi there,
currently,
grafana-client
employs testing solely by mocking HTTP conversations. Because this does not cover real integration tests with Grafana, it is easy to miss regressions, like those which recently happened here.204 No Content
responses from Grafana HTTP API #44delete_folder
in Grafana 9.3.0 #47/api/folders/{UID}
grafana/grafana#59546On the other hand, both
grafana-wtf
, and Kotori, already feature such an integration test suite with Grafana. In this manner, thegrafana-wtf
test harness was able to catch this issue.So,
grafana-client
will need to adopt that test suite soon, in order to improve compatibility and QA on different versions of Grafana, by adding them to a test matrix.grafana-wtf/tests can be an inspiration for this. While being at it, we may split this off into a generic
pytest-grafana
package, in the same spirit like the recently conceived pytest-mqtt package.With kind regards,
Andreas.
The text was updated successfully, but these errors were encountered: