Watin test .exe file does not work in another pc - testing

I have problem with running WatiN test .exe file in another pc. When I try to run .exe file in my own pc (where I created it) it is work well! But then I run the same test in another pc, it is not work. IE is open and start testing but then program give me this error:
WatiN.Core.Exceptions.ElementReadOnlyExcption: Element with Id:Fname is readonly.
I know what this error mean, but gist is that this test have to work. In another pc there is not Visual Studio. Maybe it is need to install something?

Related

ChromeDriver is null when testing on a different PC

I have a problem/bug when i try to use new ChromeDriver. After using launch4j to create a .exe file and starting it everything except the ChromeDriver, which is null, is working fine.
On my main computer everything works as usual.
Im using Java on my main computer but not on the Virtual Machine, since I need to distribute it to others without it
So my question is am i missing something?

QTP has stopped recording and spying

I've been working for few months with QTP (UFT One 15.0.2), and today it has stopped recording (when I do the actions no lines are written in the script and no objects are added to the objects repository) and recognizing objects with the spy feature.
I am using the WEB add-in, and as I've been working for months with Mozilla Firefox I have checked that the WebExtension.xpi is well added to the browser.
I've tried to open mozilla before and after UFT One, I've also restarted my computer, I've checked the size of the screen browser is 100% and that in the Record and Run Settings the option " Record and run on any open browser" is checked for Web.
This situation usually occurs because the company's IT department has changed the related policy, causing the UFT Firefox extension to fail to run normally.
You can check if the HP.UFT.Firefox.NativeMessagingHost running in Windows task manager after openning Firefox while the extension is enabled, and check if the Micro Focus UFT Agent content script loaded in Firefox debugger's Sources tab(note: you need to check the "Enable browser chrome and add-on debugging toolboxes" in Web Developer Tools' Setting firstly).
If one of these things does not exist, you should check the policy change with your IT: did they block the related thing running?
If they all exist, you can open a CPE case to UFT One support. They will help you to do the further investigation.
I have checked that I had the same problem with chrome browser, so not an Extension problem.
Finally I have decided to uninstall and reinstall UFT One, but while uninstalling an error appeared and UFT persisted on the system.
After two trys I have launched UFT One and it has started working again.
I am not sure how long it will work.

Running webdriver IEDriver on Jenkins fails

I have a small C# webdriver test suite dll which I recently created...
Runs fine in Visual Studio
Runs from the command line perfectly using the NUnit 3 console runner.
I have Jenkins installed on my laptop (for testing before I put it into my live Jenkins), running with my Windows credentials. When I execute the test suite using the same NUnit3 console runner command I used before, all the tests fail, can't even log in as it can't find any elements. I took screenshots with Selenium & it's just a black rectangle!
Anyone have any ideas on how to get IE behaving - I bet it's a Windows permissions thing from Jenkins. Thanks!
I'll answer my own question.
Turns out you can't do what I'm attempting - it's a known issue with the way IE is built. What I had to do is install a new Jenkins node on another machine and get that to run the IE tests. That way it did work.

Installing INF files for a PnP device using devcon dp_add

I'm using a BAT file to execute the following command to install my INF file to another computer:
devcon dp_add "linux-cdc-acm.inf"
It works fine with Win7 x64 but it fails in Win8 x64. The error message is:
Adding the specified driver package to machine failed. devcon failed.
I assume the INF file is correct as I can install it manually via the DeviceManager and there is no new entry on [%windir%\inf\setupapi.dev.log]. Is there another way to install INF files to the driver store for Win8?
And another thing, is using devcon really the normal and correct way in installing INF files to client computers?
EDIT:
I got the devcon source from WDK, debugged it and found that I am getting a [ERROR_ACCESS_DENIED]. Is this failing because of the settings in Win8? What are ways to overcome this?
It seems the batch file or devcon just needed to be "run as administrator" in win8.
and test signing the catalog file for the INF file was also needed.
Alternatively for future reference, I was able to use WiX and DIFxApp to create a .msi installer that installs linux-cdc-acm.inf and linux.inf (RNDIS) gadget drivers. https://github.com/ambrice/linux-gadget
Haven't been able to figure out how to create a 32 bit version from my 64 bit dev box yet, even though there's no binaries..

automate install using autoit remotely

I am wondering if I can use autoit to install a package that doesn't have a silent switch to a remote computer. I have the script and it runs the installer on the remote server but it hangs. I have a guess that because I am running the autoit script remotely, it doesn't work because GUI is not provided.
You could use FileInstall(...) to include the program's installer in a compiled autoit script and include your automation that way:
;SCRIPTEDINSTALL.AU3
FileInstall("C:\REMOTEINSTALL\INCLUDES\INSTALL.EXE",#TEMPDIR & "\INSTALL.EXE")
; AutoMagical Installation Techniques Here
Then,
Invoke SCRIPTEDINSTALL.EXE on REMOTE from LOCAL
If you are trying this:
Run AutoIt Script (SCRIPT.EXE) on LOCAL
Invoke Remote Installation (INSTALL.EXE) on REMOTE from LOCAL
And trying to have SCRIPT.EXE pick up details from INSTALL.EXE, then no, this will not work (through any methods I know of). Sorry =(
Lastly, if you mean to ask "do I need to install AutoIt on a remote server to run an AutoIt Script?" Then:
Yes, if you don't compile it to EXE.
If you compile the script, though, it will run on any Windows computer.