assertEqual is used incorrectly

Bug #1551861 reported by Gábor Antal
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
watcher
Fix Released
Wishlist
Gábor Antal

Bug Description

in several places in the test, assertEqual method is used:
  assertEqual(observed, expected)
However it should be:
  assertEqual(expected, observed)

Changed in watcher:
assignee: nobody → Gábor Antal (gabor.antal)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to watcher (master)

Fix proposed to branch: master
Review: https://review.openstack.org/286722

Changed in watcher:
status: New → In Progress
Changed in watcher:
importance: Undecided → Wishlist
Changed in watcher:
milestone: none → mitaka-rc-final
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to watcher (master)

Reviewed: https://review.openstack.org/286722
Committed: https://git.openstack.org/cgit/openstack/watcher/commit/?id=c440cdd69fa536fe1f0ac374e41849a0559b2714
Submitter: Jenkins
Branch: master

commit c440cdd69fa536fe1f0ac374e41849a0559b2714
Author: Gábor Antal <email address hidden>
Date: Tue Mar 1 18:14:05 2016 +0100

    Fixed wrongly used assertEqual method

    In several places, assertEqual is used the following way:
      assertEqual(observed, expected)
    However, the correct way to use assertEqual is:
      assertEqual(expected, observed)

    Change-Id: I5a7442f4adf98bf7bc73cef1d17d20da39d9a7f8
    Closes-Bug: #1551861

Changed in watcher:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.