Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Self learning System/method to identify test cases based on code change

IP.com Disclosure Number: IPCOM000245464D
Publication Date: 2016-Mar-11
Document File: 2 page(s) / 28K

Publishing Venue

The IP.com Prior Art Database

Abstract

This solution find the test cases to be executed based on the code changes delivered by the developers. It proposes to build a mapping of code modules(functions/methods) and work items. This mapping is maintained at 4 levels or precision - group of lines of code, function , class and package for code identification. This mapping is updated or created whenever there is a new code checkin (change set). This mapping then allows for finding the work items and the test cases mapped to the work items

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 01 of 2

Self learning System/method to identify test cases based on code change

Disclosed is a solution to find the test cases to be run based on code changes. Since the dawn of large scale software development, identifying the affected test cases for a code change has remained a challenge. There are several solutions patented based on software model diagrams or code instrumentation. In a agile development environment - there is little focus on updating anything other than the code. In a waterfall development model, this is counted as an additional overhead on part of the developers which is very difficult to enforce.

Some patented solutions and their drawbacks are explained below.

Of recently most large software development teams have adopted Application Lifecycle Management (ALM). This is an additional dimension available to solve the test case identification problem without add-on overhead over and above the linkages that need to be maintained in a ALM solution.

ALM mandates linkages between development tasks and defects (collectively called work items) to test cases. Out of the box a report of test cases to run based on the work items that were modified is available.

This solution proposes a self learning method/System to provide additional precision to that report based on code changes. Additionally test cases needed to be run based on lines of code proposed to be changed (test impact) can be generated that is not available in ALM products based on Workitem, Testcase linkages.

Code change sets are associated with work items. It proposes to build a mapping of code modules(functions/methods) and work items. This mapping is maintained at 4 levels or precision - group of lines of code, function , class and package for code identification. This mapping is updated or created whenever there is a new code checkin (change set). This mapping then allows for finding the work items and the test cases mapped to the work items .

In a ALM system used for development

Every code checkin is via a change set and is associated with 1-n number of development items / defect
Every test case is associated with 1-n number of work items.

    Every work item can have 0-n dependent workitems
In agile environment, whenever a new feature / functionality is delivered, a corresponding test case/s is also delivered with it. ALM tools keep a traceability link between test cases and the development items. The work item can be a new development task o...