General
DatabasesGood question. The underlying libaries are stable, and can be trusted.
The test libary itself is in good shape. I would not expect very many bugs to surface here.
The Eclipse plugin should be considered unstable. However, errors in this plugin would only affect your development environment, not your production system. I really need help with testing this plugin.
| [top] |
Both the test library and the eclipse plugin are licensed under the Apache license, version 2.
| [top] |
Because I am doing this on my spare time, and annotations is really the easiest way of making the kind of tooling needed for Testaco.
I will personally not backport these annotations to something like Xdoclet, even if it is perfectly possible to do so. I have no code I need to be backwards compatible with. I see that other people may not be so lucky. Sorry.
Another reason for not backporting is that Testaco is a testing tool which does not depend on any deployment structures. Who says you can't use JDK 5 for behavioural testing outside of your production system?
| [top] |
I know. I am a server-side developer, and I know next to nothing about Eclipse other than what I have been able to find in books and on the web. Therefore I also lack a toolkit of patterns that work in Eclipse.
Constructive suggestions for improvements are very welcome.
| [top] |
Well spotted. I subscribe to a view that you have to stop testing somewhere. I usually don't test my own test structures - I try to make them in such a way that the tests break instead.
And now, those testing structures all of a sudden are a deliverable of their own. Yes, I really, really should have more tests.
| [top] |
Uh. Don't know.
| [top] |
Because that is the only database I have been working with recently. Adding support for other databases should, however, be very easy. Come back when there is a bug tracker configured for the site and log an improvement request, please.
| [top] |
