Hi there,
I have a question regarding an error message that my QA team is frequently running into when playing back tests. The issue happens when either a manual or coded step has been added to a test. One example is when we created a test which uses other tests as steps. This test will initially pass up to the point where we need to create a manual step. After creating the manual step we received the following error:
The test is no longer able to run and becomes useless even when removing the manual step. This same behavior happens when either intentionally or accidentally adding a coded step to a test. The tests don't appear to load successfully and the same MSN link is given for more information.
I'm attaching a snipet of the log file associated to this error message in the ticket.
What exactly does this error message mean and what, if anything, can be done to circumvent this problem?
Thank you,
Isaiah
I have a question regarding an error message that my QA team is frequently running into when playing back tests. The issue happens when either a manual or coded step has been added to a test. One example is when we created a test which uses other tests as steps. This test will initially pass up to the point where we need to create a manual step. After creating the manual step we received the following error:
------------------------------------------------------------'4/29/2013 10:34:51 AM' - Using .Net Runtime version: '4.0.30319.296' for test execution. Build version is '2012.2.1425.0'.'4/29/2013 10:34:51 AM' - Starting execution....'4/29/2013 10:34:57 AM' - Detected custom code in test. Locating test assembly: USBank Test Cases - Sara.dll.'4/29/2013 10:34:57 AM' - Failure detected during execution. Details:------------------------------------------------------------'4/29/2013 10:34:57 AM' - System.NotSupportedException: An attempt was made to load an assembly from a network location which would have caused the assembly to be sandboxed in previous versions of the .NET Framework. This release of the .NET Framework does not enable CAS policy by default, so this load may be dangerous. If this load is not intended to sandbox the assembly, please enable the loadFromRemoteSources switch. See http://go.microsoft.com/fwlink/?LinkId=155569 for more information. at System.Reflection.RuntimeAssembly.nLoadFile(String path, Evidence evidence) at System.Reflection.Assembly.LoadFile(String path) 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.TestExecuteProxy.ExecuteTest(ExecuteTestCommand command) ------------------------------------------------------------ '4/29/2013 10:34:57 AM' - Test completed!The test is no longer able to run and becomes useless even when removing the manual step. This same behavior happens when either intentionally or accidentally adding a coded step to a test. The tests don't appear to load successfully and the same MSN link is given for more information.
I'm attaching a snipet of the log file associated to this error message in the ticket.
What exactly does this error message mean and what, if anything, can be done to circumvent this problem?
Thank you,
Isaiah
1 Answer, 1 is accepted
0
Hi Isaiah,
Cody
the Telerik team
Please try following these directions to overcome this error.
http://www.telerik.com/automated-testing-tools/support/documentation/user-guide/troubleshooting_guide/test-execution-problems/cannot-access-network-dll-net-4.aspx
Cody
the Telerik team
Quickly become an expert in Test Studio, check out our new training sessions!
Test Studio Trainings
Test Studio Trainings