Subject7 version 8.16.1 - 10/03/2020

Subject7 version 8.16.1 has the following enhancements and bug fixes:

  • Added a new Get_Desktop_Value command which retrieves values from desktop screens or from your clipboard and assigns a values to a variable. For Linux and MacOS users, some libraries are required for installation and the command will navigate to instructional pages on how to install these libraries. For Windows users, please make sure Microsoft Visual C++ 2015-2019 is installed
  • Added a new Desktop_Clear command which allows users to clear elements on demand using Sikuli locators or by targeting focused elements
  • Added a new Desktop_Shutdown command which is used to enter the names of the applications. Once execution is finished, stopping the test case will close the applications
  • Added a new Desktop_Multi_Action command which is similar to Multi_Action command and allows users to perform more complex operations such as holding Shift on the keyboard and many other operations
  • Added support for file names used in Sikuli locators to appear in cloud run logs
  • Added support to edit the automatically appended names in Sikuli locators after attempting to save the Sikuli locator when the names have disallowed characters like spaces
  • Added a new custom date format under Administration > Account Preferences. This allows users to set a custom date/time format for @test_case_execution_start_date_time and @test_case_execution_end_date_time variables used in Execution Callbacks. For example, “yyyy-MM-dd’T’hh:mm:ss.ms” can be used where T is a constant and produces for example: ‘2020-10-06T09:43:26.4326’
  • Added support in Advanced Commands Editor for Clear option of Fill command. It will now appear as CLEAR_ON_START
  • Added a new column ‘Execution Type’ in Test Case report which is used to show test cases based on how they were executed (through Execution Set or Independently). A new filter parameter has been added as well to facilitate the search process
  • Added a new column ‘Execution Type’ in Steps report which is used to show steps based on how the test cases were executed (through Execution Set or Independently). A new filter parameter has been added as well to facilitate the search process
  • Added new API enhancements:
      • Ability to start independent cloud run for a test case in ”POST /executions”
      • Ability to see which data set belongs to which data template in “GET /test-case-executions”
      • Added a new ‘Type’ parameter which shows results of test case executions by “INDEPENDENT” or “EXECUTION_SET” in “GET /test-case-executions”
  • Added a new test case to ‘subject7_samples’ folder with title ‘subject7_count_profiles’. This test case demonstrates how ‘count’ function is used in a step with Get_Web_Value command
  • Renamed ‘Default’ project name to “Common’
  • Fixed an issue with Execute_Javascript box which was previously enabled when the step is disabled
  • Fixed an issue with View Executions link not working in Executions report
  • Fixed validation issues in Advanced Commands Editor when a step uses more than one data template/data set
  • Fixed an issue with new user creation not allowing to use ‘$’ as part of the password
  • Fixed a search issue with test case search when test case names are entered with a space in the beginning in places such as Execution Set test case selection, Test Plan test case selection, etc.
  • Fixed an issue with Function References throwing an error if the referenced function is located in another folder
  • Fixed an issue with user mismatch on Usage Metrics after creating/deleting users in an account
  • Fixed issues with Desktop Highlight interfering with some elements during desktop test case execution
  • Updated SikuliX to version 2.0.4
  • Updated jQuery to version 3.5.1
  • 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

  • Avatar
    Dominic Luminello

    Hello,
    I find it hard to figure out what changes/features/defect etc. have been made between a major release (ie. 8.16.0) and minor releases (ie. 8.16.1). The release notes look exactly the same. How do I know what is in 8.16.1 and if its worth updating to?

    0
    Comment actions Permalink
  • Avatar
    Joseph Hamdan

    Hi Dominic,
    Apologies for the confusion. Here are 8.16.1 release notes, the rest are all part of 8.16.0 release:

    •Added support to edit the automatically appended names in Sikuli locators after attempting to save the Sikuli locator when the names have disallowed characters like spaces
    •Added a new custom date format under Administration > Account Preferences. This allows users to set a custom date/time format for @test_case_execution_start_date_time and @test_case_execution_end_date_time variables used in Execution Callbacks. For example, “yyyy-MM-dd’T’hh:mm:ss.ms” can be used where T is a constant and produces for example: ‘2020-10-06T09:43:26.4326’
    •Added a new column ‘Execution Type’ in Test Case report which is used to show test cases based on how they were executed (through Execution Set or Independently). A new filter parameter has been added as well to facilitate the search process
    •Added a new column ‘Execution Type’ in Steps report which is used to show steps based on how the test cases were executed (through Execution Set or Independently). A new filter parameter has been added as well to facilitate the search process
    •Added new API enhancements:
    oAbility to start independent cloud run for a test case in ”POST /executions”
    oAbility to see which data set belongs to which data template in “GET /test-case-executions”
    oAdded a new ‘Type’ parameter which shows results of test case executions by “INDEPENDENT” or “EXECUTION_SET” in “GET /test-case-executions”
    •Added a new test case to ‘subject7_samples’ folder with title ‘subject7_count_profiles’. This test case demonstrates how ‘count’ function is used in a step with Get_Web_Value command
    •Renamed ‘Default’ project name to “Common’
    •Fixed an issue with Execute_Javascript box which was previously enabled when the step is disabled
    •Fixed an issue with View Executions link not working in Executions report
    •Fixed validation issues in Advanced Commands Editor when a step uses more than one data template/data set
    •Fixed an issue with new user creation not allowing to use ‘$’ as part of the password

    Regards,
    Subject7 Team

    0
    Comment actions Permalink
  • Avatar
    Dominic Luminello

    Thank you. Is there any easy was to tell in the future what is included in the minor releases?

    0
    Comment actions Permalink
  • Avatar
    Joseph Hamdan

    Hi Dominic,
    We are going to separate every release (including minor releases) to its own page on the Knowledge Base. This should make it easier to read and differentiate the specific notes for every release.
    Regards,
    Subject7 Team

    0
    Comment actions Permalink
  • Avatar
    Dominic Luminello

    Great, thank you!

    0
    Comment actions Permalink

Please sign in to leave a comment.