Uploaded image for project: 'Stripes'
  1. Stripes
  2. STRIPES-647

SPIKE: expose test utilities for import into modules.

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed (View Workflow)
    • Priority: P3
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Template:
    • Development Team:
      Stripes Force

      Description

      Currently interactors/test setup methods are only imported via direct file path to `stripes-*/etc/etc....`
      This requires a direct devDependecy on the 'stripes-*' module rather than 'stripes' which isn't what we want.
      They should not have to reach into the directory structure, but be able to import through stripes (or other easy means)
      Test utilities should not end up in the production bundle (filtered out? tree shook?)

      An approach might be to set a particular webpack entry point based on a `process.env` variable (test?) in stripes-core

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                Unassigned Unassigned
                Reporter:
                JohnC John Coburn
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases