We need a functional test for chain-data validation.
chain-data would be any kind of data that appear on the chain itself and we have to validate it.
For the developer, isnt easy testing new features while making changes on floresta-chain and is to break something there.
The unit test include some checks on how we do validation but it passes bugs like
#198 (comment)
#198 (comment)
Which we can easily check by running and validating some blocks, but in this approach or you wait 10 minutes for a block to end up in your running floresta build or you can make the ibd which is not as easy that can be with an automated functional test for it.
The test can be some pre-selected blocks and we try to validate them making sure to catch every aspect of validation and asserting it with a bitcoin node validating the same blocks.
This will make sure that our implementation will validate the same blocks that bitcoin core validates.
We need a functional test for chain-data validation.
chain-data would be any kind of data that appear on the chain itself and we have to validate it.
For the developer, isnt easy testing new features while making changes on floresta-chain and is to break something there.
The unit test include some checks on how we do validation but it passes bugs like
#198 (comment)
#198 (comment)
Which we can easily check by running and validating some blocks, but in this approach or you wait 10 minutes for a block to end up in your running floresta build or you can make the ibd which is not as easy that can be with an automated functional test for it.
The test can be some pre-selected blocks and we try to validate them making sure to catch every aspect of validation and asserting it with a bitcoin node validating the same blocks.
This will make sure that our implementation will validate the same blocks that bitcoin core validates.