ALM (Application Lifecycle Management) is a well-known Test Management tool and it helps you to maintain quality and control of app development. ALM is now integrated with Opkey Web. By using it, users can map their Opkey Test Cases with the ALM Test plan or Requirement. The status of the mapped Test Plan or Requirement would be changed as per the result of the Opkey Test case. It also allows user to log an automatic bug in ALM, in case of failure of Opkey Test Case.
Need of ALM:
Managing the development of an application lifecycle is very important in the Agile environment. In order to maintain the quality and control of app development, Agile teams require application lifecycle management software and ALM is one of the well-known tool in this category. It not only allows you to log bugs but much more than that. It facilitates you to create a Test plan, Test Requirement, Test Sets, Test Runs etc and map them with your Test Case. The mapped Test Plans, Test Requirements and Defects are being updated as per the execution result of your mapped Test Case. It ensures key tasks throughout the lifecycle are logged, completed and tested. By keeping these advantages in mind, ALM has now been integrated with Opkey.
Getting started with ALM in Opkey Web:
Click on the Tools menu and then click on External Tool Integration.
External Tool Integration window opens. Check UseForTestManagement checkbox corresponding to QC/ALM Extension for Opkey and click on Configure icon.
QC/ALM Settings window opens. Fill valid URL, Username and Password of your ALM server and click on Authenticate.
Once, your credentials have been authenticated successfully, Domain and Project Name fields appears.
You can apply QC/ALM Defect Settings from here. Click on the QC/ALM Defect Settings link.
QC/ALM Defect Settings page opens. You can add your own defect fields. If you want to link logged defects to be linked then check Defects to be Linked checkbox.
You need to fill Field Value so that defect can be logged on test failure. You can add new Field Names & Values by clicking on Add button.
Let us initialize ALM Server on Internet Explorer (ALM support only IE).
While initializing the ALM server on IE, you may come across the security-related issue. In order to fix it, you need to add the ALM Server URL in the list of Trusted Sites in IE. To do so, follow the below-given steps:
Navigate to the Tools (Alt+X) of IE, click on it and select Internet Options.
Internet Options window opens as follows:
Go to the Security tab, select Trusted Sites, click on Sites. List of Trusted Sites displayed here.
Enter the ALM Server URL and add it to the list of trusted sites and save it. Protected Mode should not be enabled. So, keep ‘Enable Protected Mode (requires restarting Internet Explorer) unchecked.’
Now, you can open your ALM Server on the Internet Explorer successfully.
Click on ALM Desktop Client, as shown below:
Enter valid ALM credentials and click on Authenticate.
Once, your ALM credentials have been authenticated successfully, Domain and Project fields get enabled.
Select Domain and Project from the dropdown list and then click on Login.
Your ALM Dashboard page opens.
Here, you can view a few build Test Plans along with their details.
Here, you can view a few build Requirements along with details.
Let us map a Test Case with the Test Plan and Requirement.
Here, you can view the Test Case which would Fail as mandatory Data Input Arguments are not given.
Right-click on the Test Case and select QC/ALM Mapping.
QC/ALM Filter page opens.
Let us first search Requirements and map them with the Test Case. You can fill search fields and search. Click on Search to get list of Requirement(s).
Here, you can view that there is a Requirement named as radhe.
Select the Requirement and click on Apply Mapping Changes.
Mapping of Requirement with Test Case has completed successfully. Now, execution result of the mapped Test Case will affect the Requirement details.
You can hover your mouse on the Info icon under Already Mapped column to view the mapped artifact details with the Requirement.
Similarly, you can search for the ALM Test Plans and map them with your Test Case.
Here, you can view the list of Test Plans as a search result.
Select desired Test plan(s) and click on Apply Mapping Changes to map them.
Let us execute mapped Test Case which would get fail (as we have not provided mandatory Data Input Arguments).
Click on Run Now, fill all required fields, check Show Advanced Settings checkbox and click on Next.
Check Update Mapped Test Management Artifact checkbox so that your mapped Test Plans/Requirements can be updated as per the test execution result.
From here, you can add Session Tags.
You can apply Global Variables from here.
Execution process takes a while. Here, you can view the Execution Logs.
This Test Execution get fail, as expected.
Let us have a look at the logged defect:
Open this defect to view detailed information:
Have a look at the mapped Test plan and its information. It’s last execution status is Failed.
Here, you can view Associated Defects:
Here, you can view Opkey Execution Results:
Here, you can have a look at the below screenshot showing Attachment of the Test Plan. This attachment file contains detailed information about the execution result in PDF format.
You can open Test Plan Attachment file to view details:
Have a look at the mapped Requirement and its information. It’s execution status is Failed.
Click on the Req. ID to open the Requirement. Here, you can view details of the Requirement.
You can view the Attachment of the Requirement as shown below:
You can open Requirement Attachment file to view details:
When Test Case is Passed Successfully:
Have a look at the execution result as Passed.
The status of the Test Plan get changed as per the test execution result. Here, you can view the last execution status as Passed.
You can have a look at the Attachment of the Test Plan.
You can open Attachment file to view execution details.
Have a look at the Requirement details when mapped Test Case get passed. Here, you can view that current status is Passed.
Click on the Req. ID to open the Requirement. Here, you can view execution details.
Here, you can view the Requirement Attachment file for the Passed Test Execution.
You can open this attachment file to view details.
Whenever we create an artifact either of Function Library, Test Case, or Business Component, two fields will be displayed in the details tab with the name of “Version and Id”.
The version tab will begin from 1 and a unique ID will be generated. The version will get changed in fixed states, of either taking a backup, backup restore, and on other respective conditions.
How to update the version in ALM?
On clicking the tab of “External Tool Integration”, the user will have to go to QC/ALM settings>>Advance Setting. A new UI has been created with the name “Update Version” where the Opkey Field and ALM field are fixed. ALM test run field will be required in the ALM field tab by the user to proceed ahead. In the ALM test run, the field which needs an update of the version, the user will have to add the field in the “Add ALM field” tab. After saving and proceeding with the execution, by default, the specific executed test case’s version in the ALM of that specified field will be updated.
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