Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Added: | ||||||||
> > | VOMS Admin test plan1 Unit tests2 Deployment tests2.1 MySQL Backendyum install emi-voms-mysqlinstalls cleanly on an SL5 x86_64 and SL x86_64 machine configured as described in the EMI 1 and EMI2 Generic Installation and Configuration guide. 2.2 Oracle Backendyum install emi-voms-oracleinstalls cleanly on an SL5 x86_64 and SL x86_64 machine configured as described in the EMI 1 and EMI2 Generic Installation and Configuration guide. 2.3 System tests2.3.1 Basic functionality tests2.3.1.1 Administrative registration of a VO member2.3.1.1.1 Normal workflowUse "create-user" to register a new VO member by
2.3.1.1.2 Pass/Fail Criteriavoms-admin create-user exits with code 0 and list-users returns its DN as a registered member.2.3.1.1.3 Erroneous workflow
2.3.1.1.4 Pass/Fail CriteriaTest succeeds if an appropriate error message is printed and the exit code is 1.2.3.1.2 Groups and role creation2.3.1.2.1 Normal workflowUse create-group and create-role to register new VO groups/roles.2.3.1.2.2 Pass/Fail Criteriavoms-admin should exit with code 0. list-groups/list-subgroups and list-roles should display the newly created entities.2.3.1.2.3 Erroneous workflowTry to create a role/group that already exists or subgroup that full name does not start with "/vo_name/".2.3.1.2.4 Pass/Fail CriteriaAn error should be displayed to the user and voms-admin should exit with code 1.2.3.1.3 Attribute class registration2.3.1.3.1 Normal workflow and Pass/Fail Criteriause create-attribute-class to register a new one. Verify both the creation of classes with UNIQUE enforcement and without. The test succeeds if voms-admin exits with code 0 and list-attribute-classes contains the new ones.2.3.1.3.2 Erroneous workflow and Pass/Fail CriteriaIf the class already exists or the name contains illegal characters, voms-admin should print an error and exit with code 1.2.3.1.4 Users/groups/roles/classes deletion.Usedelete-user , delete-group , delete-role , delete-attribute-class to test deletion of VOMS entities. The test succeeds if voms-admin exits with code 0 and subsequent calls to the list command does not show the erased objects.
2.3.1.5 Group membership operationsTests for adding/removing/listing of group members usingadd-member , remove-member , list-members
2.3.1.5.1 Normal workflow and Pass/Fail Criteria
2.3.1.5.2 Erroneous workflow and Pass/Fail Criteriavoms-admin should print an error message and exit with code 1 if any of the following events occur:
2.3.1.6 Role assignments/dismissals2.3.1.6.1 Normal workflow and Pass/Fail CriteriaUse the assign-role and dismiss-role commands to verify the role management operations. assign-role should be tested with multiple roles for a single context.2.3.1.6.2 Erroneous workflow and Pass/Fail Criteria
2.3.1.7 Setting/Deleting attribute class values for users, groups, role/groupTest of the voms-admin commands
2.3.1.7.1 Erroneous workflow and Pass/Fail Criteriavoms-admin should exit with code 1 and print an error message if the commands are
2.3.1.8 Managing VOMS-ADMIN access control listsThe commandsadd-ACL-entry and remove-ACL-entry should be tested to modify the ACL for the top VO group and group hierarchy. The test passes if subsequent call to get-ACL for that contexts lists the new ACE.
Access control entries for the following subjects should be checked:
2.3.1.9 Managing VOMS-ADMIN default access control lists2.3.1.9.1 Normal workflow and Pass/Fail CriteriaAccess control entries are added in the default ACL for a context. Then a subgroup is created and the contents of its ACL is inspected with the get-ACL command. It should correspond to the contents of the default ACL of the parent. In this case the test is considered successful.2.3.2 Web interface2.3.2.1 VO registration serviceTesting the VOMS-ADMIN web interface as a regular user.2.3.2.1.1 Normal workflow and Pass/Fail Criteria
2.3.3 Regression tests2.3.3.1 [VOMS Admin] VOMS Admin CA update functionality fails with EGI-trustanchors CA 1.38 (https://savannah.cern.ch/bugs/?78349)Check that VOMS Admin installation and configuration works as expected with EGI trust anchors >= 1.38.2.3.3.2 [VOMS Admin] VOMS-admin AUP signing request behaviour broken for user with no AUP acceptance record (https://savannah.cern.ch/bugs/?78350)Create two users without AUP record, have one user sign the AUP and check that the other still receive a Sign AUP email2.3.3.3 [VOMS Admin] "Add to group" dialog broken (https://savannah.cern.ch/bugs/?78881)Create 2 groups in the VO. Create a user. Check the add to group dialog in the user page allows the administrator to select any of the newly created groups2.3.3.4 [VOMS Admin] "more info" link in group search users tab broken (https://savannah.cern.ch/bugs/?79087)Create a user in the VO. Search the VO root group and check that the "more info" referring to the cretead user is not broken.2.3.3.5 [YAIM VOMS] Adaptive setting of MaxPermSize according to the number of configured VOs (https://savannah.cern.ch/bugs/?80172)Configure a large number of VOs with YAIM (> 10) and check that the MaxPermSize Java VM parameter is set in a way that is proportional to the number of VOs2.3.3.6 [VOMS Admin] Database upgrade fails when usr table contains duplicated entry (https://savannah.cern.ch/bugs/?80308)Starting from a VOMS Admin 2.0.x database, insert a duplicated entry in the usr table and try the upgrade of the database. The upgrade script should warn of the presence of a duplicated entry and succed.2.3.3.7 [VOMS Admin] Confirmed pending VO membership requests are incorrectly deleted from database (https://savannah.cern.ch/bugs/?80685)Configure the expired request purger thread to excecute every 10 sec. Request membership to the VO. As a VO admin accept the membership request. Check that the expired request purger does not delete the just confirmed request from the database.2.3.3.8 [VOMS Admin] Uncaught exception shown in group membership search pane (https://savannah.cern.ch/bugs/?80892)Using the voms-admin CLI create two users with the same ceritificate subject and different CAs. Check that the root VO group membership search pane shows the two users as expected and no exception is thrown.2.3.3.9 [VOMS Admin] VOMS Admin does not resolve correctly email addresses for role an group administrators (https://savannah.cern.ch/bugs/?80945)Create a user, assign him the VO-Admin role. Check that the user receives VOMS Admin notifications for incoming user requests.2.3.3.10 [VOMS Admin] VOMS Admin SIGN AUP default grace period is too short (2.3.4 Performance and scalability testsN/A2.3.5 Standard compliance and conformance testsN/A2.3.6 Inter-component tests2.3.6.1 MkGridmapCheck that mkgridmap script work as expected against VOMS Admin service -- AndreaCeccanti - 2012-04-27 |