You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With PR #131, we now have tooling (and test cases) for the last CEL specification. (Thanks @hudlow and @stefanvanburen for doing so much work on this.)
This means we "simply" have a long list of @wip test cases.
The fourth of the sub-issues starts with triage of nearly 1200 new test cases into at least three categories: won't fix, hard-to-fix, and easy-to-fix. I'm going to open a discussion on @wip tests, to avoid cluttering this issue with a lot of digressions unrelated to the core four sub-issues.
With PR #191, we now have tooling to help analyze the @wip test cases that provide specific scenarios that are in the CEL specification, but excluded from the acceptance test case. We can now easily put the 1200 test cases into a Notebook and start slicing and dicing them to work out why they don't pass and what changes are required.
With PR #174, we have a git.log in the features directory showing the last 5 changes to the CEL-spec that was fetched. This provides some visibility into the release of the CEL-spec being tested against. Incorporating this into the README (and perhaps the help output from the CLI) must be done manually, as the @wip tags are removed.
Activity
slott56 commentedon Oct 1, 2025
With PR #131, we now have tooling (and test cases) for the last CEL specification. (Thanks @hudlow and @stefanvanburen for doing so much work on this.)
This means we "simply" have a long list of @wip test cases.
The fourth of the sub-issues starts with triage of nearly 1200 new test cases into at least three categories: won't fix, hard-to-fix, and easy-to-fix. I'm going to open a discussion on @wip tests, to avoid cluttering this issue with a lot of digressions unrelated to the core four sub-issues.
slott56 commentedon Jul 6, 2026
With PR #191, we now have tooling to help analyze the
@wiptest cases that provide specific scenarios that are in the CEL specification, but excluded from the acceptance test case. We can now easily put the 1200 test cases into a Notebook and start slicing and dicing them to work out why they don't pass and what changes are required.slott56 commentedon Jul 6, 2026
With PR #174, we have a
git.login the features directory showing the last 5 changes to the CEL-spec that was fetched. This provides some visibility into the release of the CEL-spec being tested against. Incorporating this into theREADME(and perhaps the help output from the CLI) must be done manually, as the@wiptags are removed.