Copy and Paste Test Steps, Properties and Data Table Rows

[simonalexander2005]

When I have many test cases that use similar test steps, it would be very helpful to be able to copy/paste them, instead of having to recreate them along with all the assertions each time. Likewise for data table rows, where I might have the same test data setup for different tests.

This is actually my highest priority feature request I think - it would save a LOT of time

[zheng-wang]

Please have a try on the Test Case copy paste. I have been using this for long time. I have a folder which contains many 'template' test cases for all kinds of 'patterns'. Each 'template' test case contains pre-created test steps which use managed endpoints and properties.

When I create a new test case, I just copy from a 'template' test case, and then tailor the new test case by populating few details specific to it, like input message and expected output message. I use properties in my 'templates', so most of the time I only need to populate data on the Properties tab of the new test case, and then run it. This way I treat test cases like blackboxes. I don't even remember what test steps are in a test case. I only need to care about the blackbox's parameters (the properties). This not only saved me a lot of time, but also saved me a lot of brain storage and energy.

My understanding is that copy/paste at test case level is more efficient than copy/paste at test steps, properties and data table rows levels, because more reusable logic is copied at a time at test case level.

[simonalexander2005]

I am setting up some test cases which need some steps from one test case, and some from another; so currently I can copy one of the test cases but then need to re-create half of the test steps that come from the other test case; rather than just being able to copy and paste them

[zheng-wang]

I suggest you create many 'template' test cases, and organize them in subfolders, so that most of times you can just copy test case, and don't need to care about test steps. If you find yourself working on test steps a lot, just create more 'template' test cases so as to avoid it. This initial process may need effort, but I believe you will feel a lot relieved when getting there.

Actually I had the same requirement as you a couple of years back (reuse common testing logic), and test case copy/paste was the solution I figured out. Please let me know if you are able to find a more productive way of creating test cases.

[zheng-wang]

On the other hand, copy/paste at Test Steps, Properties and Data Table Rows levels is definitely useful, but it shouldn't be used often. Otherwise it is going to make user experience close to using code.

Iron Test is designed to relieve user from reading too many details. You can achieve everything by using Java code (JUnit), but the effort is to read a lot of code again and again every day. Reading code is brain energy burning.

Similarly, reading and digging into test steps details is also brain energy burning (though less than reading and digging into code). Iron Test intends to help user dump details out of mind (and into reusable test cases), and avoid user remembering and repeating so many details so frequently.

[simonalexander2005]

Yes, I think we agree about the aim - it's the initial set up where the copy-and-pasting would be useful

[zheng-wang]

Ok thanks, the feature makes the tool's copy/paste capability more complete, and especially useful when creating new 'template' test cases from existing 'template' or 'populated' test cases. But due to not used often in the long term, I'm leaving it as a low priority item to implement.