Different patterns for ussage of method 'expected_success'
Bug #1354389 reported by
Timur Nurlygayanov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tempest |
Fix Released
|
Low
|
Timur Nurlygayanov |
Bug Description
We have common method 'expected_success' which allows to check the status code from responces.
But we can see that we have many tests in tempest, where we use this method with incorect arguments - we use resp instead of resp.status in arguments and in the result we will see that this method will do not check status code, when we use resp instead of resp.status:
https:/
summary: |
- Different patterns for ussage of method ' + Different patterns for ussage of method 'expected_success' |
Changed in tempest: | |
importance: | Undecided → Low |
To post a comment you must log in.
root@comp: ~/tempest# grep -e "resp)" -r ./ | grep expected_success services/ compute/ xml/images_ client. py: self.expected_ success( 200, resp) services/ compute/ json/images_ client. py: self.expected_ success( 200, resp) services/ orchestration/ json/orchestrat ion_client. py: self.expected_ success( 200, resp) services/ orchestration/ json/orchestrat ion_client. py: self.expected_ success( 200, resp) services/ orchestration/ json/orchestrat ion_client. py: self.expected_ success( 204, resp) services/ orchestration/ json/orchestrat ion_client. py: self.expected_ success( 200, resp) services/ orchestration/ json/orchestrat ion_client. py: self.expected_ success( 200, resp) services/ orchestration/ json/orchestrat ion_client. py: self.expected_ success( 200, resp) services/ orchestration/ json/orchestrat ion_client. py: self.expected_ success( 200, resp) services/ orchestration/ json/orchestrat ion_client. py: self.expected_ success( 200, resp) services/ orchestration/ json/orchestrat ion_client. py: self.expected_ success( 204, resp)
./tempest/
./tempest/
./tempest/
./tempest/
./tempest/
./tempest/
./tempest/
./tempest/
./tempest/
./tempest/
./tempest/