I just upgraded to the latest version of TS 2013. Right now I've got a storage, scheduling, and execution server all connected on the same machine.
When I run a test list remotely, weather through the run remotely button or scheduling, the app launches but immediately closes and the log file from Test Studio is at the bottom of this post. It appears it is not correctly compiling for the coded steps. If I run the test list locally (non-remote nor scheduled), then the test lists run fine.
The folder path that is listed in the log error is empty in windows explorer.
Overall Result: Fail
------------------------------------------------------------
'10/23/2013 9:13:49 AM' - Using .Net Runtime version: '4.0.30319.34003' for test execution. Build version is '2013.1.911.0'.
'10/23/2013 9:13:49 AM' - Starting execution....
------------------------------------------------------------
------------------------------------------------------------
'10/23/2013 9:13:57 AM' - Using 'C:\TestStudio\Executables\Kanso\Hds.Kanso.exe' application.
'10/23/2013 9:13:57 AM' - 'Fail' : 1. Execute test 'Navigate to Administration.tstest'
>>> Test-as-Step 'Navigate to Administration.tstest' log starts:
Overall Result: Fail
------------------------------------------------------------
'10/23/2013 9:13:57 AM' - Using 'C:\TestStudio\Executables\Kanso\Hds.Kanso.exe' application.
'10/23/2013 9:13:57 AM' - 'Fail' : 1. Execute test 'Fast Login'
>>> Test-as-Step 'Fast Login.tstest' log starts:
------------------------------------------------------------
'10/23/2013 9:13:57 AM' - Detected custom code in test. Locating test assembly: HDS Kanso.dll.
------------------------------------------------------------
'10/23/2013 9:13:57 AM' - Error attempting to execute a Test As Step. Details:
'10/23/2013 9:13:57 AM' - System.IO.FileNotFoundException: Unable to find the code behind assembly. Please make sure you have compiled your code behind without errors before attempting to execute the test. Looking for: C:\Users\Peter\AppData\Local\Temp\Projects\aeacbeda-a5ef-4595-a6c3-c9d9ce756c44\HDS Kanso\bin\HDS Kanso.dll
If you are running VS 2010, make sure Deployment is checked in your .settings file (in the solution items)
at ArtOfTest.WebAii.Design.Execution.ExecutionUtils.EnsureAssemblyExists(String assembly, String folder)
at ArtOfTest.WebAii.Design.Execution.ExecutionUtils.CreateCodedTestInstance(Test test, TestResult result, String binariesFolder)
at ArtOfTest.WebAii.Design.Execution.ExecutionEngine.InternalExecuteTest(Test test, TestResult initializationResult)
at ArtOfTest.WebAii.Design.Execution.ExecutionEngine.ExecuteTestInCurrentContext(Test test)
<<< Test-as-Step 'Fast Login.tstest' log ends.
------------------------------------------------------------
'10/23/2013 9:13:57 AM' - Detected a failure. Step is marked 'ContinueOnFailure=False' aborting test execution.
------------------------------------------------------------
'10/23/2013 9:13:57 AM' - Overall Result: Fail
'10/23/2013 9:13:57 AM' - Duration: [0 min: 0 sec: 82 msec]
------------------------------------------------------------
<<< Test-as-Step 'Navigate to Administration.tstest' log ends.
------------------------------------------------------------
'10/23/2013 9:13:57 AM' - Detected a failure. Step is marked 'ContinueOnFailure=False' aborting test execution.
------------------------------------------------------------
'10/23/2013 9:13:57 AM' - Overall Result: Fail
'10/23/2013 9:13:57 AM' - Duration: [0 min: 0 sec: 316 msec]
------------------------------------------------------------
'10/23/2013 9:13:57 AM' - Test completed!
When I run a test list remotely, weather through the run remotely button or scheduling, the app launches but immediately closes and the log file from Test Studio is at the bottom of this post. It appears it is not correctly compiling for the coded steps. If I run the test list locally (non-remote nor scheduled), then the test lists run fine.
The folder path that is listed in the log error is empty in windows explorer.
Overall Result: Fail
------------------------------------------------------------
'10/23/2013 9:13:49 AM' - Using .Net Runtime version: '4.0.30319.34003' for test execution. Build version is '2013.1.911.0'.
'10/23/2013 9:13:49 AM' - Starting execution....
------------------------------------------------------------
------------------------------------------------------------
'10/23/2013 9:13:57 AM' - Using 'C:\TestStudio\Executables\Kanso\Hds.Kanso.exe' application.
'10/23/2013 9:13:57 AM' - 'Fail' : 1. Execute test 'Navigate to Administration.tstest'
>>> Test-as-Step 'Navigate to Administration.tstest' log starts:
Overall Result: Fail
------------------------------------------------------------
'10/23/2013 9:13:57 AM' - Using 'C:\TestStudio\Executables\Kanso\Hds.Kanso.exe' application.
'10/23/2013 9:13:57 AM' - 'Fail' : 1. Execute test 'Fast Login'
>>> Test-as-Step 'Fast Login.tstest' log starts:
------------------------------------------------------------
'10/23/2013 9:13:57 AM' - Detected custom code in test. Locating test assembly: HDS Kanso.dll.
------------------------------------------------------------
'10/23/2013 9:13:57 AM' - Error attempting to execute a Test As Step. Details:
'10/23/2013 9:13:57 AM' - System.IO.FileNotFoundException: Unable to find the code behind assembly. Please make sure you have compiled your code behind without errors before attempting to execute the test. Looking for: C:\Users\Peter\AppData\Local\Temp\Projects\aeacbeda-a5ef-4595-a6c3-c9d9ce756c44\HDS Kanso\bin\HDS Kanso.dll
If you are running VS 2010, make sure Deployment is checked in your .settings file (in the solution items)
at ArtOfTest.WebAii.Design.Execution.ExecutionUtils.EnsureAssemblyExists(String assembly, String folder)
at ArtOfTest.WebAii.Design.Execution.ExecutionUtils.CreateCodedTestInstance(Test test, TestResult result, String binariesFolder)
at ArtOfTest.WebAii.Design.Execution.ExecutionEngine.InternalExecuteTest(Test test, TestResult initializationResult)
at ArtOfTest.WebAii.Design.Execution.ExecutionEngine.ExecuteTestInCurrentContext(Test test)
<<< Test-as-Step 'Fast Login.tstest' log ends.
------------------------------------------------------------
'10/23/2013 9:13:57 AM' - Detected a failure. Step is marked 'ContinueOnFailure=False' aborting test execution.
------------------------------------------------------------
'10/23/2013 9:13:57 AM' - Overall Result: Fail
'10/23/2013 9:13:57 AM' - Duration: [0 min: 0 sec: 82 msec]
------------------------------------------------------------
<<< Test-as-Step 'Navigate to Administration.tstest' log ends.
------------------------------------------------------------
'10/23/2013 9:13:57 AM' - Detected a failure. Step is marked 'ContinueOnFailure=False' aborting test execution.
------------------------------------------------------------
'10/23/2013 9:13:57 AM' - Overall Result: Fail
'10/23/2013 9:13:57 AM' - Duration: [0 min: 0 sec: 316 msec]
------------------------------------------------------------
'10/23/2013 9:13:57 AM' - Test completed!
4 Answers, 1 is accepted
0
Hello Doug,
Boyan Boev
Telerik
To make this work you have to copy your dll to the ROOT directory of project, then just refer it from that location.
Note this will work only if you put the dll in the root directory as it is described at the bottom of this article. Test Studio will not find references to a DLL in the subfolders of the project folder. These include: bin, Properties, obj, Data, Backup, TestResults, Results, TestLists, and Profiler Configurations.
Hope this helps.
Boyan Boev
Telerik
0
Doug
Top achievements
Rank 1
Rank 1
answered on 24 Oct 2013, 03:41 PM
Okay, Thanks for the advice.
However I might be a little unsure what you mean. Right now the .dll file is in the bin folder. with this path:
"C:\TestStudio\Source Code\WorkOrders\Tests\HDS Kanso\bin\HDS Kanso.dll"
Do you want me to copy it to the main project folder so it has this path:
"C:\TestStudio\Source Code\WorkOrders\Tests\HDS Kanso\HDS Kanso.dll"
I did tried that, and then added the .dll as a reference assembly in the project settings in Test Studio. But it didn't work. And the I got the same behavior. The log was the same on the remote list run. So I might be confused as to what you mean.
My main project folder Path is "C:\...\Tests\HDSKanso"
However I might be a little unsure what you mean. Right now the .dll file is in the bin folder. with this path:
"C:\TestStudio\Source Code\WorkOrders\Tests\HDS Kanso\bin\HDS Kanso.dll"
Do you want me to copy it to the main project folder so it has this path:
"C:\TestStudio\Source Code\WorkOrders\Tests\HDS Kanso\HDS Kanso.dll"
I did tried that, and then added the .dll as a reference assembly in the project settings in Test Studio. But it didn't work. And the I got the same behavior. The log was the same on the remote list run. So I might be confused as to what you mean.
My main project folder Path is "C:\...\Tests\HDSKanso"
0
Doug
Top achievements
Rank 1
Rank 1
answered on 24 Oct 2013, 04:26 PM
So this thread had a similar problem:
http://www.telerik.com/automated-testing-tools/community/forums/test-studio/general-discussions/remote-execution-failure.aspx
I tried the work around suggested, but did not fully work. But it did allow me a bit of knowledge. If I include the tests containing the coded steps in the test list, then the list will run remotely. Currently the coded steps are nestled in a test-as-step. However, unlike how the article suggests, if I ever take out the test with the coded steps out from the test list after the first run, I get back to the same problem.
I posted there too, since it seems to match my problem. If you want to merge the discussion I don't have any objections.
http://www.telerik.com/automated-testing-tools/community/forums/test-studio/general-discussions/remote-execution-failure.aspx
I tried the work around suggested, but did not fully work. But it did allow me a bit of knowledge. If I include the tests containing the coded steps in the test list, then the list will run remotely. Currently the coded steps are nestled in a test-as-step. However, unlike how the article suggests, if I ever take out the test with the coded steps out from the test list after the first run, I get back to the same problem.
I posted there too, since it seems to match my problem. If you want to merge the discussion I don't have any objections.
0
Hi Doug,
Boyan Boev
Telerik
Please excuse me for misunderstanding. I though you are using some custom dll, in your case you don't need to copy the project dll to the root directory.
Let's continue the discussion in the other thread for public benefits.
Thank you for your understandings.
Boyan Boev
Telerik