Skip to content
This repository was archived by the owner on May 4, 2024. It is now read-only.
This repository was archived by the owner on May 4, 2024. It is now read-only.

[Bug][Move CLI] move test crashes when --coverage is specified with no test cases being executed #968

@rahxephon89

Description

@rahxephon89
Collaborator

🐛 Bug

In the move cli, we can specify test cases to run by executing move test MODULE_TO_TEST. However, if there is no test to be executed, move cli will panic when the option --coverage is attached probably because no coverage trace file is generated.

To reproduce

Inside language/move-stdlib, executing move test 0x1::vector_tests --coverage will lead to panic with the error message:

thread 'main' panicked at 'Unable to open coverage trace file '"./.trace"'', .../language/tools/movecoverage/src/coverage_map.rs:67:33

Expected Behavior

Better error message instead of panic

Activity

rahxephon89

rahxephon89 commented on Mar 7, 2023

@rahxephon89
CollaboratorAuthor

Hi, @tnowacki @tzakian, I am wondering whether the panic described in this issue is intentional or not? If not, could you give me some direction on how to fix it? Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @rahxephon89

        Issue actions

          [Bug][Move CLI] move test crashes when --coverage is specified with no test cases being executed · Issue #968 · move-language/move