Subject7 version 7.17 - 09/18/2017

Subject7 version 7.17 has the following enhancements and bug fixes:

• Function creation through grouping of steps is fixed
• EXECUTE_SELENESE command is enhanced to cover additional edge cases
• Compare wizard is enhanced to allow empty strings
• Functions in cloud reports are collapsible similar to local run
• Desktop menu titles changed to Sikuli
• References option is added to the edit function page
• DRAG_AND_DROP command is enhanced to support HTML5
• Execution records are archived after 30 days
• Subject7 Jenkins plugin is enhanced to allow triggering of multiple comma separated execution sets
• Added total row to usage metrics report
  • Go to Reporting -> Proof Usage Metrics
  • A new row is added at the end of the metrics table that sums up the numbers on each column

• File upload allows multiple files to be uploaded together. This helps a lot with Sikuli automation.
  • Go to Artifacts -> File Uploads
  • Click on Multiple File Upload
  • Select more than one file to upload

• REST functionality:
  • VERIFY_REST command is enhanced to allow checking of multiple value pairs in the REST response. If all but a few of the value pairs are successful, the return message points out the few value pairs that are failing the check
  • SET_REST command and REST connection headers are enhanced to take any var or template value in the header with any required random header key
  • REST commands are enhanced to keep the response status. This response status can be used in testing logic afterwards
  • JSON response validation against RAML files is added

• Load testing: the following REST API’s are added to support load testing
• Execute Test Plan (POST)
  • http://{server}/api/v1/executionService/onDemandExecution/testPlanName/{testPlanName}{?delay=123}.
    • server is target server name, e.g. proof.subject-7.com
    • testPlanName is name of the test plan, e.g. my_sample_test
    • delay=123 is optional parameter, where 123 is time (in seconds) to delay before message is sent

• Check test plan execution status (POST)
• http://{server}/api/v1/executionService/load/executions/{testPlanExecutionId}
  • server is target server name, e.g. proof.subject-7.com
  • testPlanExecutionId is test plan execution id which can be taken from response to Execute Test Plan call
• Get Report
• http://{server}/api/v1/executionService/reports/load/executions/{executionId}
  • server is target server name, e.g. proof.subject-7.com
  • testPlanExecutionId is test plan execution id which can be taken from response to Execute Test Plan call
• Get Report in special format
• http://{server}/api/v1/executionService/reports/load/executions/{executionId}/{format}
  • server is target server name, e.g. proof.subject-7.com
  • testPlanExecutionId is test plan execution id which can be taken from response to Execute Test Plan call
  • format can be either HTML or JSON