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
Test that the specs authored match what OpenSearch code is doing.
Early signal if OpenSearch is breaking specs.
What is the developer experience going to be?
Every PR will start various versions of OpenSearch, load the specs, run tests against the local version of OpenSearch.
What will it take to execute?
Unsure. Maybe there's an existing tool? Otherwise I would start with something simple that executes all GET requests and compares outputs against a previous recording. Then author requests/responses and compare. Finally, we need coverage to know how many of the APIs are invoked, how many request/response bodies are matched.
The text was updated successfully, but these errors were encountered:
What/Why
What are you proposing?
Coming from #271 (comment), we don't actually know whether the specs authored here are correct. Add integration tests that exercise these specs.
What users have asked for this feature?
See #271 (comment).
What problems are you trying to solve?
What is the developer experience going to be?
Every PR will start various versions of OpenSearch, load the specs, run tests against the local version of OpenSearch.
What will it take to execute?
Unsure. Maybe there's an existing tool? Otherwise I would start with something simple that executes all
GET
requests and compares outputs against a previous recording. Then author requests/responses and compare. Finally, we need coverage to know how many of the APIs are invoked, how many request/response bodies are matched.The text was updated successfully, but these errors were encountered: