Karsten Hilbert wrote:
http://salaam.homeunix.com:8080/gnumed-test-war
Not bad at all. Needs lots of polishing but at least you get the sense
that Gnumed is a working system.
Well, we had times when even in the Python client about 2/3rds
of this were working, too. They were deemed not looking good
enough (not my fault) or not "properly" implemented (my fault)
and hence fell into disrepair.
Good enough or not, surely it would have been possible to take a
snapshot of these so that you (collectively) and others could compare
the "better" solutions which followed with the "not good enough"
solutions which preceded them? Either keep a frozen version in its own
branch in the CVS, or make a tarball and archive it separately? It's not
like a finite set of Lego in which you have to dismantle one project in
order to build another.
Surely, the Python client is
"harder" to test.
What automated testing tool do you (collectively) have in mind to carry
out functional testing when the GUI client is complete?
Tim C
_______________________________________________
Gnumed-devel mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/gnumed-devel
