IdentityRelatedInstallerTests
(Difference between revisions)
| Line 1: | Line 1: | ||
| - | |||
__NOTOC__ | __NOTOC__ | ||
This test specification is performed by installer QE team to verify correct installation and configuration for Identity runtime (Access Manager) and Identity tooling in IDE. | This test specification is performed by installer QE team to verify correct installation and configuration for Identity runtime (Access Manager) and Identity tooling in IDE. | ||
Current revision as of 18:25, 6 November 2009
This test specification is performed by installer QE team to verify correct installation and configuration for Identity runtime (Access Manager) and Identity tooling in IDE.
Identity related post-install tests
Purpose:Verify Identity runtime (AM) and Identity tooling successfull installation and configuration.
| Test ID | Test Procedure | Expected Results | OS | Type | Auto |
|---|---|---|---|---|---|
| IDENT_001 | Verify Identity tooling is installed correctly Install the IDE with AS, start IDE, start AS. Switch to runtime TAB. | 1.There should be 'Sun Java System Access Managers' node. 2. There should be 'Sun Java System Access Managers > Default Instance > Profiles > SAML-SenderVauches' node. 3. There should be 'Sun Java System Access Managers > Default Instance > Profiles > SAML-HolderOfKey' node. 4. There should be 'Sun Java System Access Managers > Default Instance > Profiles > X509Token' node. 5. There should be 'Sun Java System Access Managers > Default Instance > Profiles > UserNameToken' node. 6. There should be 'Sun Java System Access Managers > Default Instance > Profiles > LibertyX509Token' node. 7. There should be 'Sun Java System Access Managers > Default Instance > Profiles > LibertyBearerToken' node. 8. There should be 'Sun Java System Access Managers > Default Instance > Profiles > LibertySAMLToken' node. | - | ||
| IDENT_002 | Verify AM admin console is accessible 1. Go to the URL http://hostname:port/amserver (by default http://localhost:8080/amserver). 2. Login to console (by default username is 'amadmin' and password is 'admin123'). | Access Manager console opened successfully. | - | ||
| IDENT_003 | Verify Identity tooling is configured correctly 1. Select one of the security profiles under 'Sun Java System Access Managers > Default Instance > Profiles' node. 2. Right click on the profile and choose Edit. | Editor window opened without any error. | - |
Identity related post-uninstall tests
Purpose:Verify Identity runtime (AM) and Identity tooling successfull uninstallation.
| Test ID | Test Procedure | Expected Results | OS | Type | Auto |
|---|---|---|---|---|---|
| IDENT_004 | Verify AM configuration data is removed Stop AS, shutdown IDE, uninstall the IDE and AS. | 1. Directory specified in file under $User/AccessManager (by default 'AS_DIR/domains/domain1/config/amflatfiledir') is removed. 2. File under $User/AccessManager is removed. | - |
XML tools post-install tests
Purpose:Verify XML tools successfull installation.
| Test ID | Test Procedure | Expected Results | OS | Type | Auto |
|---|---|---|---|---|---|
| XML_001 | Check XML project 1. Create new project: select 'File->New Project...' in main menu, choose 'Java->Java Application', press 'Next' and 'Finish'). 2. Right-click 'Source packages' node of project, choose 'New->Other...' in popup menu. | Select XML category. The File Types list should contain 'Purchase Order Sample Schema' and 'Loan Application Sample Schema' items. | - |
Orchestration related post-install tests
| Test ID | Test Procedure | Expected Results | OS | Type | Auto |
|---|---|---|---|---|---|
| ORCH_001 | Verify SOA modules installation Install the IDE, start it. Click Tools->Plugins in the IDE main menu. Plugin Manager window opens. Switch to Installed tab. | 1. The following plugins should be installed and active: SOA Report Generation Framework, SOA, BPEL, BPEL Validation, Composite Application. | - | ||
| ORCH_002 | Verify runtime install and configuration 1. Install the IDE, start it. 2. Switch to runtime tab 3. Start GlassFish 4. Expand the GlassFish node | 1. There should be JBI node under the GlassFish node 2. There should be JBI->Service Engines->sun-bpel-engine node. 3. There should be JBI->Service Engines->sun-xslt-engine node. 4. There should be JBI->Binding Components->sun-http-binding node. | - |
