32.9 OpKey Release – 5.52

New Features

Introducing Pre & Post Test Execution Report(Beta) feature

OpKey has now been added with an all new advanced feature, Pre & Post Test Execution Report. This feature allows you to export Pre as well as Post execution report of the Test Case and Suite. You can upload your sample report(s) template to the selected project from the Upload Templates tab in Reports under the Project Management of OpKey Admin. Later, you can update, export and delete the uploaded report as required. You can download Sample Template for your reference by clicking on the Download sample template button. Pre execution report feature allows you to generate a report of your test without doing the actual test execution of the flow.

There are some System Fields showing in System Fields tab in Admin under Reports in Project Management. These fields are the unique fields that can be added in the sample report to be uploaded which results filling of respective test data in the mapped fields in the Pre and Post execution reports. You can add your custom field tags from the Custom Fields tab in the selected project. In order to generate Pre-Report, open your Test Case, click on Run Now and then select Pre-Report option. Enter Report Name, select Agent, Report Template, Steps Hierarchy, Format, Report Logo and click on Next. Once the Pre-Report is generated, you can download it from the Pre-Reports tab under the dockable panel to view and analyze. Pre Execution Reports contains a table with few columns like S. No. Test Step Description, Expected Result, Actual Status, Comments and Date, as per the selected sample report. It contains another table in the bottom named as Revision History which contains information about the Test Case & Suite like Created By, Authored By, Reviewed By, Approved By & Published By.

To generate Post-Execution report, click on the Execute under the Run Now button. Check Show Advanced Settings checkbox in Local Execution wizard and click on Next. Navigate to the Advanced Execution Settings and check Post Execution Report checkbox and click Next. Next step opens Post Report Settings (Beta) page which allows you to select Template, enter Report name, select Snapshot, Steps Hierarchy, Report Logo and then click on Next. Follow other steps to start test execution. Once the test execution gets completed successfully, click on the Export Report, select Post Execution Report and export it to analyze the Post execution report. Post Execution Reports contains a table with few columns like Step No, Test Step Description, Expected Results, Actual Status, Snapshot, Comments & Date, as per the selected sample report. It contains another table named as Revision History which contains information about the Test Case & Suite like Created By, Authored By, Reviewed By, Approved By & Published By. It contains another table in the bottom named as Revision History which contains information about the Test Case & Suite like Created By, Authored By, Reviewed By, Approved By & Published By.

Note: System Fields (like Test Script ID, Test Script Name etc.) where Test Data is filled in reports, must be mapped under the Test Procedures Table in the uploaded sample report.

Maker Checker Feature Enhancements

There are some significant enhancements in the Maker Checker feature. There were only two states Draft and Published earlier but two new states Review and Approved have now been added in this OpKey Release. Thus, there would be total 4 states named as Draft, Review, Approved and Published. When your file is in Draft state then it can be edited by any user (Admin or Non-Admin) but when state gets changed from Draft to any other states (Review, Approved or Published) then the file will get freezed (locked) and no further editing can be done by the user (Admin or Non-Admin) in that state. However, Admin user can change its state to Draft and then further editing can be done.

A non-admin cannot change freezed (locked) state (Review, Approved or Published) of the file while an admin user can do that. If state of an upper artifact/file (like Suite) file is being changed then the state of all the mapped lower artifacts/files (like TC, FL, OR, GDR etc.) with Suite will get changed automatically. If there is a Function Library file which is already mapped with a Test Case and you are adding/editing Input Parameters & changing the state of Function Library file then State of the Test Case (in which that Function Library is mapped) will get changed as per the final state of the Function Library.

In addition, you can add your own States at Project level from the Manage State tab under the Project Management section from OpKey Admin Panel. Draft, Review, Approved and Published states are System Defined and cannot be modified and deleted. Review, Approve and Published state will lock files and only Admin will have rights to unlock them. Name of the newly added States (User Defined) cannot be matching with the System Defined state (like Draft, Review, Approved or Published) names. If you have your existing User defined states with the same name matching with the new System Defined state (like Review & Approved) names added then any changes in States results locking of the artifact/file as per the rule of System defined states.

Note:

  • If there is an existing artifact in Published state (created in earlier OpKey builds like 5.51, 5.50 etc.) then it will be editable (behaves like a Draft state) but once the state gets changed from Published to Review or Approved state then the artifact will get frozen (locked) & no further editing can be done, as per the new rule of OpKey build release 5.52.
  • If there is an existing artifact in Published state (created in earlier OpKey builds like 5.51, 5.50 etc.) then it will be editable (behaves like a Draft state) but when the state gets changed from Published to Draft and then Draft to Review, Approved or Published state then the artifact will get frozen (locked) & no further editing can be done, as per the new rule of OpKey build release 5.52.

Introducing “Replica” feature at OpKey Test Accelerator platform

Now, OpKey Test Accelerator users can make replica(s) of their files or folders on same or different domain in different project. You can make replica of the exported and copied file. You can right click on the file, copy the file and then right click on the folder and select Replica option. You can right click on the file, select on the export option to export the file. Once its successfully exported in compressed form, you can later make a replica of the exported file while choosing Import option.

Now you can import exported artifacts of OpKey Web and make Replica in the OpKey Accelerator platform. Here, a new folder (named as Dependencies) is created in Accelerator which contains the dependent files. If there are OpKey Web components (like TC, OR. GDR, SR etc.) then they will be hidden in the Accelerator platform. Only Function Libraries (FLs) of OpKey Web, which are equivalent to the Business Components (BCs) of Accelerator will be visible in Accelerator end. In addition, a copy of the imported file folder through replica, will be created at the OpKey Web in Project Workspace. It contains all the imported files through replica.

Similarly, when you make a replica of the exported Accelerator folder in OpKey Web then a new folder named as Dependent_Artifacts will be created in Project Workspace in OpKey Web which contains the replica files. As Business Components (AC) of Accelerator are equivalent to the Function Libraries (FL) of OpKey Web so created replica of AC will be visible in the OpKey Web but other replica components of the Accelerator will be hidden in the OpKey Web. In addition, a new folder named as Dependencies, will be created at Accelerator end which contains the newly created replica files.

Introducing “RestoreTo” feature at OpKey Test Accelerator platform

OpKey Accelerator users can now create a backup of their Business Components (BCs), Business Processes (BPs) and Test Cases (TCs) and make required changes to them. In case you want to restore their backup copy then you can easily restore desired backup version in the desired folder. To create a backup copy, click on the Create New Backup button. Navigate to the dockable panel and click on Backup to have a look. You can make various copies of the backup. In order to restore it to the desired location, click on the RestoreTo button, choose folder and restore it. You can restore the backup file and replace the current file.

Other significant feature enhancements

  • Now, there is a Run Now button which contains options (Execute, Debug & Pre-Report) to can be used for execution in normal mode, debug mode and generate Pre-Report respectively. Pre-Report option is enabled only in Test Case i.e. Pre-Execution report can only be generated for the Test Cases.
  • Now, Local Execution Wizard has a new step (Plugin Settings) from where you can apply Plugin settings and save them for further test executions.
  • Performance of the overall test execution, using supported plugins, has now improved significantly.
  • Now, you need to instrument your existing APK files to automating your mobile test flows as there are some enhancements from Plugin side.
  • There is a new mobile keyword Mobile_SwitchDynamicLoading has now been added and it allows you to apply wait until the page gets loaded. It takes True/False as data input arguments. If you have provided True then it will wait for the page load whereas for False data input argument, it will not wait for page load.

Note: You are recommended to download & install latest released OpKey Agent for test execution.

Major Bug Fixes

Known Issues

Article

No items found.