 +91 20-67 117 117  info@prototechsolutions.

com BLOGS NEWS EVENTS CAREERS

HOME SERVICES  COMPANY CLIENTS  PRODUCTS  CONTACT 

Home / Technical Support and Quality Assurance, Regression Testing, UI, Quality Assurance, Technology, Manual AutomationQA, Test management, Testing / 9 Tips for selecting test cases for Regression Testing

9 Tips for selecting test cases for Regression Testing Subscribe

Name
Regression testing is selective retesting of a system or component to verify that
modi cations have not caused unintended e ects in previously working modules of
Email*
software/application. This type of testing is typically associated either as a ‘challenge’ or
‘unimportant’ by developers; but a good tester always enjoys breaking the software to scour
out each and every fault from it. Having said that even regression testing can become a Submit
challenge for the testers as well. Here are some of the reasons:-

1. The Number of test cases in regression suite increases with each new feature.
Post Categories
2. Sometimes, the execution of entire regression test suite becomes di cult due to time and budget
constraints.
3. Minimizing test suite while achieving maximum test coverage is not a cake walk.  News (48)
4. Determination of frequency of Regression Tests after every modi cation or every build update or after
a bunch of bug xes is always a challenge.  3D Game Development (3)

The graph below depicts the same  Coding (3)

 Hence selecting test cases for regression testing is quite a tricky task. Today, I am sharing some tips that I  Technical Support and Quality
found to be most e ective while selecting test cases for regression testing Assurance (4)

Below are the 9 simple tips:-  Blogs (55)

1. Include the test cases which have frequent defects:
 Engineering (2)
Some areas in product are so error prone that they usually fail with a small change in code. We can keep
track of failing test cases due to such areas throughout the product cycle and cover them in regression
 Analytics For Desktop (1)
test suite.

2. Include the test cases which verify core features of the product:  Engg Interoperability (1)
Prior to designing of the test cases gure out all core features of application. Ensure that, test case cover
all functionality mentioned in requirement document. One can make use of traceability matrix to make  3D PDF (2)
sure that no requirement is left untested.
Example:- Client would never expect a Home Page/Login Page/Key functionalities of his application   Regression Testing (1)
getting failed.
 3D Visualization – Web (12)
3. Include the test cases for Functionalities which have undergone more and recent changes:-
SRS keeps on getting updated. Sometimes, the updates are not in full change to the previous SRS. But to  Web Based 3D Visualization (3)
some extent (may be 15-30 %) changes may happen for every version upgrade. We testers have to agree
that, it’s di cult to keep writing (modifying) test cases, as the SRS keeps on getting updated often and  AutoCAD (4)
this leads to some end moment internal defects and changes into the code which in turn might break
some already existing functionalities, So it’s a “Must” (a must with capital M ) to always include such test  UI (2)
cases which has recent changes.
 3D Visualization – Mobile (6)
4. Include all the Integration test Cases:
Even if Integration testing is a separate part of software testing cycle, its test cases should be included in  3D Mobile Visualization (2)
regression test suite.
A last moment x, in already tested application can break the integrity between di erent modules. For  Data Interoperability (2)
example, data might get lost across an interface, messages might not get passed properly or interfaces
might not be implemented as speci ed.  MFC (1)

5.  Include all Complex Test Cases:-  AR-VR Development (5)

Some functionality of the system may only be accomplished by following some complex sequence of GUI
events.  DWG/DXF (2)
For example, to open a le a user may have to click on the File Menu and then select the Open operation,
and then use a dialog box to specify the le name, and then focus the application on the newly opened  iOS Development (1)
window. Obviously, increasing the number of possible operations increases the sequencing problem
exponentially. This can become a serious issue even if one of the steps is not working—A whole  AR-VR Devpt (1)
functionality comes to HALT, and End-User feels like a crap . That’s why all such complex test case should
be included in regression test suite.
 Engineering Interoperability (3)

6. Prioritize the test cases for regression testing:

 Import and Export AutoCAD (1)
“A stitch in time saves nine” …nay!!
We will go with “A SMART stitch in time (can) saves Ninety-nine”
 Inventor (1)
Prioritize the test cases depending on business impact, critical & frequently used functionalities. It is
always helpful if some analysis is done to nd out what test cases are relevant and what are not. It is a  Quality Assurance (3)
good approach to plan and act for regression testing from the beginning of project before the test cycles.
One of the ideas is to classify the test cases into various Priorities based on importance and customer  3D CAD Plugins (5)
usage. Here it is suggested the test cases be classi ed into three categories;
 3D Scanning (1)

Priority-0 Priority-1 Priority-2  Graphics (1)

Sanity test This includes  These are executed as a  Gaming (3)

cases which the test cases part of ST cycle and
checks basic which tests selected for regression  CAD (5)
functionality essential testing on need basis.
(as per the functionalities These test cases deliver
 3DMAX (1)
SRS of that deliver moderate project value.
product) and high project
 OpenGL (1)
are run for value to both  
pre-system engineers and
 Game Testing (1)
acceptance customers.
and when
 Plugin/Translators (4)
product goes
through
 3DPDF (1)
major
change.
These test  3DPDFExport (1)
cases deliver
a very high  BIMSync (1)
project value
to both  OBJ (2)
engineers and
to customers.  Manual and Automation QA (1)

Selection of test cases based on priority will greatly reduce e orts spent on regression testing.  Technology (2)

