Menu
▾
▴
[Firebird-test] Test will not connect to database (rather long)
|
From: Jeff J. - S. <J_...@MC...> - 2008-03-27 23:04:19
|
Dear all,
If you have been following the saga of getting qmTest working for me,
you will know that I have been at this for more than a week. I don't
want to give up on it yet, because I think this would be a good solution
for what we need. So, if anyone can offer advice, suggestions, or
whacks on the side of the head, I am ready.
I want to describe what I am doing with qmTest and qmEditor so that you
may be able to see where I have gone wrong, or you may be able to
suggest things to try that have not already been suggested.
I was running Firebird 1.5 as a service, but Philippe suggested running
it as an application, so I made that change.
My context file:
temp_directory=C:\fbtest\temp\
server_location=127.0.0.1/3040:
database_location=C:\fbtest\temp\
suite_database_location=C:\fbtest\fdb\
backup_location=C:\fbtest\fbk\
files_location=C:\fbtest\files\
isc4_path=C:\Program Files\Firebird\Firebird_1_5\security.fdb
user_name=SYSDBA
user_password=masterkey
isql_path=C:\Program Files\Firebird\Firebird_1_5\bin\isql.exe
gsec_path=C:\Program Files\Firebird\Firebird_1_5\bin\gsec.exe
gstat_path=C:\Program Files\Firebird\Firebird_1_5\bin\gstat.exe
gbak_path=C:\Program Files\Firebird\Firebird_1_5\bin\gbak.exe
#nbackup_path=C:\Program Files\Firebird\Firebird_1_5\bin\
gfix_path=C:\Program Files\Firebird\Firebird_1_5\bin\gfix.exe
gpre_path=C:\Program Files\Firebird\Firebird_1_5\bin\gpre.exe
database_name=test.fdb
The fbclient.dll file is in the c:\fbtest directory.
My batch file to launch qmEdit:
cd..
cd /fbtest
qmedit.py
This does launch qmEditor successfully.
In qmEditor, select the New Test button.
Test ID: oj.local.database.table_create
Test File: oj.local.database.table_create
Target Version: 1.5.4
Target Platform: Windows
On Identification page:
Title: Create a table
Bug/Issue ID: <blank>
Author: jonesj
On Database page:
Database Creation Method: Restore From Backup
Database Name / DSN: ojlocal.fdb
Database Path property: database_location
SQL Dialect: 3
Character Set: NONE
Page Size: 8192
User Name: SYSDBA
User Password: masterkey
Backup File: ojlocal.fbk
On Initialisation page: NO CHANGES
On Test page: NO CHANGES
On Finalisation page: Drop Database is checked
After saving the test, I run it, and it passes. (I checked that the
database is actually being restored from the backup, and that is working
correctly.) I expect this, since it is not trying to do anything
unusual. What I really want to do is create a table in the database.
So ...
On the Test page, I select the Python / SQL code tab.
Statement Type and Result: SQL: String
And the value is:
CREATE TABLE MYTEST (ID INTEGER, MYNAME VARCHAR(50));
After saving the test again, I run it. Here is the QMTest Output:
--- TEST RESULTS
-------------------------------------------------------------
oj.local.database.table_create : FAIL
Expected error output from ISQL does not match actual error output.
FirebirdTest.ISQL_stderr_actual:
Statement failed, SQLCODE = -924
bad parameters on attach or create database
Use CONNECT or CREATE DATABASE to specify a database
Use CONNECT or CREATE DATABASE to specify a database
FirebirdTest.ISQL_stderr_actual_stripped:
Statement failed, SQLCODE = -924
bad parameters on attach or create database
Use CONNECT or CREATE DATABASE to specify a database
Use CONNECT or CREATE DATABASE to specify a database
FirebirdTest.ISQL_stderr_expected:
FirebirdTest.ISQL_stderr_expected_stripped:
FirebirdTest.ISQL_stderr_stripped_diff:
+ Statement failed, SQLCODE = -924
+ bad parameters on attach or create database
+ Use CONNECT or CREATE DATABASE to specify a database
+ Use CONNECT or CREATE DATABASE to specify a database
qmtest.end_time:
2008-03-27T22:36:15Z
qmtest.start_time:
2008-03-27T22:36:09Z
qmtest.target:
local
--- TESTS THAT DID NOT PASS
--------------------------------------------------
oj.local.database.table_create : FAIL
Expected error output from ISQL does not match actual error output.
--- STATISTICS
---------------------------------------------------------------
1 tests total
1 (100%) tests FAIL
So, why would this fail? Do I need to connect to the database first?
Okay, lets try that.
On the Test page, and the Python / SQL code tab, delete the previous
command, and enter:
CONNECT '127.0.0.1/3040:C:\fbtest\temp\ojlocal.fdb' user 'SYSDBA'
password 'masterkey';
Save and run, and this is the QMTest Output:
--- TEST RESULTS
-------------------------------------------------------------
oj.local.database.table_create : FAIL
Expected error output from ISQL does not match actual error output.
FirebirdTest.ISQL_stderr_actual:
Statement failed, SQLCODE = -924
bad parameters on attach or create database
Use CONNECT or CREATE DATABASE to specify a database
Statement failed, SQLCODE = -924
bad parameters on attach or create database
FirebirdTest.ISQL_stderr_actual_stripped:
Statement failed, SQLCODE = -924
bad parameters on attach or create database
Use CONNECT or CREATE DATABASE to specify a database
Statement failed, SQLCODE = -924
bad parameters on attach or create database
FirebirdTest.ISQL_stderr_expected:
FirebirdTest.ISQL_stderr_expected_stripped:
FirebirdTest.ISQL_stderr_stripped_diff:
+ Statement failed, SQLCODE = -924
+ bad parameters on attach or create database
+ Use CONNECT or CREATE DATABASE to specify a database
+ Statement failed, SQLCODE = -924
+ bad parameters on attach or create database
qmtest.end_time:
2008-03-27T22:39:44Z
qmtest.start_time:
2008-03-27T22:39:39Z
qmtest.target:
local
--- TESTS THAT DID NOT PASS
--------------------------------------------------
oj.local.database.table_create : FAIL
Expected error output from ISQL does not match actual error output.
--- STATISTICS
---------------------------------------------------------------
1 tests total
1 (100%) tests FAIL
Everything I do seems to keep coming back to this: the test portion is
not connecting to the database.
What can I do? I am at a loss to know what else to try. The solution
seems tantalizingly close, but it's not there yet!
Please, if you can help me figure out what I need to do to get qmTest
working for me, I will be deeply grateful.
Thanks!
Jeff Jones
|
