June 28th, 2021 by inflectra
Two of the major features in our most recent release of Rapise are the completely overhauled Spira Dashboard and the new support for handling the bane of test automation engineers everywhere - flaky tests! In this article we shed some light on the new dashboard in Rapise 7.0.
Before we look at the new Spira Dashboard and how it works, first lets take a trip back in time to the original Spira Dashboard:
The original dashboard let you connect Rapise to Spira and display a list of the test cases and test sets in the current project that were either assigned to the current user or were assigned to the automation host that Rapise was running on. However, it was a bit cumbersome to use and had lots of separate boxes and sections. In addition, it used the older Spira SOAP API and was relatively slow to navigate and display content. With those limitations in mind, with the launch of Rapise 7.0 we now have a completely new Spira dashboard:
The new Spira Dashboard has a completely new user interface and style that more closely mirrors the 6.x version of Spira.
The new Spira Dashboard has a fast, easy to use navigation bar that lets you change Spira product as well as access the different parts of the dashboard in one click.
The dashboard contains top level menu to switch between views and a dropdown to switch between products/projects. There is also a button to refresh data and search field to filter data in the current view. Filtering is applied to a column with orange caption (usually
In many cases first column of a data table contains ID of an item in Spira. You may click an ID to open the corresponding item in a browser window.
Each data table has a menu opener (hamburger) located in the top right corner. The menu contains some predefined filters and also allows you to display the filter row and choose which columns to show. Clicking a column caption turns on sorting.
The Plus icon in a table row means that it can be expanded. Click the icon to reveal the row details. It may contain more data tables.
Test cases and test sets may be placed into folders in Spira. The dashboard will load and display the folder hierarchy. To navigate it click on the folder icons.
Some tables include an
Action column. It allows the user to perform certain actions on an item displayed in the row when the
Action menu is expanded.
Here is the list of tasks you may accomplish with the new Spira Dashboard:
If you did not connect Rapise to Spira yet, you will be prompted to enter the connection info.
If you did not assign an automation host token to the machine where Rapise is running you may do it in Automation Hosts view. You may even create a new host there.
The dashboard view shows tests included in the currently opened test framework (parent test and it's sub-tests).
View test runs that are in progress right now.
View tests that are scheduled to run on the local host for the next 24 hours.
Some features of the dashboard require aditional custom properties to exist in Test Cases, Test Sets and Test Runs. Click
Create Custom Properties for Rapise button to add the following custom properties in the selected project:
Clicking the button more than once is safe. If a custom property exists - Rapise won't create a duplicate. To create the custom properties you will need to enter administrator credentials (user name and API Key).
Action menu for a test allows to
This view displays scheduled test runs that must be executed within next 24 hours.
In the test cases view one may see the tree of test cases for a project, discover when a test case was last executed and status of execution.
Expanding a test case reveals last 10 runs of it. The details pane also shows test case parameters and custom properties (editable).
Action menu for a test case allows to
Executethe test case on the local host.
Executethe test case on a selected Automation Host. It will run as soon as RapiseLauncher on that host is ready.
Flakyor remove the flag.
For execution of a test case on a selected automation host (#2) - Rapise will use a special test set with the name of the automation host.
If you want to create a test case in a specific folder - select corresponding row in the table, otherwise the test case will be created in the root folder. Click the
New Test Case button at the bottom of the view and provide necessary details in the opened modal dialog.
In the test sets view one may see the tree of test sets for a project, discover when a test set was last executed and status of execution.
Expanding a test set reveals the list of included test cases. The details pane also shows test set parameters and custom properties (editable).
Add Test Cases to open the test cases tree, select test cases and append them to the test set.
Using hamburger icon next to a test case ID one may reorder test cases in a test set.
Action menu for a test set allows to
Executethe test set on the local host.
Executethe test set on a selected Automation Host. It will run as soon as RapiseLauncher on that host is ready.
Rerunjust failed test cases on a selected Automation Host.
For execution of a test set on a selected automation host (#2,#3) Rapise will use a special test set with the name of the automation host.
If you want to create a test set in a specific folder - select corresponding row in the table, otherwise the test set will be created in the root folder. Click the
New Test Set button at the bottom of the view and provide necessary details in the opened modal dialog.
This view shows most recent test run reports. One may see test run status and execution time and duration. If a test run is failed - Details column displays the first error message.
Expanding a test run reveals the report with execution status for every test step. The details pane also contains links to download test run attachments and execution log.
This view displays last 500 incidents and allows to create new ones.