Articles Tagged 'profile'

How to set path for local browser and mobile profiles

Since version 6.3 Rapise has support for local browser and mobile profiles. Using it you may package browser profiles along with tests. What if you want to reuse browser profiles between different projects? Or have sets of profiles for different situations? You may now set path to profile directory using a special global variable.  Supported in Rapise 6.4+

How to define a profile for Web Application in Rapise

Each web application is unique in terms of assigning attributes to elements and this complicates the process of generating XPath locators. Some applications assign dynamic IDs to elements, some use ARIA attributes and some do not, some values of class attribute have meaning related to element position and some just used for styling . There are also cases when an app contains hidden DOM layers which stack on top of each other. So usage of same set of attributes for generating XPath is not efficient and may lead to weak locators that break after application reloading or slight modification. To cope with these problems Rapise introduces Web App Profile. It is a simple JSON file of a defined structure that instructs Rapise how to build XPath for elements in a particular application. From this article you will learn how to define a profile for your web application.

Errors occur when trying to attach a screenshot or display "My Profile" page
SpiraTeam uses Java (tm) for attaching screenshots to artifacts and for adding a user logo or avatar on My Profile page.
If a current version of the Java Plug-In is not installed in your browser, problems can occur. Depending
 on your browser, the source of the problem may not be clear.  For example, sometimes IE will report that
 there is a problem with the page. This article explains how to update your browser's Java Plug-In.