Subject7 version 7.13 - 04/23/2017

Subject7 version 7.13 has the following enhancements and bug fixes:

  • Load Testing: added browser, timeouts, and VM capacity to the load testing report
  • Load Testing: Added the ability to distribute the load to multiple virtual machines
  • Load Testing: support for functions is added
  • Manual test case edit page is switched back from popup to tab
  • Manual test case: when adding the manual test case results, if the entire test case is being marked as PASS, all individual steps are marked as PASS. As individual steps of the test case are being marked as PASS or FAIL, the test case status automatically gets updated to PASS or FAIL accordingly
  • Notification email subject line is changed to include PASS/FAIL/FAIL_SKIP for easier access to the final test case status
  • Increased the size of EXECUTE_SELENESE text area
  • Fixed a defect with BOOLEAN usage inside IF
  • Data template support for REST URL is added
  • Added the ability to alphabetically compare 2 strings in the COMPARE method
  • Added a new command called HOTKEYS to the wizard allowing some hot key interactions such as escape and CTRL+F5
  • RefID is added to the execution report PDF and Excel exports
  • Added inline help for SET_DATE command
  • COMPARE command is enhanced to handle larger integer values
  • Cancelling a cloud run was marking the test case as PASS, it is changed to ERROR
  • FILE_UPLOAD command populates the newly uploaded file automatically in the wizard
  • When cloud run failure is due to locator not found, a link to definition of locator is available in the report for easier modification
  • Ref ID search is added to test case filter
  • Selected data sets, failed step number, failed step, and reason for failure are added to the notification emails
  • JIRA-integration enhancements:
    • Ref ID is added to test suites. This will be served as the parent of any subtasks created under this suite
    • JIRA ticket creation is added to the test case edit page and allows subtask creation
    • If Ref ID for the test suite is populated, and a JIRA subtask is created from the test case edit page, the parent ticket will automatically get populated from the Ref ID mentioned in the suite of this test case
    • JIRA ticket creation icon is added to all steps of execution set report
  • Some other minor enhancements and bug fixes.
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

Please sign in to leave a comment.