This section provides an overview of the features that were introduced or enhanced in ALM 12.60 and ALM 12.60 Patch 1.
ALM 12.60 enhancements
This section provides ALM 12.60 enhancements.
|Importing QCP from previous versions||
You can import QCP files from previous versions (ALM 12.00 or later) to ALM 12.60 without the need to include them in the initial upgrade process. This can be useful with archived or support phased upgrade projects.
|Business Models Module enhancements||
Business Models module now enables you to import models from ARIS 10.00. For details on Business Models module, see Business Process Models.
|API Key authentication for API integrations||
API key authentication provides a secure authentication mechanism for external applications accessing ALM's API.
The ALM site administrator generates and manages the list of API keys for ALM. For details, see How to Manage API Keys.
When writing ALM extensions or API scripts, obtain a Client ID and API Key Secret from the administrator, and use them for authentication. For details on API key authentication when using REST and OTA, see the API References.
JDK is decoupled from the ALM installation. You can now install a JDK patch level to meet the policy needs of your organization.
|Business Views Microsoft Excel add-in enhancements||
Includes the following updates:
Now you can add branches to your business process tests, either from ALM or UFT (version 14.50), enabling you to configure the components that UFT runs, depending on the state of your application during runtime.
BPT branches provide additional structure to your test to support complex and dynamic applications, which have non-linear functions and interfaces. Use branches to cover many different user flows in your app, using the same test.
For details on how to add branches from ALM, see How to Add Branches.
For details on how to add branches from UFT, see UFT Help Center.
|ALM Help Center enhancements||
The help center now includes advanced site search functionality:
ALM 12.60 Patch 1 enhancements
This section provides ALM 12.60 Patch 1 enhancements.
|Running ALM client without deployment||Using the ALM Client Launcher tool, you can now use an ALM client on any Windows machine without the need of deploying it from an ALM server and without Windows administrator permissions. For more details, visit Marketplace.|
|Support for Microsoft Application Virtualization||You can now create ALM App-V packages using Microsoft App-V Sequencer. For details, see this KB article.|
The ALM installation now supports OpenJDK 8.
|API Keys enhancements||
SaaS. When deactivating a customer in ALM, all associated users are deactivated and their API keys are deleted.
|Support for Microsoft Azure|
|Memo field enhancements||
|Increased length of user defined fields||
|Support for NUnit 3.0 files||
When importing tests from an external file to your Test Plan Tree, ALM now supports NUnit 3.0.
For details on how to import from an external XML file, see Generate Tests from External Test Results Dialog Box.
|Sharing dashboard pages||You can share dashboard pages for viewing outside ALM client. For details, see Share Dashboard Page Dialog Box.|
|Creating releases from template projects||When creating a new release by copying from an existing release in a template project, ALM now also copies release scopes and milestone scopes from the template project. For details, see New Release From Template Dialog Box.|
|Customizing the ALM Login Window||
You can customize the ALM Login window, so that you can share any special announcements or important events with users that are using the same ALM server. You create a content file and save it on the ALM server. Users can view this content from their ALM Desktop Client machines. For example, you can notify the users that the ALM server will not be available for use due to an upgrade.
|Monitor test coverage with ALM Prisma (technical preview)||
ALM Prisma is a Google Chrome extension that monitors your activity when testing a web application (AUT), and shows you at a glance which areas in the UI have been covered by your manual tests. Prisma reflects the actual coverage on your AUT by coloring the areas in the application that were tested. This helps you focus future testing on areas that have not been covered.
For details, see the ALM Prisma Guide.
Includes the following updates:
Defining default application areas. When creating an application area resource in the Test Resources module, you can now define a specific application area as the default one used for all components in the ALM project. For details, see Test Resources Module Menus and Buttons.
Skip option for debug runs. You can now configure a debug test run to skip specific components to speed up the run time – focusing in only on those components that need debugging. For details, see Run or Debug Test Dialog Box.