Summary
In response to the problem raised at the beginning of this chapter and for any similar matters in the future, we have seen how to transition from simple record and playback tests to data-driven architecture by releasing the test from the hardcoded values and binding its input to various types of data sources. On one hand, the binding was demonstrated for simple UI controls which already expose a readymade property, and on the other hand for more complex UI controls where the binding had to be customized in code. This is not all, since binding does not confine only to UI controls where we have learned how to bind data columns to verification steps also. We have also highlighted dynamic filtering on data sources, where the set of the executing rows can be evaluated and retrieved based on automation criteria just before the test executes. A powerful feature inside Test Studio was also explained and illustrated in the examples discussed previously. This happens when one test is nested...