Skip to main content

What is a Workflow in HP ALM - 7 minute guide

For those of you who start with HP ALM, or using it for basic functionality and looking to increase the capacity of the tool, I wanted to mention one of the most powerful features within HP ALM, and the one that sets it above the competitors - the ability to fully customize most of sections within the tool. This customization goes as far as giving the possibility to create new buttons with customizable functionality, updating functionality of existing functions and adding fields to different components. All that can be achieved through HP ALM’s workflow section.

This sections allows configuration of day to day functionality like preventing defect from being closed without a reason, to a more complex customization with have VBScripting like exports, execution or even initiation of other tools and applications.
In future posts I’m planning to explore some specific application of this powerful tool, meanwhile for those who interested here are some examples of what can be achieved with workflow:
  1. Limiting to what status a defect can be changed from any existing state
  2. Allowing approval of Requirement only to specific group
  3. Setting up complex logic when for example test cases can be set for review by anyone but moved back to draft only by specific user
  4. Creating export functionality to Excel of test cases and steps with one button
  5. Creating export of Requirements to excel with one button
  6. Customizing the built in delete function to move items to Recycle bin instead of deleting them
  7. Creation of custom confirmation and notifications beyond the built-in functionality of the HP ALM tool.

For those who are interested to find out more about this powerful piece of HP ALM can find out more in:

I will be posting in the future specific Workflow customizations that are very useful in my experience, so stay tuned….


Popular posts from this blog

Story Points estimation for Scrum with Fibonacci vs Shirt Sizes vs Linear - 7 minute guide

It is all began long time ago when Development Teams were constantly asked to provide estimate and they were having a hard time to properly face the task. Let's admit it, there are so many things that can change, happen, and simply go wrong during the development process that one can hardly expect a proper estimation of hours for each task. That why a relative estimation with Story Points came along. Story Points Estimation Its a different way to estimate the effort of the Scrum Development Team with-in Agile methodology, which means that instead of estimating hours of work the team estimates each effort relatively to other efforts in the project. Let's assume that a developer knows that specific 'Task 1' is much harder than another 'Task 2' it is hard for him/her to quantify that harder feeling in hours of additional work but it is possible to say that it much more work. This situation is being address by Story Points when each story point is

7 Most Popular Test Types in Software Testing

Today we are going to return back to basics of software testing and discuss the 7 most popular test types that are being used in every software testing effort. Those different test types cover all the levels of the software to make sure that the final result matching the expectations from every possible angle. Here is our list: Unit testing Smoke testing Regression testing Functional testing Integration testing User Acceptance Testing Performance Testing Now let’s have a deeper dive into each one of those by using a simple example of an imaginary system that was created in order to manage warehouse activity including shipments, inventory and goods receptions from suppliers. Unit Testing This type of testing is usually performed by the developers and is covering the very basic development component. In this test developers are testing the straight forward functionality of a functional piece of code to make sure that it is performing according to th

What is the velocity of an Agile scrum methodology?

Let's discuss some of the important measurements in Agile, and that is the Velocity of the Scrum team work. Based on Wikipedia definition Velocity is " ...the rate of change of its position with respect to a frame of reference and is a function of time...", which when transferred to the scrum world can be summarized as: The amount of work that the scrum team completed in a single measure of time - in a sprint. How we Calculate Velocity? Velocity is actually a very simple to calculate, it is done but totaling the number of story points of fully completed user stories from the sprint backlog. So if a current sprint included 4 user stories: 2 with 8 story points each, one with 3 story points and one with 32 story points. and by the end of the sprint the 32 one was not fully done the velocity calculation will be: 8+8+3=19 Note: the 32 story points are not part of the velocity calculation as this user story was not completed. What Velocity is used for? The v