Programmatically activating widget?

[dbr]

Background

I am looking to write some unit tests for an imgui based application.

Say I have a window with some text inputs, and a "create" button. It all works, but I want to write a unit that verifies when the button is pressed that the desired action occurs.

The immediate mode methodology makes it trivially easy to pre-fill the form with my test input strings, but I'm not sure how I'd go about setting the "button id ##example has been pressed" state.

I could add additional variables to allow triggering the button being pressed, e.g

if simulate_button_click || ui.button(...) {

as discussed in #966 but I would rather not, as it clutters up the code just for testing (which adds more potential for errors)

Main question

At the end of the discussion #966 (comment) there was a comment saying

Note that there are plan for a new API to programmatically activate widgets based on their ID, but that won't be ready short-term.

I am wondering if this has come to existence yet? I had a search around and couldn't find any further mention of it (but it's a slightly hard thing to know the search terms for!)

Followup ideas

I'm imagining something very vaguely along the lines of this

let ui = imgui_context.frame();
my_widget.example_input = "test";
my_widget.render(&ui);
...
imgui_context.set_element_active("##example", true);
let ui = imgui_context.frame();
my_widget.render(&ui);
assert!(my_widget.other_thing == "button was clicked an value was test";

I'm using the imgui-rs bindings, not sure how exactly that'd translate to the original C++, but should give a rough idea as pseudo code - basically on next query I want the element with that ID to be as if the user clicked on it

My other thought was I could determine the button location and simulate a mouse click (by moving the cursor position to there and setting the mouse button as down) - this might actually be a better way to go since it exactly what I'm wanting to test, just the implementation is slightly more complex

[ocornut]

There is such an automation system see #435 but it hasn’t been made public.

[ghost]

@ocornut is there any update on the automation framework? Any ETA for when it will be made public?

[ocornut]

This is still being tested/iterated with selected partners and sponsors. We’re working on a license and expect to release it publicly between Q2 and Q3.

[dbr]

Most likely done via #435 🥳

[ocornut]

Yes as per your specific need Test Engine should ideally be the answer.
But I’ll reopen this issue as - and given the specific wording used in issue title - I want to also finish implementing API to do things like from dear imgui API point of view too.