| Mentioned below are some of the questions that our clients have asked about OpKey. In case you have any other questions that are not answered by FAQ below, please feel free to contact OpKey support |
| Q.1) Is OpKey some kind of Automation Tool? |
| No. OpKey is not an automation tool in itself. It’s a Automation Framework that integrated with commercial and open source automation Tools and facilitate effortless automation |
| Q. 2) Is OpKey framework application dependent? |
| No. OpKey framework in not application dependent. The keywords provided out of box with OpKey are generic in nature (Like set_text, click_button, validateDB etc..) and can be used with any application |
| Q. 3) What are the benefits of using OpKey framework? |
| OpKey facilitates users with no scripting knowledge to convert their manual test cases to automated test cases with utmost ease through the use of Keyword driven interface for test script preparation. They can also data drive their tests just at a click of their mouse without the need of writing complex login for the same.
Also features like Advanced Object management and Exception handling make the automation scripts more maintainable and Robust bringing about higher ROI in long run.
Another problem that OpKey solves is that open source tools like Selenium, Sahi etc do not have in build features like Object repository for GUI object management, Exception, Visual reporting etc. OpKey brings those commercial grade features to open source tools and ensure ease of adoption |
| Q. 4) Does OpKey supports modularity |
| OpKey is based on the principle of modularity and script re-use. Business Process Mode of OpKey allows user to define their own components and re use these components in whatever script they want. For example an user can define Login as a component in OpKey and then call this Login component in whatever script he wants to use Login |
| Q. 5) What are the prerequisites for using the OpKey Framework? |
OpKey is a standalone desktop application build in dot net. The following are the pre-requisites for using OpKey
System Requirement
- P4 Machine with minimum 1 GB RAM
- Dot net Framework 3.5 (freely distributed by Microsoft)
User Skills Requirement
- No Coding skill required to start preparing test scripts
|
| Q. 6) What are the various components of the OpKey Framework? |
OpKey has Two modes of operations
- Default Mode : Good for automating small application with medium complexity
- Business Process Testing (BPT) Mode : Used for automating complex enterprise application?
Various components of OpKey across both these modes are
- Object Repository (OR): Used for storing GUI Object of the application. Test Scripts refer these Objects in OR. This makes test scripts independent from any changes in GUI objects of the application across different builds and tomorrow if some object changes, you just have to go to OR and change the object. Test Script remains same
- Data Repository (DR): Used for storing data that would drive the test scripts. Data repository is an integrated Grid that allows user to define the test data which would be used to drive the tests.
- Data Import wizard: This wizard allows user to import test data from an external source (CSV file, database, excel file) into OpKey.
- Test Scripts: Test script is a series of steps (keywords) that mimic a manual test case. Each step consist of actions to be performed (keywords) like set text, button click etc, the objects on which these steps needed to be performed (referred from Object Repository) and the data needed to perform this step (referred from DR)
- Test Suites: Test suite is like a batch of test cases. Multiple test cases that user want to run are combined together to make a test suite and then executed at one go
- Test Results and Analysis: This module enables OpKey users to organize their results and isolate the source of error quickly
Apart from these, BPT mode has unique components like
- Application Components
- Business components
- Business Flows
|
| Q. 7) What sort of Keywords are provided by OpKey |
OpKey provides two categories of Keywords
GUI Keywords: These are the keywords used to interact with GUI element on the web page. For example set_text, object_click, object_get_text, Object_verify_property etc.
Constructs: Constructs are general purpose keywords that are GUI independent. Example IF, ELSE, ENDIF, fetchDBValue, ValidateDB etc.
For a detailed list of keywords please contact OpKey Support |
| Q. 8) Apart from the out of box keywords provided by OpKey, can I make my own keyword that is dependent on my application? |
OpKey has a well defined interface that gives advanced users the flexibility to define their own keywords and register it with OpKey. These keywords can then be used while creating test scripts.
However to create own keywords, user require to have the scripting knowledge of the back end automation tool in which the keyword is going to be executed |
| Q.9) Can I import my test data from external source within OpKey? |
| Yes. Data Import wizard within OpKey allows user to import test data from an external source (CSV file, database, excel file) into OpKey. This data can then be referenced to drive test scripts |
| Q. 10) What are features that are present in OpKey and not present out of box in tools like Selenium and Watir? |
OpKey has the following features that are unique and are not present out of box in open source tools
- Keyword Driven GUI to create test scripts
- b) Object Repository to hold information of test objects and keep it separate from Test scripts
- c) Integrated Data Management in OpKey gives users GUI interface to define data for data driven testing. In selenium and Watir, one has to define data in an external file and then write code to access this data
- d) Graphical Result analysis features enables OpKey users to organize their results and isolate the source of error quickly
|
| Q. 11) My application is prone to GUI object getting changed from one build to next build. How can OpKey handle this challenge for me? |
| OpKey is designed to minimize the maintenance effort involved with typical automation projects. Objected Repository (OR) within OpKey allows you to add objects from your web page and keep it separately. While Preparing test script, you just refer object from OR. This way if your object changes in next build, you need not change the test script. Just go to Object Repository and change the object description and the task is done for you. |
| Q. 12) Does this OpKey framework handles exception like a pop up coming during test execution |
| Yes. OpKey has Pre defined keywords to handle pop up exception handling. If you expect that a specific kind of popup can come anywhere in between your tests, you just have to include pop up handling keyword in the beginning of your test. This would make OpKey to look for any pop up with the defined description and close it as soon as it appears. This enables test to continue run without interruption. |
| Q. 13) What are the challenges faced in automation that are solved by OpKey Framework |
OpKey was conceived with a vision to solve the above mentioned pain of most test teams.
OpKey enables test teams to have Day-1 start in preparing test scripts and reduces maintenance effort associated with any automation project. This effectively eliminates automation set up and maintenance cost associated with a typical automation project and saving up to 50% of testing budgets |
| Common Automation Problems |
Solution – The OpKey way |
Budgets constraints to invest in commercial tools
Most of the teams want to move to commercial automation tools because of the ease of use with which the test scripts can be created and the features provided by that tools. However the license cost is a major deterrent for the organizations wanting to adopt COTS for automation.
Because of this constraint, Teams look towards open source tools like Selenium and Watir to automate their apps. |
Integration with open source automation solutions
OpKey comes with out of box integration with Selenium, Watir and Sahi and provide the same features as provided by commercials tools. This allows test teams to work s conveniently with open source tools without worrying about spending a fortune there. |
Lack of skilled automation Engineers:
Automation demands Test Engineers to have domain knowledge as well as technical knowledge (scripting). Often it becomes a constraint for organization to source right people having this skill set |
Keyword driven interface for Test Scripts
OpKey has a power packed key word driven interface for preparing test scripts. Manual Tester can create a new test scripts easily by combining existing keywords. This does not require any coding experience.
By providing more than 150 pre build keywords that are application independent, OpKey caters to most of the needs of automation script |
Ramp up Time involved in making team comfortable with the automation tools
Even if you have existing automation solutions, one need to invest continuously in the trainings for the QA team to derive the optimum productivity out of automation. |
Easy to Use GUI driven test automation
OpKey’s Graphical User Interface is highly intuitive and doesn’t need any specific training for the users. Most of the End users have picked up OpKey within a couple of days without any formal training. |
Lack of knowledge on Automation Best practises
Most of the organizations moving to automation for the first time face a typical challenge where they do not posses process maturity or the required know how of automation best practises with the automation for the first time |
OpKey is based on industry accepted best practises and Business Process testing methodology
OpKey Testing workflow is based on Automation Best practises accumulated with years of experience on executing complex automation project across domains and technologies.
This allows the organization adopting OpKey to Build automation test without worrying about associated processes |
Difficulty in selecting the right automation framework.
It’s a well accepted fact that any automation activity requires an effective framework fitting the needs of the application and QA processes of the organization. However most organization find it difficult to choose the right automation framework |
OpKey is a Keyword Driven framework in itself
OpKey is keyword driven framework that has pre build function libraries for common tasks like database interaction, Result logging, Exception handling, File Read Write etc. This takes care of most of the framework needs. At the top of it, features like integrated data and Object Management, Extended Result Analysis framework and Test Suite scheduling helps clients start test scripting from day-1 |
|
