@@ -22,12 +22,11 @@ for relevant licenses.
22
22
## 1. Preparations
23
23
24
24
See [ INSTALL] ( https://oracle.github.io/node-oracledb/INSTALL.html )
25
- for installation requirements and more details.
25
+ for installation details.
26
26
27
27
Note: the
28
28
[ test suite] ( https://github.com/oracle/node-oracledb/tree/master/test )
29
- is in GitHub. From node-oracledb 1.9.1 it is not included when
30
- installing from npmjs.com with ` npm install oracledb ` .
29
+ is on GitHub. NPM module has not contained the tests since node-oracledb 1.9.1.
31
30
32
31
### 1.1 Create a working directory
33
32
@@ -63,27 +62,10 @@ The test suite uses [mocha](https://www.npmjs.com/package/mocha),
63
62
64
63
### 1.4 Configure Database credentials
65
64
66
- The database credentials for node-oracledb test suite are defined in ` dbconfig.js ` .
67
- They can also be set via environment variables shown in that file.
65
+ The file ` test\dbconfig.js ` contains the configuration. Change the credential information to yours.
68
66
69
-
70
- ```
71
- vi <some-directory>/node-oracledb/test/dbconfig.js
72
- ```
73
-
74
- ``` javascript
75
- module .exports = {
76
- user : process .env .NODE_ORACLEDB_USER || " hr" ,
77
- password : process .env .NODE_ORACLEDB_PASSWORD || " welcome" ,
78
- connectString : process .env .NODE_ORACLEDB_CONNECTIONSTRING || " localhost/orcl"
79
- };
80
- ```
81
-
82
- To enable external authentication tests, please make sure Oracle Database
83
- and the authentication service have been appropriately configured. See
84
- [ Documentation for External Authentication] ( https://oracle.github.io/node-oracledb/doc/api.html#extauth )
85
- for more details. And then, set the environment variable ` NODE_ORACLEDB_EXTERNALAUTH `
86
- to be ` true ` .
67
+ To enable external authentication tests, firstly make sure the Oracle external authentication service is correctly configured.
68
+ See [ Documentation for External Authentication] ( https://oracle.github.io/node-oracledb/doc/api.html#extauth ) for details.
87
69
88
70
Note: the test suite requires a schema with privileges CREATE TABLE, CREATE SESSION,
89
71
CREATE PROCEDURE, CREATE SEQUENCE, CREATE TRIGGER.
@@ -124,22 +106,14 @@ shows the numbering of tests.
124
106
In order to include your tests in the suite, add each new test file
125
107
name to [ ` test/opts/mocha.opts ` ] ( https://github.com/oracle/node-oracledb/blob/master/test/opts/mocha.opts ) .
126
108
127
- ## 4. Compatibility
128
-
129
- We basically test with the following environment options:
130
-
131
- - Oracle Instant Clients: 11.2.0.4, 12.1.0.2, 12.2.0.1
132
- - Operating Systems (X64): macOS, Linux, Windows
133
- - Node.js LTS versions
134
-
135
- ## 5. Troubleshooting
109
+ ## 4. Troubleshooting
136
110
137
111
You may encounter some troubles when running the test suite. These troubles
138
112
might be caused by the concurrency issue of Mocha framework, network latencies,
139
113
or database server issues. This section gives some issues that we ever saw
140
114
and our solutions.
141
115
142
- ### 5 .1 ORA-00054: resource busy and acquire with NOWAIT specified or timeout expired
116
+ ### 4 .1 ORA-00054: resource busy and acquire with NOWAIT specified or timeout expired
143
117
144
118
This error occurs when Node.js programs try to change database objects which
145
119
hold locks. The workaround would be:
@@ -149,7 +123,7 @@ test files.
149
123
(2) Try not to use 'beforeEach' blocks for object operations to avoid
150
124
the interference between cases.
151
125
152
- ### 5 .2 ORA-00018: maximum number of sessions exceeded
126
+ ### 4 .2 ORA-00018: maximum number of sessions exceeded
153
127
154
128
This error occurs when the test suite takes up more sessions than the
155
129
configured limit. You can alter the session limit on the database server side.
166
140
done
167
141
```
168
142
169
- ### 5 .3 ORA-28865: SSL connection closed
143
+ ### 4 .3 ORA-28865: SSL connection closed
170
144
171
145
You may encounter this error when the test suite sends more connection
172
146
requests per second than the database is configured to handle.
0 commit comments