)]}'
{"doc/source/devref/functional_testing.rst":[{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"ab763015f9a65b18c8b968bab7b14b1b7aaef41c","unresolved":false,"context_lines":[{"line_number":18,"context_line":"Functional Testing"},{"line_number":19,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":20,"context_line":""},{"line_number":21,"context_line":"Functional tests are currently run in two gates using the tempest plugin"},{"line_number":22,"context_line":"available under ``keystone_tempest_plugin``."},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"- gate1 - is voting and exposes both the v2 and v3 endpoint."}],"source_content_type":"text/x-rst","patch_set":1,"id":"1a1ced50_af48f48b","line":21,"updated":"2017-03-23 18:32:17.000000000","message":"This could go into even greater detail about what keystone thinks functional testing is. For example, how does this differ from the functional-like tests we have in the keystone/tests/unit/test_v3_*.py modules. That might be a great way to set the stage for the rest of the document.","commit_id":"3f2abbe7d081758a605e11568a4fcacbc71e6091"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"ab763015f9a65b18c8b968bab7b14b1b7aaef41c","unresolved":false,"context_lines":[{"line_number":21,"context_line":"Functional tests are currently run in two gates using the tempest plugin"},{"line_number":22,"context_line":"available under ``keystone_tempest_plugin``."},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"- gate1 - is voting and exposes both the v2 and v3 endpoint."},{"line_number":25,"context_line":"- gate2 - is non-voting and exposes only the v3 endpoint, but additionally,"},{"line_number":26,"context_line":"  it runs federation tests."},{"line_number":27,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"1a1ced50_8f1c18c3","line":24,"updated":"2017-03-23 18:32:17.000000000","message":"For the sake of readability, the two items in this list could be consolidated in to the above paragraph.\n\n  ... available under `keystone_tempest_plugin`. The first is a voting\n  job that exposes both the v2 and v3 endpoint (more details can be\n  elaborated on here). The second is a non-voting job that exposes only\n  the v3 endpoint, but takes additional steps to setup things required for\n  federated workflows in order to run federated test cases (more details\n  can be elaborated on here).","commit_id":"3f2abbe7d081758a605e11568a4fcacbc71e6091"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"ab763015f9a65b18c8b968bab7b14b1b7aaef41c","unresolved":false,"context_lines":[{"line_number":29,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":30,"context_line":""},{"line_number":31,"context_line":"To help with automating an appropriate environment on which to run functional"},{"line_number":32,"context_line":"tests, keystone provides a Devstack plugin."},{"line_number":33,"context_line":""},{"line_number":34,"context_line":"As of right now, the plugin only supports setting up and environment with"},{"line_number":35,"context_line":"federation and keystone as a service provider, but more features are to"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1a1ced50_0feca88e","line":32,"updated":"2017-03-23 18:32:17.000000000","message":"This is a great place to explain the role of the devstack plugin. For example, it could say that the whole purpose of the devstack plugin is to give the maintainers of the project the flexibility to setup keystone in specific ways before testing (using hooks from devstack, etc..).\n\nAs a developer reading the document, it gives me an idea of why this devstack thing exists within keystone, why I should use it, and when its usage is appropriate.\n\nIt could also describe when in the functional testing process I need to contribute to the devstack plugin. For example, if I want to develop some new tests for a new thing, my first step might be to contribute to the devstack plugin that adds functionality for the new thing. Then my next step would be writing tests, but those live somewhere else, etc..","commit_id":"3f2abbe7d081758a605e11568a4fcacbc71e6091"}]}