Completed
Last Updated: 03 Apr 2023 21:13 by ADMIN
ADMIN
Cody
Created on: 21 Nov 2014 16:20
Type: Bug Report
1
Error "Unable to find the test class type" when using Telerik.TestStudio.CommandLineClient.exe
When running a test list in which a parent test calls a subtest with a coded step you may get the following:
Overall Result: Fail
------------------------------------------------------------
'11/21/2014 10:10:33 AM' - Executing test: 'ExecuteTestAsStep', path: 'ExecuteTestAsStep.tstest.'
'11/21/2014 10:10:33 AM' - Using .Net Runtime version: '4.0.30319.18444' for test execution. Build version is '2014.3.1016.0'.
'11/21/2014 10:10:33 AM' - Starting execution....
------------------------------------------------------------
------------------------------------------------------------
'11/21/2014 10:10:35 AM' - Enabling Html Popup Tracker. Test expecting Popups.
'11/21/2014 10:10:35 AM' - Using 'InternetExplorer' version '10.0' as default browser. 
'11/21/2014 10:10:35 AM' - 'Fail' : 1. Execute test 'AccessWebsite'

>>> Test-as-Step 'AccessWebsite.tstest' log starts:

------------------------------------------------------------
'11/21/2014 10:10:35 AM' - Detected custom code in test. Locating test assembly: CommandLineClientExecutionErrorSample.dll.
'11/21/2014 10:10:35 AM' - Assembly Found: F:\TEMP\Projects\ed08cc31-39a7-4e41-b982-3cc9af2cfda7\CommandLineClientExecutionErrorSample\bin\CommandLineClientExecutionErrorSample.dll
'11/21/2014 10:10:35 AM' - Loading code class: 'CommandLineClientExecutionErrorSample.AccessWebsite'.
------------------------------------------------------------
'11/21/2014 10:10:35 AM' - Error attempting to execute a Test As Step. Details:
'11/21/2014 10:10:35 AM' - System.ArgumentException: Unable to find the test class type 'CommandLineClientExecutionErrorSample.AccessWebsite' in your test assembly. Please make sure your test code behind is compiled with your latest changes.
   at ArtOfTest.WebAii.Design.Execution.ExecutionUtils.EnsureTypeExists(Assembly assm, String typeName)
   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 'AccessWebsite.tstest' log ends.

------------------------------------------------------------
'11/21/2014 10:10:35 AM' - Detected a failure. Step is marked 'ContinueOnFailure=False' aborting test execution.
------------------------------------------------------------
'11/21/2014 10:10:35 AM' - Overall Result: Fail
'11/21/2014 10:10:35 AM' - Duration: [0 min: 0 sec: 121 msec]
------------------------------------------------------------
'11/21/2014 10:10:35 AM' - Test completed!

Sample project to reproduce the problem is attached. Run it from command line using:
"c:\Program Files (x86)\Telerik\Test Studio\Bin\Telerik.TestStudio.CommandLineClient.exe" -l TestLists\SampleList.aiilist -u http://localhost:8009
4 comments
Andrew
Posted on: 10 Jul 2015 13:57
The work around provided by Ivaylo has worked for us.  You must first run your test from the Telerik Test Studio UI client before you can use the command line client.  If you don't want to recreate the database you can just delete the data within the tables.

Thank you.
ADMIN
Ivaylo
Posted on: 10 Jul 2015 11:22
Another workaround:

1. Recreate the database.
2. When brand new you need to execute the test list using the scheduling but with Test Studio. This will upload all necessary files in the database.
3. Then you are free to use the Command Line client.
ADMIN
Iliyan Panchev
Posted on: 12 Dec 2014 11:54
Hi, most probably you added a code in the test as step and it didn't got uploaded on the storate. A workaroud for this is to add a step, for example Capture Desktop. in the test as step and delete it. This will change the time stamp of the test as step and it should get uploaded with latest code. This is a known problem with the scheduling architecture, that we are currently working on. Unfortunatelly I cannot give you estimate for a fix.
Bryan
Posted on: 21 Nov 2014 16:45
This and other issues make this tool unusable by our organization.