Skip to content

Rust evaluator panics when a test definition returns a non-boolean value #1941

@beu5a

Description

@beu5a

quint test selects test candidates by name:

  • by default any definition ending in Test
  • any definition matching the --match regex if provided.

The TypeScript evaluator handles non-boolean results gracefully by marking them as ignored.
The Rust evaluator panics instead:

  error: [QNT516] Rust evaluator exited with code 101
  thread 'main' panicked at src/value.rs:486:18:
  Expected boolean

To reproduce:

quint test examples/language-features/counters.qnt
The file contains:

  // this is just a value, and it should be ignored as a test
  val ignoredTest = 1

The Rust evaluator should ignore non-boolean results or gracefully handle the error.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions