Testing with Internet Explorer on Selenium Grid with node as Windows service - selenium-webdriver

We have build several Selenium tests of our corporate portal. The next step is to test on a Selenium Grid setup. We have access to a Hub and a Node which are started as a service on a Windows Server. We can connect to the Hub and the tests are started on the Node.
Because the Node is started as a service the tests are executed in the background. The tests have to be executed in IE11 because the portal only works correctly on that browser. So far so good.
Only our tests of the portal do not execute properly. The portal is made in Tibco and contains ActiveX elements and a lot of scripts.
We tried several possible solutions:
Started the service (of the node) with an actual user instead of the System user
Lowered all security settings
Switched protected mode in all area's
Added the portal url to the Trusted Sites
But nothing worked.
We also tried a test on a very simpel website with only a textbox and a button and that worked. Also when we navigate to the portal from the server where the node is located everything works fine.
Only when the tests are executed from the background it looks like the website cannot be properly loaded.
Has anyone encountered this problem before? Or does anyone know how to troubleshoot this issue?

Related

How to see if gatsby-plugin-offline is working

I am new to Gatsby so please bear with me.
I want to add offline support to my app such that if a user were to try access it while offline (after having visited it online) it would still show up.
Would gatsby-plugin-offline help me achieve this?
If so, how can I try this out? So far I have tried using the plug-in in my app (all default settings), building the app and then serving it locally on my computer at http://localhost:9000/. When I stop the dev server and try access http://localhost:9000/, it does not show up. How can I test to see if this plugin works?
After gatsby build the public folder should include sw.js file.
Otherwise, you can find whether the service worker is registered on not at Chrome Dev Console over Application > Service Workers.

Problems testing Office Add-In with an already Existing Web API project

I have a Web API service that is tested and working well. In a separate project I have an Outlook Web Add-In. The UI is working just fine. Now, I would like to make calls to the Web Service I've created.
The Web API project launches IIS (using SSL)
I've copied (copy/paste) the Office Add-In folders to what would be the root folder ... (at least I think I have the web root folder)
After launching the Web Service from Visual Studio, I run OWA and side load my Add-in. The right Icon appears. When I click on one of the commands in the drop down, nothing happens. Chrome's debugger doesn't show any messages that would indicate that my Add-in has been called. No errors.

Selenium tests with WebDriver and Visual Studio Online

I'd like to run a number of Selenium tests as a part of my product's Contionous Integration mechanism. We're using Visual Studio Online.
I've tried using IE WebDriver and it could not connect to my resources. I've tried deploying portable versio of Firefox and tests appear to be stuck - I'm guessing that there is a firewall prompt happening?
I've tried PhantomJs web driver, but that does not appear to properly render the test page at all (unless I'm doing something completely wrong)...
so... is it even possible to run Selenium based browser tests from Visual Studio Online build servers?
It appears that this is currently not supported by the hosted build controller. The way to do it is to set up a remote build controller and connect it with your visualstudio.com account. I haven't tried this out yet but here's instructions on how to do it with an Azure machine: http://erictummers.wordpress.com/2014/02/12/run-selenium-from-visualstudio-com/

Click once Deployment suddenly does not work. Displays windows login?

I am facing a peculiar issue. We use click once deployment for our windows application. It was working fine till last week. I made some changes to the application (just code nothing changed in properties) and suddenly I cannot publish anymore. When we give publish now it displays windows authentication dialog and when we provide the credentials nothing happens. It tries to connect to remote server (local LAN) and shows the dialog again.
Any idea why this happens?
Thanks for your help.
Are you publishing it to http or ftp? Have they added password-protection to the server so you have to enter credentials in order to publish the application?
After you enter credentials, what does it say in the Output window?

Silverlight tests not working unless RDP connection open

I have a few Silverlight UI tests that I'm automating with White. These tests are subsequently run by a TFS build agent, which is running interactively so it can access the desktop.
The build passes if I have a Remote Desktop connection open to the build agent as the tests are run; I can see the mouse pointer moving around. When the test clicks on a HyperlinkButton navigation takes place, and is subsequently verified by assertions within the test.
The build fails if I do not have a Remote Desktop connection open to the build agent as the tests are run. The Internet Explorer window is created and the Silverlight app loads, but no clicks happen; the application remains on the initial page and test assertions subsequently fail.
Has anyone out there found a solution to this problem?
See Starting a Windows service in an interactive session
If you are setting up a windows service, that service can be set to run with an interactive desktop, though it will be running as a local machine user and not a domain user.
The other alternative is tweaking the registry to use the AutoAdminLogon feature. Use with caution!
HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon:
DefaultUsername
DefaultPassword
DefaultDomain
AutoAdminLogon = 1
The answer is on this CodePlex thread. Basically there is no solution; White tests must be run by a logged-in user (either physically, or via VNC or RDP).

Resources