)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":8576,"name":"Yair Fried","email":"yfried@redhat.com","username":"yfried"},"change_message_id":"64bdf3aa1c926c1c9bb6a76007844de15fa9f47f","unresolved":false,"context_lines":[{"line_number":4,"context_line":"Commit:     Miguel Lavalle \u003cmiguel@mlavalle.com\u003e"},{"line_number":5,"context_line":"CommitDate: 2014-05-26 17:18:16 -0500"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Add spec for bp:neutron-scenario-tests"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"Increase the number of scenario tests for Neutron"},{"line_number":10,"context_line":""}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"3ae8d1ca_80761a3d","line":7,"updated":"2014-05-27 19:12:03.000000000","message":"there\u0027s an old bp for roughly the same subject\nhttps://blueprints.launchpad.net/tempest/+spec/neutron-advanced-scenarios\neither close the old one, or expand it, but we shouldn\u0027t have both of them open","commit_id":"d589c1bbcc24c37c8130f8fe67650dff12a3ab54"}],"specs/neutron-scenario-tests.rst":[{"author":{"_account_id":8576,"name":"Yair Fried","email":"yfried@redhat.com","username":"yfried"},"change_message_id":"75053c3f804a7932b7d124b1d2c2ec42ce5664b8","unresolved":false,"context_lines":[{"line_number":34,"context_line":""},{"line_number":35,"context_line":"#. A \"How to develop scenario tests for Neutron\" tutorial will be developed as"},{"line_number":36,"context_line":"   an extension to the `Tempest documentation"},{"line_number":37,"context_line":"   \u003chttp://docs.openstack.org/developer/tempest/field_guide/scenario.html\u003e`_."},{"line_number":38,"context_line":"#. A set of scenario tests will be well specified taking as a starting point"},{"line_number":39,"context_line":"   the result of the design summit in Atlanta and captured at "},{"line_number":40,"context_line":"   `Atlanta design summit "}],"source_content_type":"text/x-rst","patch_set":1,"id":"3ae8d1ca_e0043e17","line":37,"updated":"2014-05-27 19:04:47.000000000","message":"Such tutorial should include strict guidelines for\n1. documentation - each test is unique, and complex operations will most likely be enclosed in supporting methods or shared between modules, so documentation should provide sufficient information about the test for people outside the tempest or neutron effort (hopefully even for \"simple\" users who will use tempest to test their deployment)\n2. logging - test run should log test operation in details so it is clear from log what operations and achievements took place prior to failure","commit_id":"d589c1bbcc24c37c8130f8fe67650dff12a3ab54"},{"author":{"_account_id":8576,"name":"Yair Fried","email":"yfried@redhat.com","username":"yfried"},"change_message_id":"75053c3f804a7932b7d124b1d2c2ec42ce5664b8","unresolved":false,"context_lines":[{"line_number":52,"context_line":"      Tempest cores."},{"line_number":53,"context_line":"    * Progress will be discussed at the Neutron and Tempest weekly IRC"},{"line_number":54,"context_line":"      meetings."},{"line_number":55,"context_line":""},{"line_number":56,"context_line":"The tests developed as result of this process will reside in the tempest tree"},{"line_number":57,"context_line":"hierarchy at tempest/scenario"},{"line_number":58,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"3ae8d1ca_3adbb41c","line":55,"updated":"2014-05-27 19:04:47.000000000","message":"Assign owners to tests.\nOwner should be in charge of maintaining the code, debug future failures, and enhancing code documentation and logging (for existing modules), as well as providing reasonable support for relevant questions (though adequate doc should minimize such questions), thus easing new contributors into the fold.","commit_id":"d589c1bbcc24c37c8130f8fe67650dff12a3ab54"}]}