Skip to content

Make all tested opcodes validate on multiple addresses? #13

@superfury

Description

@superfury

Could you perhaps modify the tests for the various opcodes that can use memory operands to test on multiple (at least 2 different) memory addresses? That way it can make sure that the opcodes are actually operating on their memory operands as intended (and not applying on some kind of buffered address that's changed by a previous opcode)?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions