New Features
Integration of Bamboo with OpKey
Bamboo is a popular Command Line Integration (CLI) tool which has now been integrated with the OpKey. By using Bamboo environment, you can easily execute OpKey Suites through command line syntax. You need to add OpKey Jar given by OpKey team and integrate Bamboo with the OpKey. Being a CLI tool, you need to use commands (syntax) and trigger Suite execution. You can also schedule multiple Suites for execution.
There are some environments which are not supported for test execution by using Bamboo so far. They are OpKey Cloud, pCloudy, BrowserStack, Run with Tag version, Scheduler, Grid Execution, Portal, Runtime Global Variable, Collection, List, Secure String, Randomize Object & Highlight object. Support for test execution using Bamboo on these environments will be delivered in forthcoming releases.
Improvements in Collection Variable feature
Newly added Collection Variable feature has various improvements in this OpKey release. Now, it is available with Local Data Repository (LDR), MBT (input parameter & output parameter, Custom Keywords, Function Library (Input parameter & output parameter) etc. Audit Trails tab in dockable panel, now contain information related to Collection variable editing. You can also sync & make replica of artifacts collection variables & modify global Collection variables at runtime. You can use the Collection & KeyValuePair type of variable by using specific keywords which are created for these keywords. There are few additional new keywords added in this release corresponding to the Collection & KeyValuePair variable type. They are given below:
- AddItemInCollection
- AddItemInKeyValuePairCollection
- SetGlobalVariableCollection
- GetValueFromKeyValuePair
- GetKeyFromKeyValuePair
Improvement in Coded Function Library
The functionality of Coded Function Library has now been optimized significantly. The Intellisense feature comes in action even when you work with your Private Functions. It would suggest you some relevant popup list of files & functions from where you can select as required.
Optimized speed of Debug mode of Execution
The debug mode of test execution has now been optimized significantly in this OpKey release. Previously there was an inherent 2 seconds delay after every keyword, running in Debug Mode of execution. In addition, it was taking a bit more time to start test execution due to this inherent wait but now it waits only for 20 milliseconds between every step so that the Debugger Window can function properly. Thus, the overall speed of test execution has been optimized.
Execution Session Limit & Multiple deletion
Now, there is a limit of 1000 execution sessions per project. When count of executed sessions reached to 1000, you need to delete old executed sessions from execution result. You would be unable to perform execution once execution session count reached to 1000. In fact, large number of execution sessions results slowness of working with OpKey. Now, user can delete multiple session by selecting desired sessions through checkbox.
Sparkin feature improvement
There are some important improvements in Sparkin feature delivered in this OpKey release. Now, you can sync, import, export, make replica of Sparkin files. In addition, you can also map Sparkin scenarios with TMT & Jira so that automatic bug can be logged & associated bug can be updated as well.
Improved visibility of OR Object
The visibility of the fetched OR object has now been improved. When objects are fetched through recording, now size of the fetched object may be up to 1MB which will have optimized visibility.
Other Improvements
Performance of the test execution using heavy LDR, has been optimized significantly. There is filter in Execution Result using which you can search desired session easily.
Breaking Changes
OpKey WEb Plugin improvemnts:
There are some major improvement changes done in the functionality & behavior of OpKey Web in this OpKey Release. These changes results quick & smart object recognition for performing respective action during test execution. So, here are the points describing the behavioral changes done:
- If multiple objects (>5) are found during finding an element by any property, filter out invisible objects to see if object can be identified uniquely. Otherwise, move to the other property & search for it.
- First search all elements by tagName and then search for the element by specific property using elements found (This need to be done using FindByJavascript).
- We have two finders in our OpKey Web Plugin: JavaScript & Selenium. It first searches by using JavaScript. In case JavaScript is unable to find an object, it try to find it by Selenium. This is the existing behavior. As per new changes, now findByJavaScript will also return multiple objects (similar to findBySelenium). The decision whether to use the object or continue the search will be same as existing implementation of FindBySelenium.
- Implement TextContent and InnerText provided by recorder and in plugin.
Matrix explaining the OpKey Web Plugin changes:
Major Bug Fixes
Known Issues
