When using Spira or KronoDesk on a separate web and database server, the easiest configuration is to use SQL Server authentication to connect between the web server and database. However that means hard coding a password in the web server (in the Web.config file). So in this article we explain how to use Windows Integrated Authentication instead.
If you are using older ESET Antivirus products (e.g. v6.x) on Amazon Web Services (EC2) Elastic Cloud Compute (EC2) Windows instances (which we use for Spira and KronoDesk) you may not be able to easily upgrade to the latest version of ESET 7.x because ESET 6.5 will block its own un-installation. We have a solution that worked for us that we'd like to share.
Some test scenarios require running processes as different user or entering user credentials into Internet Explorer security prompt. Rapise can enter user credentials into Windows Security dialog on Windows 10 automatically.
Unfortunately, Windows10 has a nasty habit of frequently updating itself and then breaking existing applications. We found that the February 14th, 2018 Windows10 update corrupted the Excel device driver that Rapise uses to access the RVL test script spreadsheet during playback.
Sometimes when running RemoteLaunch and either TestExecute or TestComplete (from SmartBear) on Windows 8 and Windows 10 will result in an error message being displayed due to the security permissions in Windows 8 and 10:
HRESULT: 0x800702E4 (Requires Elevation)
Sometimes when testing local/desktop applications you need to access the Windows registry to verify that keys exist or that keys have specific values. For example you may be testing that a DLL was successfully registered. This article provides information on the 'UsingRegistry' sample that comes with Rapise.
If you are using Rapise on Windows Vista or Windows 7 it is not necessary to disable the Windows User Account Control (UAC)
to use Rapise. Unlike some other automated testing tools on market, you can use Rapise with UAC enabled.
If you install SpiraTeam or KronoDesk on Windows 8 or later, you need to make sure that the various IIS Roles and Features are installed. If not, you may find that various Menus don't display correctly or that the pages do not display any data. This article describes the features and roles that need to be included.
If you install SpiraTeam or KronoDesk on Windows Server 2012, you need to make sure that the various IIS Roles and Features are installed. If not, you may find that various Menus don't display correctly or that the pages do not display any data. This article describes the features and roles that need to be included.
This article describes how to resolve the following error message that can occur on new installations of SpiraTest, SpiraPlan, SpiraTeam or KronoDesk when ASP.NET is not correctly configured. This message typically only occurs on Windows Vista, Windows7 or Windows 2008 Server.
HTTP Error 500.21 - Internal Server Error
Handler "PageHandlerFactory-Integrated" has a bad module "ManagedPipelineHandler" in its module list.
When using Rapise to record test scripts against Windows, Java, Flex, or other thick client applications that have windows or objects whose names may change in between test runs, you will usually need to make changes to either the test script or the learned objects so that they can match correctly. This article outlines some suggested techniques for recording/playing back scripts against such applications.
When installing Spira on SQL Server 2012 (any edition) using Windows Authentication, you may receive an error message "Cannot Create User" (or similar) during the installation. This is because of a configuration change in SQL Server 2012 (as opposed to earlier versions). This article explains the step needed to prepare SQL Server 2012 for installing Spira v3.x. Newer versions of Spira will not need this step as the installer has been updated.