)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"fb44bf5f04125661e25441ba314a42aa573967ca","unresolved":false,"context_lines":[{"line_number":11,"context_line":"before the rules in tempest around changing api responses became more"},{"line_number":12,"context_line":"stringent and thus to facilitate a breaking api change 2 checks were"},{"line_number":13,"context_line":"added. However, we should only except the current expected error code"},{"line_number":14,"context_line":"as valid to prevent the invalid behavior from slipping back."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"Change-Id: Ia5d46163fc1f52d5bc4a9296b8d1e5692d09fc71"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"9aa7fdbe_7c4d8999","line":14,"updated":"2014-10-28 06:17:13.000000000","message":"I agree with the above comment, we need to avoid slipping back.\n\nThis topic should be restrict in negative tests because API Change guideline[1] allows error status code changes only.\nI feel negative tests need to be moved from Tempest into each project repo because these cases are handled at the face of each REST API and they don\u0027t seem integrated tests. I don\u0027t think we need to take much time for these tests on the gate for all projects..\n\nI don\u0027t have quick solution idea for this topic, and maybe we need to move forward with tempest-lib for negative tests also.\n\n[1]: https://wiki.openstack.org/wiki/APIChangeGuidelines#Generally_Considered_OK\n\n Changing an error response code to be more accurate","commit_id":"38b8bf19e628aa36c1179f5fac8b47960847a8d7"}]}