I am using a recorded action via coded ui tests in Visual Studio 2013 to launch an internal website and log in. All of this processes normally, except after logging in a loading animation continues to spin until the test fails. Attempting to log in normally without the automated test works flawlessly and the page loads normally with a <2 second delay.
I have attempted to add a pause in but no matter how long I wait it does not load. Is there a reason the coded ui test would be causing the page to hang?
This post here explains the problem using a much more simple application and points to this answer here on SO:
Jquery AJAX success not getting triggered with Coded UI test project
And if you do not have an app.config file, just right-click your solution->Add->New Item->Application configuration file and then replace existing text with:
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<appSettings>
<add key="WebWaitForReadyLevel" value="3"/>
</appSettings>
</configuration>
Related
I have the following in the runsettings
<?xml version="1.0" encoding="utf-8"?>
<RunSettings>
<!-- MSTest adapter -->
<MSTest>
<Parallelize>
<Workers>0</Workers>
<Scope>ClassLevel</Scope>
</Parallelize>
</MSTest>
</RunSettings>
I dont have the parallize setting in assemblyinfo.cs file
however before the tests are run the azure pipeline updates the workers attribute to 4. I want it to remain at 0 so it determines the cpu count using the available resources.
Does any have any thoughts on this?
Regards
Cleaned up the local files to make sure old files are not there.
Tried different workers setting however it keeps reverting to 4
We deployed Batching Custom functions project into IIS as hosted application. Task-pane is working fine with API. But when trying to invoke as custom functions facing issue
Error in loading custom functions
at the bottom of add-in. We developed using webpack.config.js but little confused when deploying on IIS for exact server running. So do we need to use express js to run separate port or directly shall we run only enough webpack.config.js file? Kindly confirm on this deployment process.
Also Taskpane related API's are able to fetch successfully but only facing issue with custom functions related API.
You may can check if custom function related files can be seen in your website hosted by IIS. You can have the url information in manifest file.
Would you please check whether you could access the JSON file by browsing to http:///custom-function.json? Would you please also check whether the mime type is correct? If the mime type is not correct, you may need to update the web.config, such as
<configuration>
<system.webServer>
<staticContent>
<remove fileExtension=".json"/>
<mimeMap fileExtension=".json" mimeType="application/json" />
</staticContent>
</system.webServer>
</configuration>
By the way, to make it work for Excel online, you also need to enable CORS access to the custom-function.json
I've been attempting to fix a problem I have with Test Explorer not showing tests when I'm in a different configuration environment. I make local environment changes by updating my app.config.
I have already tried a few steps found here and in other sites including cleaning my project, updating to the latest xUnit test runner, etc.
I am sure the reason is code/project based and not the Visual Studio environment itself. What I would like to know is whether or not there is a log file I can look at that would help me to determine why my tests are not showing. Or, is there another good method to troubleshoot errors with tests not showing up in Test Explorer?
There is a MSDN Blog post about this.
Essentially, you need to:
Go to folder %VSInstallDir%\Common7\IDE\CommonExtensions\Microsoft\TestWindow
Find the config file for the process you want to debug (e.g. vstest.console.exe.config, vstest.discoveryengine.exe.config, etc)
Alter the config file system.diagnostics node to include:
<system.diagnostics>
<switches>
<add name="TpTraceLevel" value="4" />
</switches>
</system.diagnostics>
Close VisualStudio, open it again, and discover/run tests from TestExplorer Window
Look for logs under %temp%[processname].TpTrace.log (e.g. vstest.console.tptrace.log)
Windows vista 32 bit - C# - .NET 4 - sqlite - IIS 7
I'm building a small project that contains is a custom HTTP handler where an user can request a XML file and the project will generate the file and send it to the user. It should be flexible enough to send something else too like e.g. json.
Everything was going well until I had to deploy the handler. I've created a library (dll) file which contains the logic for serving of the requested information. I've open IIS manager and I've created a virtual directory to the debug bin file (later on i made it an application. it did not make a difference).
I've followed countless examples and tutorials like these ones:
I started with this one: http://support.microsoft.com/kb/308001
http://msdn.microsoft.com/en-us/library/bb515343.aspx
msdn.microsoft.com/en-us/library/46c5ddfy.aspx
But with no luck. As you could have read I'm not using any asp.net website even though I do have a web.config that I've added to the bin folder and it looks like this:
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<system.webServer>
<httpErrors errorMode="Detailed" />
<asp scriptErrorSentToBrowser="true" />
<directoryBrowse enabled="false" />
<handlers accessPolicy="Read, Script, Execute">
<add name="LigoManagedHandler" path="*" verb="*" type="Ligo.Service, Ligo" resourceType="Unspecified" preCondition="integratedMode" />
</handlers>
</system.webServer>
</configuration>
When I try to run handler in the browser get the following error:
Could not load file or assembly 'Ligo' or one of its dependencies. The system cannot find the file specified.
Exception Details: System.IO.FileNotFoundException: Could not load file or assembly 'Ligo' or one of its dependencies. The system cannot find the file specified.
I have tried so many possible combination in IIS manager to get it working ('httphandlers', 'classic mode' and so on ...) but i'm truly stuck. The information I've found on the internet is not helping much.
What am I doing wrong or missing to make it work?
Something in this rant triggered an idea, an I stumbled on the answer.
The line in all those tutorials that say put type="ClassName, AssemblyName" into the Handlers section in Web.Config are plain WRONG.
All I did was change this to type="AssemblyName.ClassName" and everything started working, in both a Web Site Project and a Web Application Project that I had created.
I'm running IIS 7.5 in integrated mode so YMMV.
Craig
I figure it out. I had to make a asp.net website project and add my dll as reference to this project.
I read this thread that provided this information which is not clear on the internet.
http://forums.asp.net/t/1088861.aspx/1?What+causes+the+quot+Could+not+load+type+quot+problem+
It should state that it is not possible to make the httphandler without a aspnet website project. or am i mistaken? the example on the internet are incorrect! or provide too little information.
I know, this is an old thread. However, I've been looking for an answer for a few days without finding a clear one. So, in case anyone comes across similar scenario.
You can create custom Http Handler as a stand-alone Class Library project and use it in IIS.
On IIS Add new Application with ASP4 Integrated mode. Place your compiled DLL into bin folder (this is what i was missing all along). Seems obvious that it should be there; took some time to figure this out. :)
web.config:
<configuration>
<system.web>
<compilation debug="true" targetFramework="4.0" />
</system.web>
<system.webServer>
<handlers>
<add verb="*" path="*.ogg" name="test" type="Namespace.Classname"/>
</handlers>
</system.webServer>
</configuration>
Hope this helps.
Cheers.
The solution works great with cassini but as soon as I make it run into IIS (7.5 on Windows 7 / 64), it stops working. All js & css file are never downloaded and the script fails. I looked into the MiniProfilerHanler, the GetHttpHandler method is called for each required js & css but the ProcessRequest method never runs.
The same behavior is observed using the sample.mvc project that goes along with the mini profiler sources.
I went to Program/Feature control pannel and clicked add remove windows feature. There I saw that under IIS, ASP.Net was not selected (all my sites worked like a charm) and checked it.. and Voila ! Don't ask ;-)
this is an older question but if you are still trying to get this to work try adding this to your web.config
<system.webServer>
<modules runAllManagedModulesForAllRequests="true"/>
</system.webServer>
not really the best solution but it works