Hi,
We are struggling to copy tests with coded steps in them. After copying and pasting a test with a coded step it fails to compile due to "The namespace 'TestProject' already contains a definition for 'TestX'"
The reason why we are using copy and paste rather than execute test as step in Test Studio is due to the fact that our workflows require many variable test data columns ( some consist of over a thousand ) therefore we are splitting the test data up into smaller more manageable tables in the database, creating a test for this data and binding it to all rows, then when the QA staff copies this test they will open the data bind and select only the rows they want to use.
Is there any way around this or will I have to workaround it by either changing the namespace in the code each time or renaming the step and code behind the step making it impossible for QA ( who have no technical knowledge ) to re-use?
Thanks
Shane
EDIT: At the moment I have created a single test containing just the coded step to workaround the issue. Although this works it seems strange to have to create tests every time I want to add a coded step. Please let me know if I have missed something.
We are struggling to copy tests with coded steps in them. After copying and pasting a test with a coded step it fails to compile due to "The namespace 'TestProject' already contains a definition for 'TestX'"
The reason why we are using copy and paste rather than execute test as step in Test Studio is due to the fact that our workflows require many variable test data columns ( some consist of over a thousand ) therefore we are splitting the test data up into smaller more manageable tables in the database, creating a test for this data and binding it to all rows, then when the QA staff copies this test they will open the data bind and select only the rows they want to use.
Is there any way around this or will I have to workaround it by either changing the namespace in the code each time or renaming the step and code behind the step making it impossible for QA ( who have no technical knowledge ) to re-use?
Thanks
Shane
EDIT: At the moment I have created a single test containing just the coded step to workaround the issue. Although this works it seems strange to have to create tests every time I want to add a coded step. Please let me know if I have missed something.