In the codebase, we have many places where we try to generate different types of transactions with different inputs and see that we can serialize/deserialize them properly.
Instead of doing that manually we can use the proptest framework to generate transactions.
In the codebase, we have many places where we try to generate different types of transactions with different inputs and see that we can serialize/deserialize them properly.
Instead of doing that manually we can use the
proptestframework to generate transactions.https://github.com/FuelLabs/fuel-vm/pull/707#discussion_r1556474574 https://github.com/FuelLabs/fuel-vm/pull/707#discussion_r1556478293 https://github.com/FuelLabs/fuel-vm/pull/707#discussion_r1556562692 https://github.com/FuelLabs/fuel-vm/pull/707#discussion_r1556599596
We have this problem for each type of transaction, so it should be a huge refactoring of all tests related to serialization and deserialization.