)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":8648,"name":"Radomir Dopieralski","email":"openstack@dopieralski.pl","username":"thesheep"},"change_message_id":"7dd7c5df1b50bcdc3e09cb8cc7b2a2e85acbb17b","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"1ab2f747_01d41195","updated":"2025-10-27 15:29:56.000000000","message":"I think there is a bit of a confusion. We are only removing the old integration tests from Horizon, not all integration tests entirely. They have been replaced with pytest-based tests, which still require selenium and xvfbwrapper. You probably will want to write your integration tests the same way the new integration tests in Manila-UI are written: https://review.opendev.org/c/openstack/manila-ui/+/961503","commit_id":"fdbd6ac68876a065e10d99761de9c2290bba7f75"},{"author":{"_account_id":8648,"name":"Radomir Dopieralski","email":"openstack@dopieralski.pl","username":"thesheep"},"change_message_id":"43e328bed55ee05106f4e83e668f714f1f4a9236","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"28cd2c90_d9834f9f","updated":"2025-10-28 14:35:46.000000000","message":"We are reverting that patch on Horizon side, so there is no reason to merge this yet.","commit_id":"fdbd6ac68876a065e10d99761de9c2290bba7f75"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"966f3bad0151ec3bbd6c2e65ca16b822fb434b12","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"aae8760a_afb40550","in_reply_to":"1ab2f747_01d41195","updated":"2025-11-03 14:25:04.000000000","message":"pytest is not approved for use under the pti and horizon is not actully allow to use it today.\n\nhow that is technially a serpate topic form this removeal but currently i see that as a blocker to using the new integration testing framework that horizon has built since 2023.\n\nchandan is starting a topic with the tc about potitally adding pytest to the allowed testign runtime that can be used for writing test.\n\neven if that is adopted i see the introduction fo pytest in watcher-dashboard when all other testing in watcher deliverables as problematic.\n\nits not nessically a blocker but it shoudl not be done lightly.\n\nunlike the standard lib unittest moduel which is mandated by the pti the use of selenium is not and i also question fi that is an approate tool to build integration test with in 2025.\n\nit was the defcto tool when horizon was first created by there are other althernitives that we shoudl consider in 2025 such as python-playwright\n\ni am not sold on either framework today but  given the minimal nofucntional coverage we have today that does not run in ci im thinking it best to start form frist principals and build up new integration test coverge then try and adapt the xisting test taht we know done currently work.","commit_id":"fdbd6ac68876a065e10d99761de9c2290bba7f75"}]}