We are proud to announce that Opkey has secured a new funding round →  Read more!
x

Opkey Help Desk

Text Link
1. A Quick Opkey Surge Walkthrough
User Profile and Admin Console allows you to update your profile, manage users and projects. It must be noted that Profile is accessible to all users but Admin Console will be accessible only to the users having admin rights.
Text Link
13. Using Global Variables
Text Link
14. Trackwise Test Opkey Surge
Text Link
15. Service Now Test Opkey Surge
No items found.
Text Link
16. External Tool Integration with Opkey Surge
Text Link
17. User Profile and Admin Console
User Profile and Admin Console allows you to update your profile, manage users and projects. Profile is accessible to all users but Admin Console will be accessible only to the users having admin rights.
Text Link
18. Working with BDD (Gherkin Stories)
Overview Behavior-Driven Development (BDD) is an agile software development practice that enhances the paradigm of Test Driven Development (TDD) and acceptance tests. It encourages the collaboration among developers, quality assurance, domain experts, and stakeholders. Test Driven Development (TDD) mainly relies on the repetition of a very short development cycle, where the developer writes an (initially failing) automated test case that defines a desired improvement or new function, then produces the minimum amount of code to pass that test, and finally refactors the new code to acceptable standards however, Behavior-Driven Development, primarily focuses on obtaining a clear understanding of desired application behavior through discussion with stakeholders using a Ubiquitous language, which is lucid and easy to comprehend. Behavior-Driven Development was introduced by Dan North in the year 2003. BDD, principally being an idea about how software development should be managed by both Business Analysts and QA teams, it also assumes the requirement of specialized software tools to support the development process and for intended use in BDD projects. Conversational patterns in BDD BDD is all about the conversations you have, exploring examples (or scenarios) of an application’s behavior, to see if everyone has the right understanding. We’ve got a good chance of discovering what someone else knows, and has perhaps forgotten to tell us, if we start questioning the ways in which our understanding might be wrong. These are two patterns which are commonly used. Context Questioning We can ask, “Is there any other context which, when this event happens, will produce a different outcome?” It might be an additional context, or a context which occurs instead of the one(s) we’re considering. We can ask this question, or we can think of contexts ourselves and ask about those. For instance: Given a salesperson, Tom, wants to sell three cars, Volkswagen, Fiat and Honda When Tom uses the application Then Tom should only be able to see the price of Volkswagen, Fiat and Honda As a Test Engineer, one will have obvious question “Given I have no cars, what happens then?” The Head of showroom says, “Who cares? Why are you even using the application? Go & get some clients already!” (He’s thinking of his failing business.) Even though the behavior of the application is not going to change immediately, still a lot can be learnt about business domain this way. Outcome Questioning This is similar to Context Questioning, but instead, we ask. “Given this context, when this event happens, is there another outcome that’s important? Something we missed, perhaps?” For instance: Given the serverX of shopping site has a problem When a user bought a gift Then the user should be told about the problem You’ll wonder, “Is that all that should happen? I’d be upset if I was a user and this happened a lot.” My business analyst says, “Well, we’ll still have the details in the system, so you’ll be able to do it again later. Oh, yes! We need to store the details of the gift in our system still, too, but make sure it doesn’t have a ServerX ID so that we can tell it didn’t go through.” There are lots of other ways to have conversations around behavior. They’ll usually be trying to find missing contexts and outcomes – places where a new piece of behavior happens. These also tend to be the things which business users, familiar with their domains to the point where they don’t think about it, forget to talk about. Developers are pretty good at spotting this, because they’re usually thinking through how they’re going to implement the problem, and wondering what goes on the other side of the “if… else…” statement (even if we’re not meant to be implementing yet, we already are in our heads). Testers are also very good, because they’re used to the kind of things people get wrong when they produce software. This is why getting all three people – a tester, a developer and a business analyst – is so useful when we’re discussing scenarios. It’s also why it’s so important to have the conversations – because if you’re not having conversations, you’re not doing BDD.
Text Link
21. Working with Bamboo in Opkey Web
Text Link
23. Working with Sparkin
Text Link
24. BC-BP Dashboard
Text Link
24. Commonly Used Features
Text Link
27. Licensing in Opkey
Overview: OpKey Web allows you to create your account & experience awesomeness of test automation free within the trial period. Once trial period is over, you are required to purchase license to further use OpKey. For details about Account registration, refer this link OpKey Account Registration. OpKey has two types of License one is Seat License and Second one is Concurrent or Floating License. Seat License: Seat License is a Computer bond or Node locked License. It is tied only for one machine in which you have installed your OpKey. Seat License is different for OpKey Web, OpKey Execution Agent and Plugins Concurrent License: Concurrent or Floating License is a Network based License. In this type of License, multiple users can use same Concurrent License for OpKey Web, OpKey Execution Agent and Plugins.
Text Link
29. Working with Single Sign-On feature in Opkey
Overview: Single Sign-On (SSO) services gives an easy access to manage our team’s identity across all the SaaS products that is being used in the organization. SSO services allows user to use one set of login credentials (e.g., email and password) to access multiple applications. The service authenticates the end user credentials only once for all the applications according to the rights given to the user and eliminates further prompts when the user switches applications during the same session. A very common example that you can see is Google’s SSO implementation of login for their products, such as Gmail, YouTube, and so on. Any user that is logged in to one of Google’s products is automatically logged in to their other products as well. Some common advantages of SSO: Removes the need for users to remember and manage multiple passwords. Simplifies user’s experience by allowing them to log in at one single access point and enjoy a seamless experience across multiple applications. Increases productivity significantly by reducing the password-related support emails. Reduces phishing and thereby making sure users aren’t tricked into giving away sensitive information. Now with OpKey using the SSO feature, user is allowed to login with IDP service called as “Okta” & “ADFS“. Currently OpKey supports SAML protocol. Other IDP services like Google, OneLogin, etc. will be supported soon.
Text Link
30. Working with BitBucket in Opkey
Text Link
31. Multi Browser Testing
Text Link
36. Manage MetaData
Text Link
38. Marketplace
No items found.
Text Link
39. BackUp and Restore
Text Link
4. Working with Local Data Repository
Text Link
4. Working with Test Cases
Test Case is a collection of test steps that contain a Keyword, a Control Flow Construct, or a Function Library. Further, a Keyword can take either no input or can take an object, data, or both as inputs. Each test step also returns an output which can be used as input for other test steps as well. The test Case module is integrated with a recording feature which helps while recording actions performed on a web application and create a complete test case easily and quickly. For example, You can create a Test Case for testing functional as well as the user interface of an eCommerce web application. The test case steps may contain test steps as login to the web, searching the product, buying a product, making payment, and finally one for logging out of the portal. Working with Test Case After successfully login into the OpKey Web, select the appropriate Project in which you want to create a Test Case File. You will be navigated to the screen has as shown. You can mark the “Don’t show me again” checkbox as checked if you do not wish to view this notification again. Click “End Tour” to proceed with the process of creating a Function Libraryfile. How to create a Function Library File? Method 1 After clicking on “End Tour” , you may “Click to Create New Artifact“.Select Function Library. The “Function Library” text will appear highlighted. Click on the highlighted icon to create a New Function Library file. A Create Function Library window will get open as shown The fields marked with * are mandatory. Enter the Name of the Function Library. You can also enter the Description. Click OK. Method 2 Go to Project Workspace > Select the root Folder > Click Create New file icon > Select Function Library. A Function Libraryfile will be created in the root Folder of the project Workspace. You may rename the Function Library accordingly. Method 3 Right click on root folder > select Create New > select ‘Function Library’. A Function Library file will be created in the Root Folder of the Project Workspace. The Function Library window will open up as shown. There are two ways of creating Function Library: By adding test steps and by recording. Let’s first discuss about creating Function Library by adding test steps in the next article.
Text Link
41. Job Portal Testing
Text Link
6. Working with Opkey Recorder
Overview: OpKey Recorder is action recorder utility which is used for recording actions performed on web, mobile & desktop applications for Test Automation. OpKey Recorder is usually referred as OpKey Smart Recorder which is a complete recorder package & works as a Web, Mobile, Desktop, Java, Salesforce, Workday, Oracle as well as OracleFusion Recorder. While beginning recording session, you need to choose the platform (Web, Mobile or Desktop) on which you want to perform recording. If you are performing recording on Web, mobile or Desktop application for the first time, you need to install OpKey Smart Recorder. Once it is installed, you can perform recording on the supported platform applications. OpKey Recorder: Useful Links: Installing OpKey Smart Recorder OpKey Web Recorder Desktop/Java Recorder Salesforce Recorder Oracle Recorder Workday Recorder OracleFusion Recorder iOS Recorder PeopleSoft Recorder
Text Link
7. Working with Object Repositories
Object Repository is a collection of objects of the web application upon which actions are performed during test execution. OpKey tests the dynamically changing application by identifying and fetching the objects from web application along with their expected values and properties. You can easily fetch objects, create object repository and gather information for testing the web application. Before execution, you should make sure that Object Repository contains all the objects used by the test. There are two ways creating Object Repository file: Creating Object Repository manually and Fetching objects for creating Object Repository.
Text Link
9. Execution Agent
1. What is Opkey Accelerator and why do we need such test automation platform?
change the text to whatever you wish
1. What is Opkey Accelerator and why do we need such test automation platform?
change the text to whatever you wish
1. What is Opkey Accelerator and why do we need such test automation platform?
This is some text inside of a div block.
Example Video 2
Example Video 1