assertNoMessages() not working as expected
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Dashboard (Horizon) |
Expired
|
Undecided
|
Unassigned |
Bug Description
If you add self.assertNoMe
If we use instead self.assertNoMe
specifying a response ( https:/
My first instinct would be to make the response argument mandatory, in line with most (all?) assertions that need a response, though it'd be nice to first investigate how/why/if this used to work.
We use assertNoMessages() without an argument pretty much everywhere, but fixing them to add the argument doesn't seem to cause problems. There is one exception that appears due to the helper class handling rather than the test itself:
=======
ERROR: test_instance_log (openstack_
-------
Traceback (most recent call last):
File "/home/
return fn(self, *args, **kwargs)
File "/home/
self.
File "/home/
self.
File "/home/
elif hasattr(response, "context") and "messages" in response.context:
TypeError: argument of type 'NoneType' is not iterable
tags: | added: horizon-core unittest |
Changed in horizon: | |
assignee: | Julie Pichon (jpichon) → nobody |
Changed in horizon: | |
assignee: | nobody → utsav dusad (utsavdusad) |
Using self.assertNoMe ssages( ) seems to function fine for me on master, throwing an error as expected.