What is a Workflow in HP ALM

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:

Limiting to what status a defect can be changed from any existing state
Allowing approval of Requirement only to specific group
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
Creating export functionality to Excel of test cases and steps with one button
Creating export of Requirements to excel with one button
Customizing the built in delete function to move items to Recycle bin instead of deleting them
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….

Comments

What is Quality Assurance?

What is Quality Assurance (QA) in the software development world? This one will be the most popular question,with the widest variety of answers, which by its own gives me a good reason to answer it. So, I will start with dictionary(Wikipedia) definition: Quality assurance, or QA (in use from 1973) for short, is the systematic monitoring and evaluation of the various aspects of a project, service or facility to maximize the probability that minimum standards of quality are being attained by the production process. QA cannot absolutely guarantee the production of quality products . By large this is a nice definition, though it has two issues that need to be discussed further more: 1.minimum standard of quality. 2.quality of a product. But before we go there let me say something about "assurance"

Proper QA estimation in Agile project

Today, I want to chat about a common issue in Agile development – story point estimation. You see, it's easy to get caught up in estimating how long a feature will take to develop and forget about the crucial Quality Assurance (QA) effort. It happens to often: your team is in the middle of sprint planning. New user stories are being discussed, and estimations are given, but there's a catch. You've estimated the development time perfectly, but you've barely even glanced at how much effort QA will take. Why? Agile talks about Development Team and you mistakenly thought that it is all about DEVELOPMENT. Sound familiar? Trust me; it's a more common scenario than you might think. So, what's the big deal? Well, when you leave QA effort out of the equation, several not-so-great things can happen: Vilocity can suffer: You might think you can squeeze more into a sprint than is humanly possible, setting your team up for disappointment and overcommitment. Quality can de...

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...

QA Bean

Search This Blog