Test as Step not working with imported tests

Progress® Telerik® Test Studio® Feedback Portal

Create an account Log In

Back to Feed

Request a Feature Report a Bug

Completed

Last Updated: 10 Mar 2014 07:51 by ADMIN

ADMIN

Velin Koychev

Created on: 12 Aug 2013 08:44

Type: Bug Report

Test as Step not working with imported tests

To reproduce:
1) Create Project A with two tests that are inside folder Test Steps.
2) Make one of the tests to be Test as Step in the other test.
3) Create new Project B and copy the folder Test Steps from Project A and paste it in Project B
4) After clicking Refresh button, these tests are imported in project B. 
5) Double click the Test as Step in the main test. It doesn't open the subtest, it throws error "test with Id 'cf04.......' was not found!"
6) If we try to execute the main test, it executes successfully the subtest (it is able to find the subtest)

The sample projects are attached in the internal description..

Note: It doesn't reproduce every time.

3 comments

ADMIN

Iliyan Panchev

Posted on: 10 Mar 2014 07:51

Hi, what version of Test Studio are you using? In latest releases this behavior is not reproducible. The tests have IDs and TS handles better copying of test as steps and importing them in a new project.

Dean

Posted on: 06 Mar 2014 22:37

I have not found that this issue gets fixed as described.

What would be nice is if the copy procedure, when done from within Test Studio, should trace the steps inside of the test being copied and identify/include all of the test dependencies and make those corrections as the copy is being done.  As it is now, the dependencies are not identified and have to be manually found and fixed.

Inasmuch as the TS recognizes a change in one test and identifies all of the other places that the change will affect, then updates those files and waits for the user to save the changes, it seems that a copy process from one project to another should be able to identify the components in the other project associated with the copy and then fix or import the needed dependencies.

TS is already doing most of the work within a single project, but did not extend that capability to the import of something from a different project.

ADMIN

Iliyan Panchev

Posted on: 12 Aug 2013 14:53

The problem is that after copying the tests, their path changes. When they are imported into the new project with the Refresh button, the tests are marked as dirty (they are in bold). In order to open the nested test from its parent, you should first save the project, so all paths are updated. After that the issue will be gone.