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
Goal: as a client of libovsdb I want to be able to write unit tests on my side and have libovsdb provide a framework which enables me to validate the result of the database at the end of my test.
Background: This is almost possible today given the fact that any client can inspect the state of the cache using .Cache().Table() / .Cache().Table().Row() APIs. However what would be really neat is if the cache could just be dumped and serialized to a string using a Cache().Dump() function. What would be even better than that is if libovsdb could run in "test mode" and generate deterministic UUIDs for items in the rows that have references to other models.
Goal: as a client of libovsdb I want to be able to write unit tests on my side and have libovsdb provide a framework which enables me to validate the result of the database at the end of my test.
Background: This is almost possible today given the fact that any client can inspect the state of the cache using
.Cache().Table()
/.Cache().Table().Row()
APIs. However what would be really neat is if the cache could just be dumped and serialized to a string using aCache().Dump()
function. What would be even better than that is if libovsdb could run in "test mode" and generate deterministic UUIDs for items in the rows that have references to other models.Today the output of a test run could look like:
It would be cool if the generated object could look like:
The assertion of the database content would practically become trivial in that case.
The text was updated successfully, but these errors were encountered: