This would be useful as an "object oriented" use of test steps. The goal would be to reuse test steps for different data inputs and website global settings for our website testing. Another benefit of the test bind data being set outside of the test step is that source control would be relatively unaffected by the modification of data input into the bound table. Considering using MS Access to have tables bound to specific test steps and deleting records and appending new records prior to test step execution within a system test (some are simple functional test and others are more complex system tests and setups). In our proposed implementation a 'coded step' would need to be executed prior to the test step to clear and append the table which is bound to the test step. Btw, many of the test steps are bound to a table with a single record. Perhaps allow instances of test as steps to be inserted in a test case with instance specific data binding. This may not be ideal but it should work.