The following new features have been implemented in this release of Opkey Web:
In this release, we have come up with a one of its kind feature, a new portal called Marketplace, which will be integrated with Opkey, where our developers will be able to utilize the addons through the Marketplace at our Opkey portal. The Marketplace portal is comprised of various addons which are uploaded by Opkey users and developers.
These addons will be beneficial for our OpKey users who can subscribe to the addon and successfully use its features as per their requirements. If in the future, the user doesn’t want to use that addon, then they can unsubscribe to it. The portal comprises of various category of addons which is categorized as Top Rated, Top Liked, there are Free and Paid add-ons also. For now, it is not accessible for all users, however very soon we are going to give rights to users outside of Opkey to visit the portal and upload the addons.
How to use the Marketplace Portal
The user will have to log in to the Opkey portal and can click on Manage Addon in the left ribbon to visit the Marketplace Portal. Else the user can directly login to the marketplace portal to use its features.
The Marketplace is open for only Opkey users as of now.
To use an “Addon” from the Marketplace portal, the user will have to “Subscribe” to it. Post subscribing to the addon, the user will have to navigate to OpKey Web or Opkey Surge portal where they can view the option of “Addon Launcher”. The “Addon Launcher” helps to launch the addons.
The Addon Launcher will display all the addons to which the user will subscribe on the Marketplace portal. The user can view and utilize those addons as per their requirement.
Add On Launcher
The add-on launcher is placed on the left-side panel which displays the addons that are subscribed. On clicking the Manage Addons link, the user will be redirected to the Marketplace portal.
We can use two categories of addons from the addon launcher. Those are of “Utility” and “Workflow” type. The “Keyword” and “Test Accelerator” types will not be displayed on the add-on launcher. The list will only display 5 addons and the rest will be displayed in the “View All Addon Link” The keywords will get added in the keyword list when the user subscribes from the Marketplace portal.
There is a Manage Addon tab, which comprises of Subscription, and Developers Workspace tab. The Developers Workspace tab will be visible only to those users who will be granted the rights to upload the addons in the Marketplace.
Under the subscription tab, the user will be able to view all the addons which have been subscribed. The next tab on the timeline will display the “Version” of the addon. The user can have a look at the versions and subscribe as per the need. If the user subscribes to the old version, they will get to view the button of “Upgrade to Latest Version”, which will redirect to the addons version list page, from where a user can subscribe to any version according to their need.
There are basically four types of Addons which we are providing namely:
For now, we are supporting Keywords, Utilities, and Shared Workflow Addons. Test Accelerator Addon will be launched soon.
Keywords – In this type of addons there will be keywords that will be developed to create scripts.
Test Accelerators – The developer will upload the exported Opkey script in the category of test accelerator for others to use it. Users can subscribe to the addon and use the script on their project or on their domain for their requirements. This eliminates the time taken for every user to write the script.
Utilities – These types of addons are built for extra functionality and they are of a miscellaneous kind.
Shared Workflow- A workflow addon is a combination of “States and Transitions” where users can either add “By-Default States” (Draft, Review, Approve and Publish) or the “Customized States” which they wish to add. By adding those States, through Transitions we depict that the particular file or artifact in Opkey is in which state. The transition helps the user know from which state to which state it can be moved. This Workflow typically represents the lifecycle of a process within an organization. The Workflow can be associated in a different manner for individual projects. Additionally, we can define separate workflows for specific modules, within the same project. To be more precise, the user can define three different workflows for an “Object Repository”, a “Test Case”, and for the “Suite”. Workflow 1 can be defined for an Object Repository, Workflow 2 for a Test Case, Workflow 3 for the Suite, and so on. It is created by the user as per their need.
The Default Workflow Addon of Opkey which we are providing to the user can be used directly or they even can customize the Workflow as per their requirement for their Projects and Modules. The rules and properties, or transitions of Default Workflow can only be viewed and are not editable. The user can add Workflows as per their requirement, create rules and change the properties. The user can create customized workflows which they’ll be able to edit.
Now with the new feature of SMTP settings, users can customize the subject line of the SMTP by selecting the various checkpoints included in this feature. The subject line will be framed according to the check box which the user selects.
Custom Logo in Opkey execution result
With the new feature, the user will be able to select the logo as per their choice in the admin panel. For all the external tool integrations the logo will be selected as per the requirement of the user.
The user will have to go to the Admin Panel and click on Project Management. On selecting the “Project” tab, whenever we create a new project, there will be an option of “Default Report Logo”. The user will have to upload the logo and save it. The selected logo will be displayed on the external tool reports.
Jira on Premise
With this new feature, the user will launch the utility on their Jira on-premise. The user will add the domain of Opkey which needs to be connected, fill in all the details of “Domain, Username, Password, Client Name”. Post connection, the message will be displayed as “Successfully Launched”. The user can Connect and Execute the run.
The utility can be connected with one domain with only one single user. If the user wants to connect to a different environment, the user will have to logout from the domain and log in again to the one which needs to be connected.
If the existing users want to access the utility, the user can check the box of “Use Utility” on the Jira window and proceed.
The Summary Report will now have a count of the total number of Passed, Failed, Skipped Over, Incomplete, Not Executed, Steps for the entire session. This report will be also applicable for Agent Side. (Detailed, Integrated).
Opkey Portal Performance
The time taken to load the Opkey portal will be reduced by a good number of seconds after the changes.
Implementation of Chromium Edge Browser in Local Execution Wizard
We have included Microsoft Edge as an additional browser in the Local Execution Wizard along with Chrome, Firefox, and Internet Explorer. When the user executes the run through Spock Agent, they will be able to view the above four options as Browser to choose from and can select Microsoft Edge as their browser.
When the run is executed, the details of the Browser gets reflected as Edge. Users can also generate Validation Reports through the Browser.
Removing Desktop Mode from the Agent
“The Desktop Mode” button which was earlier present in the UI of the agent is now being changed and now only the “Web” mode will be operational. The button has been removed from the main area as well as from the right-hand side corner. Desktop mode is useful only for the Spock Agent as it runs only on the desktop mode.
While launching the agent, a message was being displayed for “Current Mode”. It has now been changed to “Mode” which notifies of the existing Web Mode.
The notification next to it which says “Agent can be connected in two modes” has been completely removed from the display notification.
Admin Password in local Opkey Hosting
The new feature allows the user to update the email address to be able to change the password of the admin user, which does not have the username as its registered email address. After the user logs in to the portal and visits the profile page, the user will get the option of “User Id” as blank, if the login is from “Admin” or if the username does not consist of an email address.
If a user wants to change the password, this feature will allow to enter the email address and enter the password to be changed along with the previous existing password. Once updated, the user will not be able to log in again from the “Admin” panel. Users trying to log in will move ahead from the username that will be “Email Address” and the newly created “Password”. The password can be renewed later when required but the email address can’t be changed as it gets freezed.
Result/Session Metadata Information
The new feature allows the user to view the metadata information even if the session/result gets deleted from the execution result in Opkey. From the execution result, the user can view the Metadata Information, by switching through the toggle button, where a new tab is opened of the MetaInformation Execution Dashboard. This tab will display the list of Builds and Sessions which has been deleted and non-deleted ones. The MetaInformation of the session is shown when the toggle bar is changed.
The session can be deleted from the Execution Result but it will not be deleted from the Meta Information Execution Dashboard. The deleted session will be in “Red Colour” which notifies of the “Deleted Sessions”. And the rest are not deleted. Now the user will have the Metadata Information of both the deleted and the non-deleted ones. If the user wants to delete an undeleted session permanently from the MetaInformation Execution Dashboard, then a notification will be displayed asking to get it deleted first from the Execution Result. To view the result of the undeleted session, users will have to right-click on the “View Execution Result”.
The filter to download reports of the MetaInformation for the Created Sessions, Details, etc can be done for a maximum of 3 months in a row. On running the search button, all the Builds and Sessions run during the defined period will be displayed below. If the user wants a complete report, then it can be done by clicking on the “Download Report”. To view the MetaInformation of any one of the Builds, the user will have to select the particular Build from the list or from the “Box” which gets auto-populated. That particular build will be displayed on the UI with the help of expanding and collapse button. Users can then download the report of all the sessions present in that build. There is also the option of checking the box of the particular session of which the Report can be downloaded by clicking on the “Download Button”.
If the user wants to access the Metadata Information through API, the user will have to input data of the Build name at Postman and fetch information. The same task can be done through API of fetching MetaData Information.
Meta Data API’s
GetAllMetaDataSessionofBuild- On entering the Project Name, Build Name, and Session Name, this API will fetch all the Sessions and their Metadata present in that Build, which the user will be able to edit.
GetAllMetaDataBuild- On entering the Project name this API will fetch all the Builds and Sessions present in that specific Project in the Execution Result from Metadata.
Get Session Metadata of ProjectName- On entering the Build Name, Project Name, Session Name, this API will fetch all the specific sessions Metadata present in that particular Project.
MetaData Search Session- Recent Used Metadata
On viewing the execution result, the user will be able to view 50 builds at a time. To view more, the user will have to click on the Lazy Loading. The Recent Used Metadata feature lets the user view the recently used Session, which otherwise makes it time-taking to locate the session manually. The last ten worked upon sessions gets saved in the Recent Used Metadata. This feature is now only implemented for the Opkey Saas.
Automatic Result Deletion
The new feature allows the admin to automatically delete the result rather than manually clicking on the specific results, checking the boxes, and deleting. The user can visit the Admin Panel where three buttons will be present of “Edit, Stop and Delete” and there will be rules to go ahead with as per the requirement. When the user will specify the Start and End Date for which the Build and Sessions will have to be deleted, it will select those Build and Sessions that were executed during the period and will delete from the backend. Only admins will be able to perform this task, not the non-admin users. Users can also reschedule this as per requirement. The first rule is based on the duration.
The Admin will have the option of deleting the Builds and Sessions which are passed, failed, or incomplete, skipped over. After deletion, the data will remain visible in the MetaInformation.
When the user selects the “Date Time Range” while creating cron i.e Start Date and End Date while creating the Cron, the data will be deleted for that specified period. Suppose the user selects the Start date as 1st of January, 2021 and End date as 10th January, 2021, the message will be displayed to the user to confirm “Whether the user wants to delete the data, selected during the interval”. If the user clicks on the “Yes” button, the data during that specified period will be deleted. The rest data other than that specified period can be viewed.
If the user selects the “Date Interval” in the Tab of Time Period while creating Cron, and proceeds to enter suppose 1 month in the “Months” tab, or 1 year in the “Year” tab, the user will get the message displayed as “In Date Interval”, the selected months of data will be kept in your project, rest data will be deleted”. It is contrary to the first option of “Date Time Range” where the data for the selected period gets deleted. In the second option of “Date Interval” the data selected for the date remains and the rest of the data gets deleted.
Cron Job Audit Trail
While creating a rule in Cron, if the user changes or updates any specification in the rule within cron, which may be of either of Project Change, Name Change, or of any changes in the rule is been done, the Audit Trial of that changes will be visible in the Cron Job Audit Trial.
Meta Data Audit Trial
The deleted and updated MetaData details will get saved in the MetaData Audit Trial.
Project Workspace Audit Trial
The result deleted through automatic Cron Job will be saved in the Project workspace Audit Trial.
SAP Fiori and Netweaver Plugin Implementation for Spock Agent and Coded Function Library
Now the SAP Fiori and Netweaver Plugin is supported and implemented for Spock Agent and Coded Function Library.
MS Dynamics AX Recorder and Plugin
This Opkey Release allows you to automate your MS Dynamics CRM Application using Opkey’s MS Dynamics AX Recorder and Plugin. It lets you easily record all your actions performed on the MS Dynamics application, create a Test Case or Function Library and execute it using MS Dynamics specific plugin. There are MS Dynamics-specific keywords implemented in Opkey to perform specific actions during test execution.
Veeva Vault Plugin
The next Plugin which we are releasing in this feature is Veeva Vault. Veeva Vault is a true cloud enterprise content management platform and a suite of applications specifically built for life sciences. All vault applications are built on the same core platform, companies gain additional efficiency and compliance through the streamlined flow of documents across regions and departments. Content stays accessible, current, and in context across the entire development and commercial lifecycle.
It will let you perform all your recordings with ease with specific keywords.
1.LaunchInstalledIOSApp: Launches already installed ipa on the device
2.LaunchInstalledAndroidApp: Launches already installed apk on the device
3.RemoveApplication: Removes/uninstall application on device
4. Implemented SwipeOnObject Keyword
Major Bug Fixes
Minor bug fixes related to highlight objects in iOS devices on Appium Importer
Bug fixed for keyword VerifyObjectVisible
Show Bad Plugin Response (-9902200) DESCRIPTION: Conflicting Status and ResultCode. Original Status ‘Fail’, ResultCode ‘0’, Message: Object Not Found
We are releasing new features with the below-mentioned Keywords:
Mobile Capture Image
This will help capture the image.
Crash Issue fixed for Hybrid Applications
Multiple applications can now be opened together as the Crash Issue is now Fixed for some applications.
Bug fixes for swipe keywords
Changes in the functionality of the highlighter for hybrid apps in spy mode – When an object is clicked, it gets highlighted.
New Instrument Server– After updation the functionalities will be enhanced and perform better.
Validation Report Feature Enhancement
The replica path should not come in the FL description. It should be only logged in the Audit trail.
2. If FL description was provided blank, then only FL name should be printed in the validation report.
3. If the Expected Result was provided blank in the FL/Keyword then NA should be printed in the validation report.
Major Bug Fixes