Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1690002 - React Snapshot test errors
Summary: React Snapshot test errors
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Other
Version: 6.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: John Mitsch
QA Contact: Peter Ondrejka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-18 15:04 UTC by Evgeni Golov
Modified: 2019-08-09 13:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-03-18 16:53:11 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 26390 0 None None None 2019-03-18 15:04:19 UTC

Description Evgeni Golov 2019-03-18 15:04:18 UTC
<pre>
Summary of all failing tests

FAIL webpack/scenes/Subscriptions/components/SubscriptionsTable/__tests__/SubscriptionTypeFormatter.test.js

  ● subscriptionTypeFormatter › renders link to a host


    expect(value).toMatchSnapshot()


    Received value does not match stored snapshot "subscriptionTypeFormatter renders link to a host 1".


    - Snapshot

    + Received


    @@ -1,11 +1,10 @@

      <td>

        <span>

          Guests of

           

          <Link

    -       replace={false}

            to="/content_hosts/83/"

          >

            host.example.com

          </Link>

        </span>


      29 |     const formatter = subscriptionTypeFormatter(null, data({ hypervisor: { name: 'host.example.com', id: 83 } }));

      30 | 

    > 31 |     expect(toJson(shallow(formatter))).toMatchSnapshot();

         |                                        ^

      32 |   });

      33 | });

      34 | 


      at toMatchSnapshot (webpack/scenes/Subscriptions/components/SubscriptionsTable/__tests__/SubscriptionTypeFormatter.test.js:31:40)

      at tryCatch (node_modules/regenerator-runtime/runtime.js:62:40)

      at GeneratorFunctionPrototype.invoke [as _invoke] (node_modules/regenerator-runtime/runtime.js:288:22)

      at GeneratorFunctionPrototype.prototype.(anonymous function) [as next] (node_modules/regenerator-runtime/runtime.js:114:21)

      at step (webpack/scenes/Subscriptions/components/SubscriptionsTable/__tests__/SubscriptionTypeFormatter.test.js:13:191)

      at webpack/scenes/Subscriptions/components/SubscriptionsTable/__tests__/SubscriptionTypeFormatter.test.js:13:437

      at Object.<anonymous> (webpack/scenes/Subscriptions/components/SubscriptionsTable/__tests__/SubscriptionTypeFormatter.test.js:13:99)


</pre>

Comment 1 Evgeni Golov 2019-03-18 15:04:21 UTC
Created from redmine issue https://projects.theforeman.org/issues/26390

Comment 2 Evgeni Golov 2019-03-18 15:04:24 UTC
Upstream bug assigned to jomitsch

Comment 5 Evgeni Golov 2019-03-18 16:53:11 UTC
this seems to have been auto-fixed in react itself :see_no_evil:


Note You need to log in before you can comment on or make changes to this bug.