Test vectors
Opened this issue · 1 comments
Discussed in https://github.com/orgs/LNP-BP/discussions/131
Originally posted by cryptoquick October 5, 2022
It would really help in development to have a set of test vectors to verify certain activities such as minting, transfers, secondary transfers, and other more complex scenarios, especially as functionality is expanded. This way improvements can be made without compromising fundamental functionality. It would also help test certain assumptions made during development, and speed up review.
If something like this desired, where should these test vectors be made, and how should they work? Ideally the nodes and their methods could be tested in an ephemeral context, without necessarily needing to make shell commands.
To make this work easier, maybe embeddable API equivalents to the cli commands that make calls to microservices over zmq could be made available as a single, unified crate. This would make it easier to make calls to test functionality within Rust tests.
What do people think? Would this work be useful or necessary?
I think this is highly required - but it is better to wait for v0.10 since otherwise all these test vectors would be broken