Bug #20122
Fix tests for sprockets-rails 3.x
Difficulty:
Triaged:
Yes
Description
One of the tests for the Docker container, is checking for the exact path of an asset. On sprockets 3.x, the exact path of the asset is no longer going to work, as even tests will use digests. The test can simply match on the asset name (finding the digest and testing for the full path would be possible but probably overkill).
Associated revisions
Refs #20122 - Match container JS file with digest
History
#1
Updated by The Foreman Bot almost 5 years ago
Updated by - Status changed from New to Ready For Testing
- Assignee set to Daniel Lobato Garcia
- Pull request https://github.com/Katello/katello/pull/6841 added
#2
Updated by Eric Helms almost 5 years ago
Updated by - Legacy Backlogs Release (now unused) set to 250
#3
Updated by The Foreman Bot almost 5 years ago
- Pull request https://github.com/Katello/katello/pull/6846 added
#4
Updated by Anonymous almost 5 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset katello|0845021d7bd08d7ab0ccf43f5912a96bde649abc.
Fixes #20122 - Fix tests for sprockets-rails 3.x
One of the tests for the Docker container, is checking for the exact
path of an asset. On sprockets 3.x, the exact path of the asset is no
longer going to work, as even tests will use digests. The test can
simply match on the asset name (finding the digest and testing for the
full path would be possible but probably overkill).