Mar 11th, 2008, 11:08 AM
Why do we write java classes for Unit Testing?
So far there are lot of unit testing frameworks available today to choose from. Each stands with different approach.
But the matter of fact is, we still need to code. Can we not configure beans what we want to test and actual and expected results?
Imagine a world where we write unit tests, if it's not so complex, in xml instead of creating lot of classes.
So here is an idea for a framework where you write your unit test cases in xml and not create any classes.
The framework provides a helpers/wrappers around various unit frameworks like Junit, TestNG, Jmock etc.
It reads the definition of test case and data providers and generates TestCase using any of above specified Unit Testing frameworks and executes it. We can even set-up some callback mechanism for better control over automated behavior.
Mar 11th, 2008, 12:02 PM
FIT use a table approach. It even knows how to parse tables out several document types including HTML and Word. This tends to be for functional tests. And you still need to write a fixture in a compiled language.