Skip to content

cli: Reenable chromedriver test #822

Open
@straker

Description

@straker

As part of the conversion to npm workspaces we had to skip the chromedriver path test since where the node_modules directory is installed locally changed (moved up to the root). Need to figure out the proper way to test it while in local and while published.

Related: #793

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions