When tested, place initials in box. If any issues were found, enter those details in Jira ticket
OPENPTK-310.
For each client / backend the minimum tests will include:
- CREATE
- UPDATE
- DELETE
- READ
- SEARCH
- PASSWORD CHANGE
- PASSWORD RESET (not implemented in CLI)
- FORGOT PASSWORD (not implemented in CLI)
API Unit Tests:
cURL:
A testing script has been added to the openptk/branches directory called testing. In that directory, you will find a curlTest.sh
which will execute Unix curl against several CONTEXTS being
implemented by an OpenPTK Server. To test, simply follow these
instructions.
- Startup OpenPTK Server
- Change directory to your openptk/branches/testing
- run
curlTest.sh
- Observe results
Please see NOTE under the CLI testing on how to change your testing against different CONTEXTS.
Example output from this test script:
$ ./curlTest.sh
Project OpenPTK CURL Testing Script (curlTest.sh)
=================================================
This script will use Unix curl to hit a
running server and backend services test
against expected output from several of the
OpenPTK Operations.
CONTEXTS Tested = Employees-Embed-JDBC Employees-MySQL-JDBC Employees-UnboundID-LDAP Employees-OpenDS-JNDI
OpenPTK Server = http://localhost:8080/openptk-server
Testing Employees-Embed-JDBC...
PASS - CREATE
PASS - READ
PASS - SEARCH
PASS - UPDATE
PASS - CHANGE_PASSWORD
PASS - RESET_PASSWORD
PASS - SET_FORGOT_PW
PASS - FORGOT_PASSWORD_1
PASS - FORGOT_PASSWORD_2
PASS - FORGOT_PASSWORD_3
PASS - DELETE
Testing Employees-MySQL-JDBC...
PASS - CREATE
PASS - READ
PASS - SEARCH
PASS - UPDATE
PASS - CHANGE_PASSWORD
PASS - RESET_PASSWORD
PASS - SET_FORGOT_PW
PASS - FORGOT_PASSWORD_1
PASS - FORGOT_PASSWORD_2
PASS - FORGOT_PASSWORD_3
PASS - DELETE
Testing Employees-UnboundID-LDAP...
PASS - CREATE
PASS - READ
PASS - SEARCH
PASS - UPDATE
PASS - CHANGE_PASSWORD
PASS - RESET_PASSWORD
PASS - SET_FORGOT_PW
PASS - FORGOT_PASSWORD_1
PASS - FORGOT_PASSWORD_2
PASS - FORGOT_PASSWORD_3
PASS - DELETE
Testing Employees-OpenDS-JNDI...
PASS - CREATE
PASS - READ
PASS - SEARCH
PASS - UPDATE
PASS - CHANGE_PASSWORD
PASS - RESET_PASSWORD
PASS - SET_FORGOT_PW
PASS - FORGOT_PASSWORD_1
PASS - FORGOT_PASSWORD_2
PASS - FORGOT_PASSWORD_3
PASS - DELETE
Test Results
============
PASSED = 44 / 44
FAILED = 0 / 44
Final Result: PASS
CLI:
A testing script has been added to the openptk/branches directory called testing. In that directory, you will find a cliTest.sh which will execute the OpenPTK CLI against several CONTEXTS being implemented by an OpenPTK Server. To test, simply follow these instructions.
- Startup OpenPTK Server
- Change directory to your openptk/branches/testing
- Set your CLI_HOME to be the home location of the OpenPTK CLI build or unziped distribution
- run
cliTest.sh
- Observe results
NOTE: This will default tests agains the following CONTEXTS:
- Employees-Embed-JDBC
- Employees-MySQL-JDBC
- Employees-UnboundID-LDAP
- Employees-OpenDS-JNDI
If you would rather run against a different set of backends, just set the environment variable CONTEXTS to the list of backends before you run the cliTest.sh:
# This will only test the Employees-Embed-JDBC service
$ export CONTEXTS="Employees-Embed-JDBC"
Example output from this test script:
$ ./cliTest.sh
Project OpenPTK CLI Testing Script (cliTest.sh)
===============================================
This script will use the OpenPTK CLI to hit a
running server and backend services test
against expected output from several of the
OpenPTK Operations.
CLI_HOME = /Users/tls/projects/svn/openptk/build/package/Apps/CLI/openptk-cli-2.0.0
CONTEXTS Tested = Employees-Embed-JDBC Employees-MySQL-JDBC Employees-UnboundID-LDAP Employees-OpenDS-JNDI
OpenPTK Server = http://localhost:8080/openptk-server
Running Tests
=============
Testing Employees-Embed-JDBC...
Testing Employees-MySQL-JDBC...
Testing Employees-UnboundID-LDAP...
Testing Employees-OpenDS-JNDI...
Checking Results
================
PASS - Employees-Embed-JDBC
PASS - Employees-MySQL-JDBC
PASS - Employees-UnboundID-LDAP
PASS - Employees-OpenDS-JNDI
Test Results
============
PASSED = 4 / 4
FAILED = 0 / 4
Final Result: PASS
UML:
In addition to the minimum tests, registration should be tested in this interface for at least 1 backend (Employees-Embed-JDBC).
IdentityCentral:
