search

collab-uniba / econference4

Automatically exported from code.google.com/p/econference4
0 stars 0 forks source link

[product, testing] Refactor JMock test cases and suites and evaluate to replace it with Mockito suite #65

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
For each feature in eConference, a test project exists. As changes to the code 
base occured, bug fixes applied and new features added, tests have become 
outdated.

Besides, only a few JMock tests were written. The impossibility of writing 
JMock test cases may indicate that there is no good separation betweeng UI and 
business code. Then, the idea here is to guide the refactoring of econference 
by refactoring / creating new JMock test cases.

Also explore the idea of using Mockito suite (http://mockito.org/) instead of 
JMock.

Original issue reported on code.google.com by calefato.uniba@gmail.com on 17 Dec 2010 at 11:08

GoogleCodeExporter commented 9 years ago

Original comment by calefato.uniba@gmail.com on 17 Dec 2010 at 11:12

GoogleCodeExporter commented 9 years ago 
Thesis title (in Italian): "Test Double framework: il caso di Mockito in 
eConference"

Original comment by calefato.uniba@gmail.com on 31 Mar 2011 at 9:25

GoogleCodeExporter commented 9 years ago

Original comment by calefato.uniba@gmail.com on 31 Mar 2011 at 9:25

GoogleCodeExporter commented 9 years ago

Original comment by calefato.uniba@gmail.com on 31 Mar 2011 at 9:26

GoogleCodeExporter commented 9 years ago

Original comment by calefato.uniba@gmail.com on 31 Mar 2011 at 9:28

GoogleCodeExporter commented 9 years ago

Original comment by calefato.uniba@gmail.com on 31 Mar 2011 at 9:28

GoogleCodeExporter commented 9 years ago 
This issue was closed by revision r804.

Original comment by davide.a...@gmail.com on 5 Apr 2011 at 3:48

GoogleCodeExporter commented 9 years ago

Original comment by calefato.uniba@gmail.com on 24 Apr 2011 at 8:52