7. Categorize the selected test cases: –  Automation Testing (1)

Regression testing becomes very di cult when the application scope is very huge and there are
 Manual AutomationQA (3)
continuous increments or patches to the system. In such cases selective tests needs to be executed in
order to save testing cost and time. Categorizing test cases makes this work easier. We can categorize
 3D Visualization – Desktop (17)
them as
1) Reusable Test Cases:
 HOOPS (3)
It includes test cases which can be repetitively used in succeeding regression cycles. This can be
automated so that set of test cases can be easily executed on new build.  Events (18)
2) Obsolete Test Cases:
These test cases are defect speci c and can’t be used in succeeding cycles. Smart way is to use them is  Software Testing (5)
when relative defect occurs.
 Onshape (1)
8. Choose the test cases on “Case to Case” basis:
 Web Based 3D Visualization (4)
There could be several right approaches to regression testing which needs to be decided on “case to
case” basis:  Test management (2)

•Case 1: If the criticality and impact of the bug xes are LOW, then it is enough that a test engineer  3D Engineering (1)
selects few test cases from TCDB (Test case DB) and executes them. These test cases can fall under any
Priority (0, 1 or 2).  3D Mobile Visualization (5)

•Case 2: If the criticality and the impact of the bug xes are Medium, then we need to execute all Priority-  Success Stories (16)
0 and Priority-1 test cases. If bug xes need additional test cases from Priority-2, then those test cases
can also be selected and used for regression testing. Selecting Priority-2 test cases in this case is
 Testing (2)
desirable but not a must.

 3D Services (2)
•Case 3: If the criticality and impact of the bug xes are High, then we need to execute all Priority-0,
Priority-1 and carefully selected Priority-2 test cases.
 CAD/CAM Customization (18)

•Case 4: One can also go through the complete log of changes that happened (can be obtained from
Con guration management engineer) because of bug xes and select the test cases to conduct
regression testing. This is an elaborate process but can give very good results. I hope this will help you to
nd out what test cases should be included in your regression test suite.
Archives

9. Change the regression test cases whenever required. Select Month

RESET of test case is not expected to be done often. Resetting of the test cases needs to be done with
following considerations;

Recent Post
a. When there is a major change in the product
b. When there is a change in the build procedure which a ects the product
c. Large release cycle, where some test cases were not executed for a long time  Skylynx – An Android App
d. You are in the nal regression test cycle with a few selected test cases
e. When there is a situation where the expected results of the test cases could be quite di erent from  IFC to OBJ and metadata |Revit
previous cycles. to OBJ and metadata |Helix
Revit Addin creator | RCS
Having said that “No use of reinventing the wheel again“, Converter
On similar lines why to execute test cases manually if we can automate them and reuse it?
 Forge Converter, Scheduler
Service
In RT Task, including an automation suite is always painless and feasible as it covers a wide area of
testing scenario. Infact Regression test suite should be 99.99% automated (It may require executing the
 Point cloud processor, Helix
RT task after every new build is red).
Matcher
Ahaa!! It sounds good, Running a test suite in night hours and getting test report in morning, what a start
to your day, when you realize your half of the work is already done.
 Want to render your own CAD
model in Autodesk Forge
With the fast proliferating gaming industry, games keep enhancing hour after hour. Thus regression
Viewer? Read on!
testing plays a pivotal role in game testing to keep the game functioning.

Guys, I hope this article will be useful for you. Correct me if I am wrong somewhere.  Meet us at AU Las Vegas 2019
(Booth – #AE260), Nov. 19-21
References:
 ProtoTech’s WebGL Exporter
1. isqtinternational.com/defect/images/2.doc Deep Insights
2. http://agile.csc.ncsu.edu/SEMaterials/BlackBox.pdf
3. http://www.ijaer.com/webmaster/upload/Apr_2012_Sheo%20Kumar.pdf  Apply Machine Learning to 3D
Data in 5 Quick Steps
Author: Abhira K.
Contact us:  Unfolding the evolution of
info@prototechsolutions.com Games and Gaming Industry
ProtoTech Solutions Pvt Ltd.

March 10th, 2013

ABOUT PROTOTECH SOLUTIONS

ProtoTech Solutions is a software development and consulting company that specializes in

rapid development of engineering software by providing fast, reliable and accurate
solutions. PTS is a private rm composed of well-trained and experienced professionals
who are fully committed to helping our customers accelerate their development programs
and build advanced solutions.
3D Services Recent Post Contact Other Links

3D Visualization – Desktop
3D Visualization – Web
3D Visualization – Mobile
CAD/CAM Customization & Plugins
Engineering Interoperability
Skylynx – An Android App ProtoTech Solutions and Services Blogs
Pvt. Ltd., Unit # 111, B Building, 1st
IFC to OBJ and metadata |Revit to News
Floor, GO Square, Aundh-
OBJ and metadata |Helix Revit Hinjewadi Road, Wakad, Pune –
Events
Addin creator | RCS Converter 411057
Success Stories
Forge Converter, Scheduler
Service  info@prototechsolutions.com Contact Us

AR-VR Development Point cloud processor, Helix Careers

 +91-20-67 117 117
Matcher
Quality Assurance
Want to render your own CAD
Game Testing
model in Autodesk Forge Viewer?    
Read on!

Copyright 2020 ProtoTech Solutions | All Rights Reserved | Legal | Privacy | Powered by Skovian Ventures