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
actually, to fully cover the complete interface the database table classes expose, the 2 test functions we currently have per database table are not enough, but we additionally need
note that while all DB classes already have a marshal function (and this function is indeed used in eg the xbrnetwork backend or the market maker), this is not covered by tests, and eg inconsistent types had been a practical headache already
also note, the User.parse class function, which is lacking from most of the other DB classes, but should be there, because it is the "inverse" of marshal
So it seems all our current tests are centered around the fbs variants of things (apart from the tests you linked above) because our database schema classes are from flatbuffers. We'd first need to write schema classes that are cbor-able.
all our DB classes need to have "marshal" and "parse", so yes, adding those is part A of this issue. part B is then adding the tests using the new functions (and the existings fbs ones) ..
actually, to fully cover the complete interface the database table classes expose, the 2 test functions we currently have per database table are not enough, but we additionally need
like for example here https://github.com/crossbario/cfxdb/blob/master/cfxdb/tests/test_user.py
The text was updated successfully, but these errors were encountered: