Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Draft] Introduce global conditions with support for fail_uncoverable (new condition) and should_panic (rework) #2532

Draft
wants to merge 15 commits into
base: main
Choose a base branch
from

Conversation

adpaco-aws
Copy link
Contributor

Description of changes:

In this draft PR we:

  • Introduce Global Conditions (currently being discussed in RFC: Global Conditions #2516)
  • Re-implement the should_panic feature as a global condition
  • Add support for a new fail_uncoverable condition

The PR has been opened to serve as a Proof-of-Concept for #2516 , therefore it's not recommended to review it unless the PR has been merged (I'll update the description when that happens).

Resolved issues:

Resolves #2299

Related RFC:

Optional #2516 , #2272 , #1905

Call-outs:

There are a few things to be done for this implementation. One thing I'm considering is moving all structs and logic related to global conditions to a new module. Another one is to convert the compute_<cond>_condition into associated functions of GlobalCondition.

Testing:

  • How is this change tested? New tests.

  • Is this a refactor change? No.

Checklist

  • Each commit message has a non-empty body, explaining why the change was made
  • Methods or procedures are documented
  • Regression or unit tests are included, or existing tests cover the modified code
  • My PR is restricted to a single feature or bugfix

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.

@adpaco-aws adpaco-aws requested a review from a team as a code owner June 15, 2023 18:50
@adpaco-aws adpaco-aws changed the title Introduce global conditions with support for fail_uncoverable (new condition) and should_panic (rework) [DRAFT] Introduce global conditions with support for fail_uncoverable (new condition) and should_panic (rework) Jun 15, 2023
@adpaco-aws adpaco-aws marked this pull request as draft June 15, 2023 18:51
@adpaco-aws adpaco-aws changed the title [DRAFT] Introduce global conditions with support for fail_uncoverable (new condition) and should_panic (rework) [Draft] Introduce global conditions with support for fail_uncoverable (new condition) and should_panic (rework) Jun 15, 2023
@adpaco-aws adpaco-aws mentioned this pull request Jun 19, 2023
4 tasks
@adpaco-aws adpaco-aws self-assigned this Jun 20, 2023
adpaco-aws added a commit that referenced this pull request Jan 12, 2024
…tions (#2967)

This PR is the next step to rework/introduce the
`should_panic`/`fail_uncoverable` options as global conditions.

Until now, we haven't had a concrete proposal to do so other than the
implementation in #2532. This PR presents one for each option in their
respective RFCs. I'd like to agree on this design before starting the
code review for #2532.

Related to #1905 #2272 #2299 #2516
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Status: In Progress
Development

Successfully merging this pull request may close these issues.

Option that causes verification to fail for uncoverable cover statements
1 participant