In Growing object-oriented software guided by tests they use a java library called Window Licker to pilot a gui running in test thread. Next time I started a new project, I wanted to apply the techniques I had learned in the book. As the project was in C#, I searched for a C# equivalent of Window Licker. I did not find any, but it turned out to be really simple to create an equivalent.
Here is the user test code I wanted to be able to write (inside a SpecFlow step) :
public void GivenTheUserEntersHisEmail(string email)
Here UserForm is an extension method I added to the ScenarioContext that is responsible for returning the current user form.
As you have noticed, the various gui components must be exposed through some kind of public api. What I did was to expose the main gui window as a property on the application top level object, and then have properties to access all the sub windows and the controls that the tests needed to access. It kind of breaks encapsulation, but it allows to keep the tests working during refactoring !
Eventually, I had to write the User class, and it turned out to be really simple :
static class User
internal static void Enters(TextBox textBox, string text)
textBox.Invoke(new MethodInvoker(() => textBox.Text = text));
That’s it, all that was needed was to ask the thread of the control to update the text !