Skip to content

Common library package for E2E tests #439

Description

@vallq

@vallq @koonpeng Many of the functionalities that are used in this package are also used in the dashboard-e2e. Does anyone have any suggestions not to repeat this code? any ideas:

  • Place the e2e-dashboard and e2e-reporting under an e2e folder?
  • Create an additional package as a common factor to use in these two packages?

I prefer a common lib package. Some build systems like react scripts are known to complain when trying to import a module outside of the root source dir.

Originally posted by @koonpeng in #417 (comment)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions