Articles Tagged 'internet'

In situations where your SpiraTest, SpiraPlan or SpiraTeam server is located on a company network that does not have direct Internet access (and connects through a proxy server), some of the integration features of Spira may not work correctly:

• The weather widget on the My Page
• The list of recent builds if your Jenkins server is hosted outside your network
• The RSS feed widgets on the My Page
• Data synchronization with bug-trackers that are externally hosted

This article outlines the step necessary to tell the Spira server to use the proxy server for its Internet connections.

Article can be considered as obsolete.
Described fix applies to outdated versions of the application only.

A couple of our customers have run into a situation where the new font-based glyph icons that we're using in Spira 5.0 don't display. This is usually due to a configuration issue within IE itself, this article provides the recommended solution.

When you are testing a web application that has popup windows (where the popup is a whole new browser window) you will need to make a slight change to the test script to enable it to playback successfully in Internet Explorer (no change is needed for Chrome or Firefox).

When writing a web test in Rapise you will often want to run the same test script in all three web browsers (IE, Firefox and Chrome). You will want to be able to choose the Test Script from within Rapise when debugging the test and then from a Test Set in SpiraTest when you move the test into production. This article explains the process.

This article is obsolete. For modern way of running Rapise tests in multiple browsers please refer to Rapise 8.0: how to run test cases on different browsers.

If you have disabled TLS 1.0 and 1.1 encryption protocols on your IIS web server, you may run into issues accessing the web interface of Spira or KronoDesk from older versions of Windows and/or IE.

An old (December 9th, 2014) security update for Microsoft Windows and Internet Explorer (KB3025390)  broke the support in IE for 'out-of-process' code execution. This effectively prevented an automated testing application such as Rapise from automating Internet Explorer (IE) applications. This was subsequently fixed by Microsoft on February 10th, 2015 with the KB 3021952 update.