Uploaded image for project: 'Red Hat Decision Manager'
  1. Red Hat Decision Manager
  2. RHDM-1129

Optaweb Vehicle Routing tests fail due to different versions of dependencies

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • 7.7.0.GA
    • 7.5.0.GA
    • Build and Assembly
    • None
    • Release Notes
    • CR1
    • CR1
    • Hide
      Optaweb Vehicle Routing was distributed with incorrect package-lock.json file. As a result, snapshot tests of optaweb-vehicle-routing-frontend module fail due to change in html code generated by different versions of dependencies.
      Change directory to optaweb-vehicle-routing-frontend module. Run "npm install" to download dependencies. then, run tests via "npm test" and when they finish, press u to update failing snapshots.
      Show
      Optaweb Vehicle Routing was distributed with incorrect package-lock.json file. As a result, snapshot tests of optaweb-vehicle-routing-frontend module fail due to change in html code generated by different versions of dependencies. Change directory to optaweb-vehicle-routing-frontend module. Run "npm install" to download dependencies. then, run tests via "npm test" and when they finish, press u to update failing snapshots.
    • Hide

      download and unpack reference-implementation.zip
      unpack the optaweb-vehicle-routing
      cd sources/optaweb-vehicle-routing-frontend
      npm install
      npm test

      Show
      download and unpack reference-implementation.zip unpack the optaweb-vehicle-routing cd sources/optaweb-vehicle-routing-frontend npm install npm test

    Description

      As package-lock.json is removed and a new one generated during the PNC build, it contains different versions of dependencies compared to upstream. Some of these (eventually patternfly, to name one) are not backward compatible on the level of generated html code. As a result, some snapshot tests fail if being run on product sources.

      Another side effect is that the newly generated package-lock.json refers to an internal Red Hat environment by starting every dependency's URL with:
      "http://indy.newcastle.svc.cluster.local/api/folo/track/build-32731". This is an unnecessary exposure of information about internal infrastructure.

      Attachments

        Issue Links

          relates to

          Task - Represents a small unit of work that is not end-user facing. RHPAM-2199 NPM dependencies: Use only fixed version in package.json files

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              emingora Enrique Mingorance Cano
              rsynek@redhat.com Radovan Synek
              Radovan Synek Radovan Synek
              Radovan Synek Radovan Synek
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: