Is it possible to expose manual encoding functions as general steps?

Question

We are studying a coded user interface, and since we have experience in coding in C #, we will code automated tests ourselves.

I already know that it is possible to have a test case with certain testing steps. Each test step is actually a function within the test method, and the description comes from a summary.

This is a great way for C # coders to expose what they are doing with non-encoding testers that will interact with these automated tests using MTM (Microsoft test manager).

However, it would be great if C # encoders could create common functions like “Steps”, and thus non-technical testers could build new tests in MTM using these building blocks.

Functions such as: Open the settings dialog, Maximize the window, Add an item (with parameters), Close all open tabs, etc.

However, these would be encoded functions, not records.

The idea would be that after creating and saving these functions in TFS (again in the form of general steps), the tester will be able to use these functions as building blocks for more automated tests.

I must also emphasize that these functions will be fully automated, so the new tests compiled in MTM should also be fully automated without having to open Visual Studio.

Is it possible?

Answer 1

The approach used by some people is to create a test structure that contains many useful features. The test itself is then recorded as a user-coded UI test, each step of which is a single record from a data source. (Typically, each step can be one line in the CSV file.) Some columns of the data source will be commands and other data for these commands.

Commands can be relatively low-level, such as: find a window, go to a page, launch an application, find a control in a window, enter text in a field, click a button or link, make sure that the field contains a given line.

Commands can be for higher-level actions in your applications, such as: login, form filling.

The framework may allow non-code machines to write tests using terminology that they understand. Structures are difficult to write.

Answer 2

This is really not possible in the way you ask - you cannot have your non-technical testers create automated tests with the test manager. A coded UI test must always exist as a test in a code file.

All the details of the test manager test are available through the TFS API, so I suppose it should be possible to create your own layer that could generate coded user interface based on a common step matching system, but it would be a fairly large enterprise - its probably it’s easier to have automated tests created by technical people.