From: Skopalik S. <sko...@hl...> - 2002-09-10 08:53:59
|
> With SHOW statement, we'll be bound to the ISQL. I'd like implement > tests in Python instead whenever possible (at least for core set of > tests), just for reference. If any test fails, we have to investigate the > real source of this failure, including db layer. Using ISQL along with > Python/kinterbasdb will add one more layer to check. Or can you provide > us both, SHOW and system tables result checks ? In the worst case, I can > translate SHOW to system tables myself. > > Best regards > Pavel Cisar > http://www.ibphoenix.com > For all your upto date Firebird and > InterBase information I think, that test trough isql (or any else) is not problem, if any test fails, it easy locate why, but is hard to locate any fails before release. Else technique: many test can be realized as excepted effect on data like this test : SET TERM ^; CREATE PROCEDURE test RETURNS (id INTEGER)AS BEGIN id=1; END ^ CREATE PROCEDURE testd RETURNS (id INTEGER)AS BEGIN EXECUTE PROCEDURE test RETURNING_VALUES :id; END ^ /* Tested command: */ ALTER PROCEDURE test(aid INTEGER) RETURNS (id INTEGER)AS BEGIN id=aid; END ^ SET TERM ;^ EXECUTE PROCEDURE testd; /* Expected result: No Error. Additional checks: ID ============ 2 Slavek |