Make Better Testing Decisions with HP Application Lifecycle Intelligence for HP ALM

Guest post by Mark Ford, Sr. Test Environment Administrator 

Mark-Ford-photo27-115.JPGImagine if you could know which requirements in your next release were hit with the most lines of code changes.  Imagine if you knew which defects in your next delivery resulted in the most rework.  Imagine if you could automatically be alerted to key business functions that were modified outside of any known requirement or defect?  You would have an even better idea of where to focus your testing efforts wouldn’t you?  Well you won’t have to imagine much longer with the new Application Lifecycle Intelligence (ALI) add-in for HP Application Lifecycle Management (ALM).

 

HP ALI plugs into HP ALM and connects to your source code repository.  Through various integrations it pulls source code information into a new Code Changes module within ALM.  The new module includes views that rank your release requirements and defects by lines of code changed and by the number of developers responsible for those changes.  This can really help QA pinpoint target areas for increased test coverage.  Code changes that are not associated with any requirement or defect show up in red alerting you of changes that might not be accounted for at all in your formal testing.  You can drill down to review the names of the files and even view source code compares to see actual lines of code.  With ALI you now have another source for impact analysis information in an easy to read table format conveniently located within ALM. 

 

The integrations between ALI, source code repositories, development tools and how code changes are linked to the actual requirements and defects is still a little unclear to me.  From what I gathered one way is to base it on comments used when the code is checked into the repository.  There were also 3rd party integrations between ALM and developer tools such as Visual Studio and Eclipse introduced at the conference that I believe can be used to further enhance this process.

 

One comment I heard more than once was “Dev is not going to like this…” which is an interesting viewpoint.  I guess the thought of exposing your work to more categorization and scrutiny and having others potentially viewing your code could be unsettling.  It’s something to consider as you introduce this to your QA and Dev organizations.  It might be helpful to point out that this identification process can benefit Dev by automatically communicating additional testing efforts needed for certain types of code changes.  I think if implemented with a mutual understanding this process can result in a big win-win for Dev and QA.

 

With the introduction of ALI it’s obvious that HP truly considers development management a key component of ALM.  I’m very interested to see where this investment leads, how far it will go, and the benefits we will realize along the way.

 

Leave a Comment

We encourage you to share your comments on this post. Comments are moderated and will be reviewed
and posted as promptly as possible during regular business hours

To ensure your comment is published, be sure to follow the Community Guidelines.

Be sure to enter a unique name. You can't reuse a name that's already in use.
Be sure to enter a unique email address. You can't reuse an email address that's already in use.
Type the characters you see in the picture above.Type the words you hear.
Search
Showing results for 
Search instead for 
Do you mean 
About the Author
Judy Redman has been writing about all areas of technology for more than 20 years.
Featured


Follow Us
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.