Skip to content

Come up with an overall design for Babel Validation #65

@gaurav

Description

@gaurav

I would like to see Babel Validation have three legs:

  • A pytest test suite that can be used to test NodeNorm and NameRes.
    • Extend this to include GitHub issue-based tests.
    • Provide CLI tools for testing all/individual issues.
  • A GitHub Action suite that runs regularly (weekly? daily?) to run the pytest suite and provides responses
    • Ideally, these reports will flow back into this repository for tracking somehow -- maybe have a GitHub Action that generates a high-level category-based report, compare that to the previous report, and then generate a PR to update it if it's changed.
  • A web frontend that collects the tools that will:
    • Allow you to run some parts of the test suite from JavaScript.
    • Help triage and manage the issues across all four Babel repos (Babel, NodeNorm, NameRes, Babel Validation)
    • Include other tools that can be useful (e.g. Autocomplete with NameRes)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions