Skip to content

File structure refactor for tests #562

@Zacholme7

Description

@Zacholme7

Although I have an understanding of it now, going through and understanding the spec tests and how everything fits/works together was quite confusing.

I would propose keeping the top level p2p, qbft, ssv, and types directories to contain spec related code, but migrate everything testing related into a new tests directory.

Few picky nits that I think would help a lot in the readability of the code

  • I think some of the names should be tweaked so the directories and file names convey more meaning. For example, when navigating the repo at first it was confusing to see spectest/tests and also spectests/generate/tests.
  • I think all logic should be kept out of the generated directory. This should only contain the input json and state comparisons.
  • Quick off the head structure I think makes sense (sorry for bad formatting)

test/

  • qbft/
    • generated/
      • input_json/
      • state_comparison/
    • qbft-categories/
      • test categories here
    • all_tests.go
    • runner.go
    • generator.go
  • ... repeat for others
  • utils

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions