Opkey modules are essential for seamless project management. They assist in enabling efficient test management, meeting software development requirements, and monitoring overall project progress. These modules are accessible through the left panel on the Opkey dashboard and help ensure successful project delivery and meeting deadlines.
Let's go through Opkey modules one by one to understand their use case.
Quality Lifecycle Management
Opkey's QLM aims to provide users platform to oversee their software projects. It brings together project management, issue tracking, and testing all in one place.
Using QLM, project managers can follow software releases, work together with development and testing teams to identify and address problems, and keep an eye on progress with custom reports. QLM encourages teamwork and transparency among developers, testers, and everyone involved in the software development process.
Let's go through its various sections:
Opkey's Release feature helps plan and track the progress of software's upcoming releases.
Additionally, you can set milestones for different phases in a release, which may include tasks, features, and bug fixes for a particular release.
For instance, for a quarterly software release, you can break down the process into monthly milestones, like development, testing, and feature updates. This way, you can efficiently accomplish tasks in each milestone step by step and track their progress for the quarter.
You can link milestones in a release to test suites, tickets, test runs, or test cases.
2. User Story
User stories store the gathered requirements from the user and present them in a way that is easy to understand and prioritize for developers and other team members working on a project. They are typically created from the perspective of the user and describe what features are required in the next planned release.
As a project manager, you can assign a user story to your development team and monitor its progress.
Under this option, you'll be able to create tests both automated and manual to verify the application's functionality and collaborate with developers to address bugs or issues. You can assign tickets to the development team for issues found during the testing of any feature and track their progress.
4. Test Suite
A test suite in Opkey is a collection of test cases that are executed together. It can be used to execute a large number of test cases in a single run. Each test case in a test suite is independent of other test cases and executes separately.
This means that each test case can be executed successfully without depending on the results of any other test case. You can also schedule the execution of test suites in Opkey on a preferred date and time.
Tickets help create and track issues or bugs found during the testing of the application. Testers, QAs, or project managers can create and assign tickets to development teams for resolution. They can be created and tracked by anyone on the project team.
This allows everyone to stay up to date on the status of issues and to collaborate effectively to find solutions. By efficiently tracking tasks and managing issues, you can save time and boost productivity.
6. Test Run
This section displays all the executed runs. This includes both manual as well as automated test runs. On the test run dashboard, you can see the list of various test run with details such as execution time stamp and run status.
This section is exclusively dedicated to test management. Testers and QAs can manage automated test cases, group them in a suite, or execute test runs. Let's look at its various sections:
In this section, you can efficiently manage all your automated test cases. You can also create reusable components with repeatable test steps to use across test cases. On the test dashboard, you can see the list of various test cases with details such as assignee, priority, and state.
2. Test Suite
A test suite in Opkey is a collection of test cases that can be executed together. Testers can create a suite of automated test cases and execute them simultaneously in this section.
The Test Suite dashboard in Automate has options to delete, edit, or search a test suite. You can also see the list of test suites with details such as priority, assignee, and state.
3. Test Data
Test data are used to map different types of data to test cases to verify how well an application works with different datasets in testing scenarios. Test data help in identifying coding errors during the initial stages of a project. This allows you to make changes for further testing before its release.
4. API Test
API testing focuses on assessing individual API methods and their interactions with other APIs.
Opkey allows you to test API with the two most popular web services, SOAP and REST methods.
Test Discovery is a test mining platform that enhances ERP application testing by automatically finding gaps in test coverage.
Test Discovery analyzes your application’s configuration logs and existing test cases to map its functionality and shows areas lacking test coverage. After this, it suggests testing scenarios to address these gaps. It has two sections:
Discovery takes Snapshots of the testing process. By adding snapshots at regular intervals, you can compare the actual and the expected outcomes of your processes, and identify areas with deviations.
This information assists in making informed business decisions, such as:
Identifying improvement areas for test coverage.
Prioritizing your resources to areas that need maximum attention.
Measuring the overall business impact of changes.
2. Impact Report
The Test Discovery Impact Report evaluates the effects of new releases or patch upgrades on your current tests.
It categorizes the differences between old and new sessions into distinct forms, codes, DB fields, etc. enabling clear identification of changes. This aids in pinpointing specific areas for testing, saving time and costs associated with performing regression tests for each code modification.
Opkey's ConfigOps platform automates the entire DevOps lifecycle, from configuration to deployment. This saves you time and effort and helps ensure your Oracle Fusion implementation and maintenance goes smoothly.
Opkey’s Config Ops helps in:
New configurations of Oracle Fusion. For example, the manual tasks of copying, importing, and exporting the configured files to different instances can now be automated using Opkey’s Config Ops.
Transferring the configuration setup data from one system to another without hassle.
Comparing configured data of different instances to the required testing environment.
Let's go through its various sections:
You can create different tasks for the Oracle application and select actions such as:
Export Configuration - It lets you export configurations from the selected instance of Oracle Fusion, which then gets saved in the repository named ‘Package' in Opkey. You need to select the Action, Source Instance, Oracle Offering, Functional Area, Oracle Task, and Business Unit.
Import Configurations - After exporting the configurations, you can make the necessary changes and import the configurations to the selected instance of your Oracle Fusion. Select the instance, package, and upload it.
Copy Configuration - You can copy the configurations to another instance by selecting the Oracle Offering, Functional Area, Oracle Task, and Business Unit.
Compare Configurations - You get a detailed view of the different instances to compare for any changes and take action. Select or upload the files for configuration and package from source, target, and User Story.
Approve - This lets you approve the configuration set up after its export. You need to select the approver or add them as per requirement. You also need to select User Story.
Merge - Use this option to merge the configurations of different instances during the development phase.
Run Test - Select the respective test cases or suites along with the User Story to run.
Send Email - Post testing, you can send emails to notify the completion status of tests. You need to add the email ID, subject, email body, and select User Story.
Do Configuration - This lets you perform the configurations in the selected instance. You have to select the application instance, package, and User Story.
Create Job From Release - Use this option to perform multiple executions in a go. Select Release and User Story to create a Job from a given release.
Create Job from User Story - Select and create the Job from User Story.
Create Configuration File - Select the Application and module, provide the business requirement, associated tasks, and the User Story to create configuration files.
This lets you create workflows to execute the tasks in the pipeline sequentially.
3. Scheduled Job
You can schedule your Test Suite from this section with the test cases that you have created.
You can view the results of sessions that have been running on Pipelines or Tasks.
The Report section has two subsections. Let's understand them one by one:
1. Test Run
Create a Test Run by selecting the test cases and schedule it to run a particular time. This dashboard displays all the executed runs. This includes both manual as well as automated runs.
2. Custom Report
Opkey’s Custom Report lets you create reports by adding widgets and selecting modules to be visualized in a tabular form. You can pick the dimensions and matrices to customize how they will be displayed. It helps extract information of specific interest and organize the data graphically.
Let's go through its sub-sections:
You can search for all the modules, assignees, reporter, status, and priority. You can save your custom filter here.
2. Assigned to me
This filter will allow you to view all the Tickets/User stories/Tasks/Test Cases assigned to you.
3. Reported by Me
This filter shows all the Tickets/User stories/Tasks/Test Cases reported by you.
4. Runs Assigned to Me
This filter will let you view all the Test Runs assigned to you.
All the notifications related to the creation, changes, assigning, or mentions of an activity such as file/ticket/user story where you are the creator/assignee/reporter will be available here.
You've reached the end of this article and are now familiar with all the Opkey Modules.
Ready to dive deeper? Check out the next article: Understanding Opkey Recorder.
Explore, experiment, and achieve your testing goals on Opkey!
Was this article helpful?
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
We appreciate your effort and will try to fix the article