Skip to content

Awesome testing experience #1971

Description

@anderseknert

This is the main issue collecting the work that needs to be done in Regal in order to provide Rego developers the best possible experience for testing their policies. The goal is to make it obvious how to:

  • Create new tests from your editor based on what you're working on
  • How to run tests and evaluate the results
  • How to find the cause of failing tests
  • Tune details like coverage, thresholds, and so on

This will be accomplished in part by improving existing functionality — like templating — and in part by providing a new API in Regal's language server that editors can interact with. Our main point of integration (and thus our measure of "success") for this story is the OPA VS Code extension. Integrating other editors is certainly top of mind, but contrary to the language server protocol there isn't a unified standard for how to collect and evaluate tests in editors, so in order to keep the scope reasonably sized, our focus will be VS Code for now, and later issues will be made for e.g. JetBrains or Playground integrations.

Also intentionally leaving out benchmarking from this as that deserves a separate "epic".

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