Progress® Telerik® Test Studio® Feedback Portal
Back to Feed
Request a Feature Report a Bug
Completed
Last Updated: 07 May 2015 15:07 by ADMIN
ADMIN
Ivaylo
Created on: 14 Apr 2015 07:57
Type: Feature Request
1
Duplicate entries in the execution log when calling test as step in data-driven scenario
Steps to reproduce:

1. Execute test #1 in the project attached internally.

2. Execution passes successfully.

3. Refer to the execution log:


1. Expected behavior: The log is output correctly

2. Actual Behavior: There are duplicates in the log, refer to the screenshot attached internally.
7 comments
ADMIN
Konstantin Petkov
Posted on: 07 May 2015 15:07 
Hi Mikael,

No, we don't have the next internal build ready yet. We're finalizing the updates so that we can publish it next week (as soon as it passes QA validation).

Thanks!
Mikael
Posted on: 07 May 2015 12:14 
nice, thanks. It's not the build i see now when i check for updates or (2015.1.415.0)?
ADMIN
Daniel Djambov
Posted on: 30 Apr 2015 10:36 
Note: regarding your latest comment - this Scheduling results issue has nothing to do with the log issue from this feedback. Please log a Support request to have dedicated team look at your specific case and offer you a solution. Thank you, Test Studio team
ADMIN
Daniel Djambov
Posted on: 30 Apr 2015 10:34 
Telerik: the issue is fixed and solution will be available in our next internal product release, planned to be out early May 2015.
Mikael
Posted on: 21 Apr 2015 12:02 
I am also having problem loading the testresults from a scheduled run. I get a popup saying that telerik wasnt able to load it and that i should reopen the project. 
Doing that doesnt solve my problem. Could it be related (ie messed up logs because of this issue)? Should i zip the result and attach to this case?

I CAN see the results/reports if I execute just a few of the iterations but not if i run all 54 of them.
Mikael
Posted on: 21 Apr 2015 06:34 
I suspect that because of this, a failure in one iteration affects the result of the following iterations marking them as failed in the log even if the succeed
Mikael
Posted on: 21 Apr 2015 06:24 
Whats the eta/timeline on this errand?
Create an account Log In
View
Type
Status