Uploaded image for project: 'Red Hat 3scale API Management'
  1. Red Hat 3scale API Management
  2. THREESCALE-10219

Consistent cucumber failing on nightly Postgres/Oracle: message outbox

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • System
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started

      Example of failure: https://app.circleci.com/pipelines/github/3scale/porta/26145/workflows/084cc2a2-8bc8-4ea5-bd92-485cf2eb03d2/jobs/294150

       

       

      (::) failed steps (::)expected "/p/admin/messages/outbox/102" to equal "/p/admin/messages/outbox/103" (Capybara::ExpectationNotMet)
      /opt/app-root/src/project/vendor/bundle/ruby/2.7.0/gems/capybara-3.35.3/lib/capybara/session/matchers.rb:24:in `block in assert_current_path'
      
      Failing Scenarios:
      cucumber -p ci features/provider/admin/messages/outbox.feature:43 # Scenario: Reading a message 

       

      Dev notes

      This fails because instead of using a comparison m.subject ==  in the `#find` block it is using an assignment m.subject=

              Unassigned Unassigned
              ramihery Hery Ramihajamalala (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: