Handle dialog step with extracted value and no file extension in code fails although is successfully performed

Progress® Telerik® Test Studio® Feedback Portal

Create an account Log In

Back to Feed

Request a Feature Report a Bug

Completed

Last Updated: 23 May 2016 12:41 by ADMIN

ADMIN

Elena

Created on: 15 Apr 2016 14:17

Type: Bug Report

Handle dialog step with extracted value and no file extension in code fails although is successfully performed

Please find attached a sample project. 

Steps to reproduce: 

1. Open the attached project 

2. Run the test. 

Expected behavior: Successful test. 

Actual behavior: The Handle dialog step fails although it is successfully executed.

Attached Files:

DownloadDialogdataBound.rar

1 comment

ADMIN

Daniel Djambov

Posted on: 23 May 2016 12:41

Telerik: this is a specific case and works as designed actually. The problem is that the extracted download path to the file does not include the extension of the file, which extension is recognized by the download dialog for the file type from Windows itself. This leads to having a path like "c:\temp\install" as extracted variable, and as file is '.msi' it downloads it successfully, but then when we make a check if file is downloaded, we look for file name "c:\temp\install" and it does not find it as it is actually saved as "c:\temp\install.msi". In the extracted code path you should include the file extension as well and in this case the step works as expected. Please bare in mind this specific requirement when working with extraction of paths in code. Thank you for the feedback.