Extend BasicOrchardFeaturesTestingUITestContextExtensions

Don't put all the code into the same class though

@Piedone Do you mean to put these new methods in a new ...Extensions file?

It's up to you how to structure the code, just let's not make that class perpetually longer.

What do you think, should we also test the creation itself of the workflow, so clicking trough each step, creating the event and the task, or creating it from a recipe is enough? Then testing the workflow of course.

Because I think clicking it together could be problematic during the part where you have to connect the event with the task:

We need to test that the workflow editor also works, yes, that's why I mentioned adding an Event and a Task. Drag and drop is possible in Selenium, so that step should not be an issue either. See e.g. https://www.browserstack.com/guide/drag-and-drop-in-selenium for inspiration (this is Java, but the API is the same).