On Fri, Nov 7, 2025, at 7:39 AM, Jan Jasek wrote:
Hi Jeremy, I am talking about the history of runners for Integration tests. And if you want to share something, please give some context to it, not just blindly throw links.
Ivan and Akihiro removed testr support almost a decade ago. https://review.opendev.org/c/openstack/horizon/+/520214
Thank you Jan
On Fri, Nov 7, 2025 at 4:13 PM Jeremy Stanley <fungi@yuggoth.org> wrote:
On 2025-11-07 13:55:01 +0100 (+0100), Jan Jasek wrote: [...]
So the point is that as far as I know Horizon NEVER used stestr runner for Integration tests. At least from what I was able to find across old branches (feel free to correct me If I am wrong). I can try to find out why but stestr is not used and (at least majority time in Horizon history) was not used for integration tests. That is a fact.
Interesting. Going back to my statement on the value of understanding why prior decisions were made understanding why this is the case could be useful. If Horizon never used stestr in the first place then I don't know that we can blame it for instability of test cases for example. Maybe part of the issue here was deciding to go off piste in the first place? Or maybe there were really good reasons for these decisions (I know django is a large framework with lots of batteries included). At this point it is probably all moot. As I explained in my previous response, I suspect that pytest can largely meet the existing goals set in the PTI. I was trying to explain that there are real goals behind the decision to use stestr, that pytest is probably sufficient to address those goals, and if necessary goals can be updated to meet current needs or expectations. On top of that, if we don't have an understanding of our goals or how well existing tools meet those goals I don't know how we can evaluate if the current tools should be replaced by something else. Looking at historical decisions can be a useful activity for understanding that better.
Based on all your messages and comments, you are here much longer than me and you are part of this discussion so you obviously somehow participate on Horizon, so feel free to share here why stestr was never default runner for Integration tests (or send me where it was). I would really like to know and I was not here when those decisions were made.
I would have to look it up myself. I don't know if anyone knows why these specific actions were taken by Horizon at this point without digging through git logs, code reviews, or project meetings.
[...]
While I was never heavily involved in Horizon development, a quick grep through its Git history indicates Matthias introduced testr support a decade ago in https://review.opendev.org/c/openstack/horizon/+/255136 so that may be a good place to begin researching from. -- Jeremy Stanley