Skip to content
This repository was archived by the owner on Jun 20, 2024. It is now read-only.
This repository was archived by the owner on Jun 20, 2024. It is now read-only.

Add model or property based e2e testing #69

Description

@shaspitz

Following integration of settlement layer devnet, an e2e testing framework should be introduced. There's a lot of flavors as to how this idea could be implemented. General idea is to apply high level actions to a system, and test the outcome of such actions against an expected system state. Few Different options:

  • System inputs w/ expected outputs can be encoded manually
  • Model based testing can be used to generate input/expected output traces that must satisfy a simplified model of the system (compatible with fuzz testing)
  • Property based testing can be used to generate i/o traces from properties/invariants defined for the system (compatible with fuzz testing)

Inspiration which I am familiar with:

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions