-
Notifications
You must be signed in to change notification settings - Fork 709
Open
Labels
aacAvoiding Accidental ConsensusAvoiding Accidental Consensusaac-testingAvoiding Accidental Consensus Testing Specific TaskAvoiding Accidental Consensus Testing Specific Task
Description
We should assess whether our testing logic requires introducing a flag (for example, a boolean) to specify the expected behavior of a transaction (whether it should be valid or invalid) when passed as a test input.
If we decide that this is necessary, we could also add a similar flag to the input block. This would allow us to:
- Explicitly define in the test the expected final result for that block.
- Reuse the flag to perform MARF computations only for blocks that are expected to succeed (restoring the original implementation based on the expected failure field before applying
insta
)
Alternatively, could we infer this behavior by inspecting the flags of all input transactions?!
Metadata
Metadata
Assignees
Labels
aacAvoiding Accidental ConsensusAvoiding Accidental Consensusaac-testingAvoiding Accidental Consensus Testing Specific TaskAvoiding Accidental Consensus Testing Specific Task
Type
Projects
Status
Status: 🆕 New