We are trying to automate the installation testing using UFT.
But, UFT is not capturing the installshield screens when we click on record.
Any suggestions?
It is just showing empty test case when we click on record.
Even manual creation of scripts also not showing.
Installshield setup.exe uses internally msiexec.exe.
Does it effect anything as the background process name is changing?
Have you selected Record and run test on any open Windows-based application in the Record -> Record and Run Settings?
If you have and it still doesn't work, it may be that the installation is running in a higher security level than UFT.
You could try using UFT's Insight option in order to work around this.
Related
I use squish for testing and it doesn't close the tested application correct always.
In that case office (Word, Excel, PowerPoint) starts with some recovery options (previous documents getting restored, some dialog windows appear, etc) I need to reset the status of the application before the start of new test.
Isn't it better to close the Office application properly?
For example, you could automate Office application using Automation. The recovery options mean the host application was not closed gracefully or something unexpected happened with it (crash?). So, I'd recommend asking squish developers what is wrong with their software other than looking for a workaround to suppress evidences.
I am working on Win 10 upgrade activity. As you know we can select application for file extension. So, those file will open on that app. e.g. html files only open in Chrome when user double click on that.
We can create XML file (DefaultAppAssociations.xml) and place it in C:\windows\system32
Now, I got the request to make one application default but let user decide if they want any other app. Is there any way to handle such things because defaultappassociations.xml will hard code this. Every time machine restart and it will set the same.
This is only possible as part of the operating system deployment or rather for newly created user profiles.
The command (official documentation):
Dism.exe /online /Import-DefaultAppAssociations:<path to exported xml>
However as I said you cannot alter existing profiles that way. Altering existing profiles in any way that is not the force via gpo is afaik not possible anymore because Microsoft does not want to allow it. A pretty stupid decision but at least you can tell whoever made the request that it is by MS design.
Using CAML or some other query system, how can I find items that use custom code and organize by modified date?
And the background. My group is looking to upgrade a 2007 SharePoint installation to SPO. The problem we're having is a lack of clarity as to what on the site is junk and what is a custom code set. The first idea was just to run through manually and make note of every node. As there are 5,200 nodes, this is pure insanity. I've done some research to find that CAML is how to query a particular site in SharePoint, however I cannot seem to figure out how to query everything at the same time.
I tried to make a view in the root, but again, it only queries the particular level you're on. I'm having the feeling that I might need to write a tool for this and spider the site, but am unsure where to begin. After trying a couple of tools (Stramit Caml running in visual studio and SPUD) I seem to be running in place as I don't understand how the connection works.
Any advice or stories like this?
To scan your environment and detect where custom solutions are used, your best bet is to use the stsadm command called preupgradecheck. This is executed from the commandline on one of your web front end servers, invoking stsadm.exe.
From Microsoft:
The Stsadm command provides a rule-based scanning operation to determine whether servers in an existing SharePoint environment meet the core requirements for upgrading from Windows SharePoint Services 3.0 and related products to future releases of SharePoint Products and Technologies.
The pre-upgrade scanning and reporting operation is implemented as Stsadm –o preupgradecheck, and can be run with or without parameters.
Upon execution, the command checks your environment against various rules. The result of each rule check is written to both an XML log file and a text log file, located in the the %COMMONPROGRAMFILES%\Microsoft Shared\web server extensions\12\LOGS directory, and when the command finishes it will display an HTML file in the default web browser summarizing the results.
I created a setup file for my project with advanced installer but when i try to uninstall the package from control panel i don't see any dialog showing up telling me that uninstallation is a success, it's just run, uninstalling the application and then close. how can i add a dialog to show after uninstallation process?
I'm using advanced installer 12.3.1 and I'm using a custom theme if that is relevant to the question.
It's because your MSI uninstallation through Control Panel goes in Basic UI mode.
There are several ways to do what you want:
If you need simple end success or failure dialog:
you need to create a custom action which will change INSTALLUILEVEL to INSTALLUILEVEL_BASIC and INSTALLUILEVEL_ENDDIALOG. Please refer these links to find more information about it: MSDN and MSDN
The second way is a trick to hide Uninstall button from Add\Remove Programs and left only Change button. Then you need hide Change and Modify buttons from Maintenance dialog window in AdvancedInstaller (InstallShield, Orca, InstEd, etc). In this case you will receive uninstallation in Full UI mode.
I am trying to give my users the ability to select the drive they want to load our software to. Instead of just giving them the InstallChangeFolder dialog I am attempting to just list the drives that are available to load on. I have done this in an InstallScript project before but now we are trying to move to MSI. Basically the flow will be they select the drive and then we append our root path to that drive. Does anyone know of any good tutorials that would explain how to create a custom dialog for changing the installdir and wiring up in all of the custom actions and sequences. If it matters I am using InstallShield 2013 and a Basic MSI Project
Why do you want to hardcode your installation path? That seems like enforcing bad design decisions on your customers.
The default method of allowing the user to pick the installation path is the standard method, for a good reason.
I agree hard coding the path is a bad design, however in order to achieve what you want just create new custom action by going through custom action wizard selecting installscript file, copy your code of install script and add place newly created custom action in the correct sequence.