Skip to content

AAC: Do we need a flag to discriminate valid transactions in input? #6577

@fdefelici

Description

@fdefelici

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

No one assigned

    Labels

    aacAvoiding Accidental Consensusaac-testingAvoiding Accidental Consensus Testing Specific Task

    Type

    Projects

    Status

    Status: 🆕 New

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions