Articles Tagged 'har'

It is common for test scenarios to share similar pieces of functionality. A good example of such sharing is login logic. This guide outlines ways in which you can share such logic to avoid having repeated code in your tests.

This article is obsolete. To find out about re-using test parts, modules and page objects please refer to Rapise 8.0: how to use Page Objects/Modules.

Sometimes, when troubleshooting complex issues with SpiraTest, SpiraPlan, SpiraTeam or KronoDesk, it's necessary for us to get some additional information to troubleshoot the issue further. For example, when we receive a report of performance trouble when using our cloud services, there are a lot of different factors that may contribute to the problem. To narrow down the cause of the performance problem, we need more data.

If you are running a web application (such as SpiraTest, SpiraPlan, SpiraTeam or KronoDesk) on an IIS web server using Secure Sockets Layer (SSL), you will want to harden the environment by removing the older versions of SSL and TLS that are no longer considered secure.

These steps apply to:

• Windows Server 2003 R1 & R2
• Windows Server 2008 R1 & R2

Usually Windows Server 2012 and later are already configured to be secure.

One of the challenges using an automated testing tool is to organize things in a way that it is logical enough to find something quickly, structured enough to avoid duplication and simple enough to maintain and upgrade.

This statement is also true for Rapise objects. A common requirement is to deal with the same objects within a flow of different test cases. For instance, if an application has “Log In” functionality then many, many tests will require logging-in and logging-out. Each test will have this object in its own object tree. However this causes trouble if a change in the application affects the recognition of the Log In object. All of the test cases will need to be updated. In such situations it is much more convenient to have the “Log In” objects placed into their own file and re-used by other tests.

This article is obsolete. In Rapise 8.0 and above the recommended approach is to use Page Objects / Modules.

Custom graphs let you see powerful and meaningful summaries of your data. One example of this is seeing how many requirements or incidents were delivered historically, broken down by the year of their release. In this article we will show you how to create such a graph to help Product Managers see delivery over time, to help them assess and manage their current and future work program.
 

Sometimes when using RemoteLaunch with a specific plugin (e.g. Selenium), you may get an error such as:

Could not load file or assembly 'WebDriver, Version=2.44.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.

The way to debug this kind of error message is to enable Microsoft .NET Fusion Logging to get more information as to which dependency could not be loaded. This article explains how to turn this on.

If you are running Rapise and you suddenly start to find that none of your recordings get saved and the reports are not displaying during execution it may be due to the fact that you have saved your Rapise test folder onto a Network Share.