Subject7 version 7.19 - 12/1/2017 – Subject7

Subject7 version 7.19 has the following enhancements and bug fixes:

VERIFY_ELEMENT command is modified to not select invisible by default
FILL command is enhanced to allow encryption of the data in the wizard itself as opposed to creation of a data template to achieve it
CHECK command issues are resolved
VERIFY_FILE_DOWNLOAD command is enhanced to provide the following:

CLOSE_POPUP command is enhanced to pass the following scenario if the user chooses to do so:

If no popups are found with the text provided in the CLOSE_POPUP command, user can decide to pass or fail that step whereas before this release it was always failing

Browser is no longer launched when there are no web commands in the automated test
Converting Selenese Script to Subject7 Selenese objects is enhanced to cover additional spaces, single quotes, and double quotes
Folder creation capabilities (creation, copy, paste, etc.) are added on the Execution Sets tab
Folder creation capabilities (creation, copy, paste, etc.) are added on the Load Testing tab
Switch Window and Switch Frame commands are added for scripts using Snippets and/or JavaScript
REST API for cloud execution is enhanced to allow selection of browser type, data sets, and pool

Subject7’s user guide available from the top menu (Help -> User Guide) is pointing to HTML pages as opposed to a PDF document
Headless browser for both automation and load testing is converted from PhantomJS to Headless Chrome
Load Testing report allows adjusting column width
Beta version of Subject7 Locator Explorer (a chrome plugin) is developed to perform locator inspection and definition. Here is how it can be installed and used:

Download beta version of Subject7’s Chrome plugin (.crx file) from the link: Subject7 Chrome Plugin. This link will be available temporarily
Go to extensions page of your Chrome
Make sure the Developer mode is checked on top of your Chrome extensions page
Drag and drop the file downloaded in the first bullet above into the extensions page
Click on the “Add Extensions” button on the popup presented
Subject7 logo should appear on the top right corner of your Chrome browser where all the plugins are shown
Click on the Subject7 logo
Provide the host (your Subject7 instance URL), username (your Subject7 username), and password (your Subject7 password) on the extensions page that appears and click on Save
Locator Configuration is saved message pops up. At this point your Subject7 Chrome plugin is available to be used
Close that browser tab where you configured the Chrome extension
Open another tab and go to the URL of your application under test
Click on Subject7 logo again
A popup appears with the message “Locator Explorer is enabled”
Start clicking and typing on and into the widgets that you want to define
A popup window is presented to accept the hint.

Hint can be the label of the field displayed on the screen, tooltip, etc.
Leave the distance as is
If your application widgets have static id’s, select the “Include ID Attribute” checkbox

Provide the page name, type, and alias
XPath should be populated by the plugin
Test XPath button highlights the widget that is identified by the generated XPath so that you can make sure the right widget is identified
Click on “Push to Server” button which will save the locator in the locator repository of the Subject7 instance you have configured earlier

Keep defining all of your widgets of interest this way
Login to Subject7 and using wizards, write your automated tests using the locators/widgets you have defined via the Locator Explorer

Go to Administration top menu and then Project Management submenu
Define all of your projects on the left panel of the tab opened
Define all of the features of each project by selecting the project on the left panel and defining the features on the right panel
Define sub-features for each feature if needed on the right panel
Click on each feature and click on the “Map Test Cases” icon for that feature to map any of the test cases to that feature
When ready to generate the coverage report, click on the Report link and provide the number of test cases that are needed to satisfy the coverage for each feature and then click on Show Coverage link
The generated report displays what the coverage percentage is for each feature. The ones that do not have the proper coverage will be listed in a table

@System.empty and @System.null constants are defined to facilitate comparing variables with an empty string or a null value respectively
508 compliance addon is enhanced to cover some missing scenarios
Test Library tab of Execution Set wizard allows filtering of the test cases on the tree view presented
Side by side test case execution comparison is added. Following steps are needed to do this:

Select Reporting from the top menu and then Test cases
From the listing that is presented, click on “Add to compare” icon under Actions column for as many test case executions that you would like to include in your comparison report
A compare window shows up on the lower right corner of the Subject7 application with a compare button
When you are done selecting all of the test case executions to compare, click on the Compare button, and it will show you all of the selected executions side by side

High level summary cloud execution report is added to show a summary of all the cloud run passes and failure at the suite level. Following steps are needed to do this:

Select Library from the top menu and then Test Library
Select the folders or suites that you would like to be included in the summary report
Select Summary Report from the menu under More
Suite Summary report is presented on a different tab
You can use date filters to look at the summary report in a specific time frame