Rank 1
I can set auto-submit on advanced setting of tfs bug tracking.
In case of failure, a different bug has been submitted for each test step and its sub step and so on.
For example in a test execution like;
Step1
Step2
Step2.1
Step2.2
Step2.2.1
Step2.2.2
Step2.2.3
Step2.3
Step3
If Step2.2.3 fails, tool seperately creates three bug on tfs for Step2.2.3, Step 2.2 and Step2.
And it says, it is Standalone test list execution feature only! Does it mean that this feature doesnt work for test scheduling and execution server?
Thanks
Ercan
5 Answers, 1 is accepted
The automatic bug submission feature functions for scheduled test list executions, even if they are executed on a separate machine. However, it is not available for Test Studio Runtime Edition or the Visual Studio plugin.
Regards,Byron
the Telerik team
Vote now
Rank 1
Thanks for your reply.
I have updated my post later and added a new question but I guess you havent seen it.
Do you have any idea about it? I am posting below again.
In case of failure, a different bug has been submitted for each test step and its sub step and so on.
For example in a test execution like;
Step1
Step2
Step2.1
Step2.2
Step2.2.1
Step2.2.2
Step2.2.3
Step2.3
Step3
If Step2.2.3 fails, tool seperately creates three bug on tfs for Step2.2.3, Step 2.2 and Step2.
Thanks
Ercan
So far, I have not been able to reproduce this behavior: test lists with automatic bug reporting to TFS submit only one bug when the last step of a multi-step subtest fails during list execution. Are you using TeamPulse bug reporting or TFS? Can you provide the version of your source control server? If possible, please provide us with a copy of your test and access to your application. Also, please provide your failure log. You can export this to file from the failure tab for your test and add them to a .zip archive. If it is not possible to grant us access to your application, please take a Fiddler trace and attach it to a support ticket in a zip file. You can capture a Fiddler trace using FiddlerCap. A Jing video of the behavior may also help us diagnose your issue. Thanks for helping us diagnose this behavior.
Kind regards,Byron
the Telerik team
Vote now
Rank 1
I have submitted the ticket #628083.
We are using TFS 2010.
By the way, problematic sub-steps are tests as sub-steps. This may be the reason of the problem?
Thanks
Ercan
Based on your support ticket, it appears that a logical step is calling a subtest containing a coded step as part of its if branch. In this scenario, Test Studio generates a bug report for the step in the subtest that fails, and a bug report for the conditional step that failed as a result, in that order.
I have created a bug report for this behavior, which you can follow in our Public Issue Tracking System (PITS). Thanks for your input, which we rely upon to improve our product.
Byron
the Telerik team
Vote now