SignatureTests
From APIDesign
(New page: -- Signature Testing Tools * [http://wiki.netbeans.org/view/SignatureTests NetBeans signature tests]) |
|||
| Line 1: | Line 1: | ||
| - | + | Since the rise of [[XP]] and other [[Agile]] methodologies testing become more and more popular. Not only among dedicated quality departments, but also among developers. It is not surprising that these days a successful projects is not just code, but also set of tests to verify that the release is good enough and that the project moves into correct direction. | |
| - | * [http://wiki.netbeans.org/view/ | + | The [[API Design]] is not exceptional in this aspect. Proper [[API Design]] requires testing and verification. The goal when designing an [[API]] is to prevent the [[Amoeba Model|amoeba shaking effect]] - e.g. prevent each new release to completely destabilize existing usages. This requires standard unit testing as well, as something special - testing for [[binary compatibility]]. |
| + | |||
| + | == Signature Testing Tools == | ||
| + | |||
| + | This is the Ant task that we use in NetBeans: | ||
| + | |||
| + | * [http://wiki.netbeans.org/view/APITests NetBeans signature tests] | ||
Revision as of 20:59, 4 January 2009
Since the rise of XP and other Agile methodologies testing become more and more popular. Not only among dedicated quality departments, but also among developers. It is not surprising that these days a successful projects is not just code, but also set of tests to verify that the release is good enough and that the project moves into correct direction.
The API Design is not exceptional in this aspect. Proper API Design requires testing and verification. The goal when designing an API is to prevent the amoeba shaking effect - e.g. prevent each new release to completely destabilize existing usages. This requires standard unit testing as well, as something special - testing for binary compatibility.
Signature Testing Tools
This is the Ant task that we use in NetBeans:
Follow
