Automatically Repairing Test Cases for Evolving Method Declarations

Automatically
RepairingTest Cases
for Evolving Method Declarations
Mehdi Mirzaaghaei
Fabrizio Pastore
Mauro Pezzè
Università
della
Svizzera
italiana
http://swiss-landmarks.ch/panos/Lugano9.jpg

public class BankAccount {
private int balance;
public void deposit(int cents){
balance += cents;
}
public int getBalance(){
return balance
};
}
Software evolves

testDeposit(){
BankAccount account = new BankAccount();
int amount = 500;
account.deposit(amount);
assertEquals( 500, account.getBalance());
}
balance += cents;
}
return balance
};
}
Software evolves

public class .....
public class AccountUtil {
private double dailyInterestRate = 0.00005;
private int interestTerm=365;

public double interest(BankAccount account
return account.getBalance()
*dailyInterestRate*interestTerm;
}
...
public class AccountFactory {
public static BankAccount create( AccountContext ctx, boolean special ){
BankAccount account = new BankAcccount( ctx.amount );
if ( special ){
account.setInterestRate(0.0001);
}
...
public class .....
testDeposit(){
int amount = 500;
}
balance += cents;
}
return balance
};
}
Software evolves

balance += cents;
}
return balance
};
}
public void deposit(Money money){
balance += money.centsValue;
}
return balance;
};
}
Original classes are modiﬁed

public class .....
public class .....
Test cases need maintenance
testDeposit(){
int amount = 500;
}
balance += cents;
}
return balance
};
}
}
return balance;
};
}
Compilation error:
Method deposit(Money) in the type
BankAccount is not applicable for
the arguments (int)

changes in method declarations:
23% changes
that impact on compilation

23% changes
> 80% in maintenance releases

23% changes
> 80% in maintenance releases
Automatic Repair to Save Effort

[Memon et. al. 2008, Grechanik 2009 ]
Repair GUI tests
Well suited only for GUI tests
AutomaticTest Repair

Repair GUI tests Repair Oracles
[B. Daniel et al 2010]
testInterest(){
...
assertEquals( 50, result );
}
FAILURE: expected 50, found: 40
Well suited only for GUI tests Focus on oracles only

Repair GUI tests
Refactoring Techniques
[ReBa, Eclipse]
Repair Oracles
[B. Daniel et al 2010]
testInterest(){
...
}
FAILURE: expected 50, found: 40
//calculate one year interest
result = account.interest();
result = account.interest( 0 );
Well suited only for GUI tests Focus on oracles only
Prevent only some compilation errors

TestCareAssistant
repairs test case compilation errors
• Parameter add
• Parameter type change • Return type change
• Parameter remove
caused by method declaration changes

TestCareAssistant
testDeposit(){
int amount = 500;
assertEquals(500, account.getBalance());
• Parameter add

TestCareAssistant
testDeposit(){
int amount = 500;
Replace:
int amount = 500;
with:
Money amount = new Money(500);
• Parameter add

TestCareAssistant
testDeposit(){
int amount = 500;
testDeposit(){
Replace:
int amount = 500;
with:
• Parameter add

Repair parameter type change
balance += cents;
}
return balance;
}
}
balance += money.CentsValue;
}
return balance;
}
}
testDeposit(){
int amount = 500;
}
Version 0 Version 1

Which parameter to initialize?
balance += cents;
}
return balance;
}
}
}
return balance;
}
}
testDeposit(){
int amount = 500;
}
Version 0 Version 1

Which parameter to initialize?
Use code diff to identify the parameter1
balance += cents;
}
return balance;
}
}
}
return balance;
}
}
testDeposit(){
int amount = 500;
}
Version 0 Version 1

How to initialize a complex object?
balance += cents;
}
return balance;
}
}
}
return balance;
}
}
testDeposit(){
int amount = 500;
}
Version 0 Version 1

How to initialize a complex object?
Find ﬁrst uses of parameter ﬁelds inVersion12
balance += cents;
}
return balance;
}
}
}
return balance;
}
}
testDeposit(){
int amount = 500;
}
Version 0 Version 1

