Skip to content

Spec Editor integration #105

@PilchardFriendly

Description

@PilchardFriendly

Hi - I'm using spec inside VSCode via spago. I'm very happy with how its worked so far.

My "micro-movements" are now from 'failing test output' to 'test' to 'source code'.

For this, I was thinking of trying to add the failing test location (file/linenumber) to some json that an extension in VSCode could parse.

Maybe you've seen something that can do this?

As a start, I don't think line-number/filename are preserved in the Spec Tree. What would it take to make that available as meta-data on the spec and input into the reporter?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions