Home: Building FDO Open Source
Configure the ArcSDE Server

Unit Tests

Run the GDAL Unit Tests
Run the ArcSDE Unit Tests
You initiate test execution from your machine. The
tests are executed on the machine hosting the ArcSDE server. The
ArcSDE server runs the tests in the Oracle or Sql Server database
depending on the command-line arguments that you provided.
Do the following in a cmd.exe window:
-
cd c:\OpenSource\Providers\ArcSDE\Src\UnitTest
-
..\..\bin\win32\debug\UnitTest.exe server=<dnsHostnameOrIPAddr>
port_multi=<port>/tcp port_single=<port>/tcp sdepwd=<sdeUserPassword> dataset=<datasetName>
rdbms=ORACLE
-
..\..\bin\win32\debug\UnitTest.exe server=<dnsHostnameOrIPAddr>
port_multi=<multiPort>/tcp port_single=<singlePort>/tcp
sdepwd=<sdeUserPassword> dataset=<datasetName> rdbms=SQLSERVER
NoteThe server value refers
to the machine hosting the ArcSDE server.
NoteThe port_multi and port_single
values are identical when the value of rdbms is ORACLE. The <port>
value is the one used by the ArcSDE server for Oracle to listen
for connection requests; you can obtain this value from the services
file on the machine hosting the ArcSDE server.
NoteThe port_multi and port_single
values are NOT identical when the value of rdbms is SQLSERVER. The
<multiPort> value is the one used by the ArcSDE server for
SQL Server to listen for connection requests to databases created
using the Enterprise Manager tool. The <singlePort> value
is the one used by the ArcSDE server for SQL Server to listen for
connection requests to the database that you created using the post
installation tool.
NoteThe dataset value is the
one that you specified when requested by the SetupTestData.perl
script.
All of the command-line arguments with the exception
of one are of the form <key>=<value>. The one exception
is an optional list of test suite names. This list can occur before
or after the <key>=<value> arguments. If no test suite
names are specified, all test suites are executed. The test suite
names follow:
- ABasicOpenTests
- BasicArcSDETests
- BasicConnectionTests
- BasicDeleteTests
- BasicInsertTests
- BasicSchemaTests
- BasicTransactionTests
- LockTests
- LongTransactionTests
- RecommitTest
- SelectAggregatesTests
- SelectTests
- SpatialContextTests
- SQLTests
- ThreadingTests
The following UnitTest.exe invocations provide
examples of the execution of the ThreadingTests suite in both Oracle
and SQL Server.
-
cd c:\OpenSource\Providers\ArcSDE\Src\UnitTest
-
..\..\bin\win32\debug\UnitTest.exe ThreadingTests
server=<dnsHostnameOrIPAddr> port_multi=<port>/tcp port_single=<port>/tcp
sdepwd=<sdeUserPassword> dataset=<datasetName> rdbms=ORACLE
-
..\..\bin\win32\debug\UnitTest.exe ThreadingTests
server=<dnsHostnameOrIPAddr> port_multi=<multiPort>/tcp port_single=<singlePort>/tcp
sdepwd=<sdeUserPassword> dataset=<datasetName> rdbms=SQLSERVER