How to determine ﬁelds values?
balance += cents;
}
return balance;
}
}
}
return balance;
}
}
testDeposit(){
int amount = 500;
}
Version 0 Version 1

How to determine ﬁelds values?
Diff to identify corresponding variable inVersion 03
balance += cents;
}
return balance;
}
}
}
return balance;
}
}
testDeposit(){
int amount = 500;
}
Version 0 Version 1

What was the original value?
balance += cents;
}
return balance;
}
}
}
return balance;
}
}
testDeposit(){
int amount = 500;
}
Version 0 Version 1

What was the original value?
Analyze the def-use chain of the variable back to
the deﬁnition in the test4
balance += cents;
}
return balance;
}
}
}
return balance;
}
}
testDeposit(){
int amount = 500;
}
Version 0 Version 1

How can we repair the test?
balance += cents;
}
return balance;
}
}
}
return balance;
}
}
testDeposit(){
int amount = 500;
}
Version 0 Version 1

Instantiate the new object,
use original values to initialize ﬁelds5
balance += cents;
}
return balance;
}
}
}
return balance;
}
}
testDeposit(){
int amount = 500;
}
Version 0 Version 1

Instantiate the new object,
use original values to initialize ﬁelds5
Replace:
int amount = 500;
with:
balance += cents;
}
return balance;
}
}
}
return balance;
}
}
testDeposit(){
int amount = 500;
}
Version 0 Version 1

To what extentTestCareAssistant can
ﬁx test cases automatically?

• Repair 22 test cases of 6 open source systems
• Continuum, Geronimo, xml-security, PMD, POI, Shindig
• 24 compilation errors caused by different changes
• 9 parameter types changed, 8 parameters added, 3 parameters
removed, 4 return types changed

Results Total Repaired %
Test Cases 22 16 72
Compilation Errors 24 18 75
Values Initialized 36 29 80
• Repair 22 test cases of 6 open source systems
• Continuum, Geronimo, xml-security, PMD, POI, Shindig
• 24 compilation errors caused by different changes
• 9 parameter types changed, 8 parameters added, 3 parameters
removed, 4 return types changed

• Static data ﬂow analysis not always effective
• Use of complex data structures, e.g. hash tables
• Changes in method logic
• Changes in interfaces
Results Total Repaired %
Test Cases 22 16 72
Compilation Errors 24 18 75

Conclusions
balance += cents;
}
}
}
}
testDeposit(){
int amount = 500;
testDeposit(){
int amount = 500;

Conclusions
balance += cents;
}
}
}
}
testDeposit(){
int amount = 500;
testDeposit(){

Conclusions
balance += cents;
}
}
}
}
Replace:
int amount = 500;
with:
testDeposit(){
int amount = 500;
testDeposit(){
TestCareAssistant

Future Work
CopticChronology EthiopicChronology
Chronology
+ withUTC()
TestCopticUTC(){
....
assertEquals("AM",
copticChronology.withUTC() );
}

Future Work
Chronology
+ withUTC()
TestCopticUTC(){
....
assertEquals("AM",
}
TestEthiopicUTC(){
....
assertEquals("EE",
ethiopicChronology.withUTC()
}
Chronology
+ withUTC()

Future Work
Chronology
+ withUTC()
TestCopticUTC(){
....
assertEquals("AM",
}
TestEthiopicUTC(){
....
assertEquals("EE",
ethiopicChronology.withUTC()
}
Chronology
+ withUTC()
AutomateTest Generation by Identifying and
ImplementingTest Adaptation Patterns

Questions?
balance += cents;
}
}
}
}
Replace:
int amount = 500;
with:
testDeposit(){
int amount = 500;
testDeposit(){
TestCareAssistant

Automatically Repairing Test Cases for Evolving Method Declarations

More Related Content

What's hot (19)

Viewers also liked (7)

Similar to Automatically Repairing Test Cases for Evolving Method Declarations (20)

More from ICSM 2010 (15)

Automatically Repairing Test Cases for Evolving Method Declarations