There is no single test for even a small part of source code. How to determine which test case is better, how to determine which is more efficient?

These questions were already asked. But what about automatically rating how good are unit test cases?

If we were only able to rate ones unit tests and give him clear guides what is wrong, then we would be at home.

So it’s all about visually supporting user in delivering better unit tests.

Deadline: june 08. Mentor: Ph.D. B. Walter

april 2008 - develop an experimental solution may 2008 - optimize, experiment june 2008 - defend my msc

12-07-2007 first readings done:

“Aspect-oriented Response Injection: an Alternative to Classical Mutation Testing” - Bogacki, B., Walter, B., 2006, in IFIP International Federation for Information Processing. Volume 227 (“Software Engineering Techniques: Design for Quality”), ed. K. Sacha, (Boston: Springer), pp. 273-282.

“Evaluation of Test Code Quality with Aspect-Oriented Mutations” - Bogacki, B., Walter, B., 2006, in LNCS 4044 (“Extreme Programming and Agile Processes in Software Engineering”), eds. P. Abrahamsson, M. Marchessi, and G. Succi, Springer Verlag, pp. 202-204.

01-12-2007 thinking…

03-2008 talked with my supervisor, other students with similar theses