IIRC, the function was added based on user request. When that function was first added, the button read “Run Actions”, then it was reduced to “Run” but the function was unchanged.
There are a number of options:
If your primary goal is to test conditions, that can be done in the automation editor UI by using the “Test” function in their expansion menu.
Use the Services tool to run the automation.trigger service with skip_condition set to false:
Add another trigger (like a State trigger based on an Input button or some other helper). Once the testing is done just delete or disable the additional trigger. (This was the way it had to be done prior to the addition of the “Run Actions” function)