Uploaded image for project: 'stripes-testing'
  1. stripes-testing
  2. UITEST-11

Sort out the use of yarn.lock in ui-testing

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Closed (View Workflow)
    • Priority: P3
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
    • Template:

      Description

      There should not be a yarn.lock when building the Docker image of ui-testing for folio-testing.aws since we want the very latest at all times from npm-folioci.

      The yarn.lock should be generated and committed for static versions of ui-testing, meant for testing a specific platform build based on released versions only. Once that version of ui-testing is tagged, the yarn.lock should be removed.

      However there's a issue with the Docker build trying to move the yarn.lock and failing, because it's not there. Wayne's looking into that.

        TestRail: Results

          Attachments

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              nielserik Niels Erik Gilvad Nielsen
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 2 hours
                  2h

                    TestRail: Runs

                      TestRail: Cases