Forum Discussion

alessandro's avatar
alessandro
New Contributor
17 years ago

run testCase & property transfer problem

hi,
got this problem with both free e pro (trial) 2.5:

when I open a project from file,

1) the runTestCase step is no more properly configured (the target testCase is different from the one I chose, though it still belongs to the same suite. moreover,  the now-targeted case is the original version of the copy I'd like to target now, but with different properties)

2) the property transfer just before the runTestCase step not only doesn't point to the correct property in the runTestCase step (which I guess is right, after point 1)), but also doesn't get in input any property of the Case step it belongs: these properties are still present in the case.

everything's working right if I do not exit, but testRunner: it gives me the message "error performing transfer - missing source property" , which it seems to me related to 2).

any hints?

thanks in advance
al

5 Replies

  • omatzura's avatar
    omatzura
    Super Contributor
    Hi Alessandro,

    thanks for reporting this. Can you tell me in which order you created this Run TestCase step? Did you:

    1) Create a Run TestCase and point it another TestCase in your TestSuite
    2) Clone the target TestCase
    3) Change the Run TestCase to point to the clone instead

    ?

    regards!

    /Ole
    eviware.com
  • alessandro's avatar
    alessandro
    New Contributor
    hi Ole,

    this is what I did:

    1)cloned a test suite within a project
    2)cloned a test case, say "a". this test case (has a step which) was already pointing to another test case, say "b"
    3) modified "b" (introduced a Case property) and changed its name
    4)modified the "a"-clone (introduced a Case property) and changed its name

    after reopening, the modified "b" was still pointing to the original "a", in the other - original - test suite (I m sorry I have just realized I wrongly reported in my previous message that the original "b" was in the same suite)
    a note: the original "a" case in the cloned suite was not intended to be used, indeed it did not work after modifying "b": was just there for reference and would have been deleted later.

    hope this helps

    regards
    alessandro
  • omatzura's avatar
    omatzura
    Super Contributor
    Thanks, I'll try to reproduce this!

    Do you see any errors in the error log after this?

    regards!

    /Ole
    eviware.com
  • omatzura's avatar
    omatzura
    Super Contributor
    Hi again,

    ok.. I got it now.. the problem is that the run-testcase step has a target testsuite setting, which is not modified to point to the new testsuite (ie it is cloned in its whole).. will be fixed soon.. I'll let you know..

    Thanks again for reporting!

    regards,

    /Ole
    eviware.com
  • Hi Alessandro,

    the next nightly build should fix this, please let me know otherwise!

    regards,

    /Ole
    eviware.com