Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
gLite-CLUSTER Test work plan | ||||||||
Line: 140 to 140 | ||||||||
Glue 1 compliance | ||||||||
Changed: | ||||||||
< < | Glue 1 compliance of the information published by the gLite-CLUSTER resource bdii should be tested. This should be done using [[https://tomtools.cern.ch/confluence/display/IS/GLUEValidator]GlueValidator]]. | |||||||
> > | Glue 1 compliance of the information published by the gLite-CLUSTER resource bdii should be tested. This should be done using GlueValidator. | |||||||
Changed: | ||||||||
< < | Status: Implemented in the GlueValidator testsuite | |||||||
> > | Status: Implemented in the GlueValidator testsuite | |||||||
Glue 2 compliance | ||||||||
Changed: | ||||||||
< < | Glue 2 compliance of the information published by the gLite-CLUSTER resource bdii should be tested. This should be done using [[https://tomtools.cern.ch/confluence/display/IS/GLUEValidator]GlueValidator]]. | |||||||
> > | Glue 2 compliance of the information published by the gLite-CLUSTER resource bdii should be tested. This should be done using GlueValidator. | |||||||
Changed: | ||||||||
< < | Status: Implemented in the GlueValidator testsuite | |||||||
> > | Status: Implemented in the GlueValidator testsuite | |||||||
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
gLite-CLUSTER Test work plan | ||||||||
Line: 43 to 43 | ||||||||
Basic functionality tests | ||||||||
Added: | ||||||||
> > | VO tag dir testCheck if under/opt/glite/var/info there is a directory for each subcluster.
Check that within each of these directories, there is a directory per VO which contains a file called <VO name>.list
Status: Not Implemented | |||||||
Resource BDII test | ||||||||
Added: | ||||||||
> > | Check if the resource bdii publishes all the relevant objectclasses for both glue1 and glue2.
ldapsearch -h <gLite-CLUSTER hostname> -x -p 2170 -b "o=grid" objectclass=GlueCluster
ldapsearch -h <gLite-CUSTER hostname> -x -p 2170 -b "o=grid" objectclass=GlueSubCluster
ldapsearch -h <gLite-CUSTER hostname> -x -p 2170 -b "o=glue" objectclass=GLUE2ComputingService
ldapsearch -h <gLite-CUSTER hostname> -x -p 2170 -b "o=glue" objectclass=GLUE2Manager
| |||||||
Changed: | ||||||||
< < | TBD | |||||||
> > | ldapsearch -h <gLite-CUSTER hostname> -x -p 2170 -b "o=glue" objectclass=GLUE2Share
ldapsearch -h <gLite-CUSTER hostname> -x -p 2170 -b "o=glue" objectclass=GLUE2ExecutionEnvironment
ldapsearch -h <gLite-CUSTER hostname> -x -p 2170 -b "o=glue" "(&(objectclass=GLUE2ComputingEndPoint)(GLUE2EndpointInterfaceName=org.glite.ce.ApplicationPublisher))"Status: Not Implemented Dynamic information testLog as root on the gLite-CLUSTER node and execute:/sbin/runuser -s /bin/sh ldap -c "/var/lib/bdii/gip/plugin/glite-info-dynamic-lrms"This should print some information for the glue2 Glue2Manager objectclass and for each Glue2Share objectclass. Check if the printed information is correct. Query the resource BDII of the gLite-CLUSTER and check if the published information is the same as the one returned by the glite-info-dynamic-lrms script. Status: Not Implemented | |||||||
Regression tests | ||||||||
Line: 61 to 131 | ||||||||
Glue 1 compliance | ||||||||
Changed: | ||||||||
< < | Glue 1 compliance of the information published by the CREAM-CE resource bdii should be tested. This should be done using [[https://tomtools.cern.ch/confluence/display/IS/GLUEValidator]GlueValidator]]. | |||||||
> > | Glue 1 compliance of the information published by the gLite-CLUSTER resource bdii should be tested. This should be done using [[https://tomtools.cern.ch/confluence/display/IS/GLUEValidator]GlueValidator]]. | |||||||
Status: Implemented in the GlueValidator testsuite
Glue 2 compliance | ||||||||
Changed: | ||||||||
< < | Glue 2 compliance of the information published by the CREAM-CE resource bdii should be tested. This should be done using [[https://tomtools.cern.ch/confluence/display/IS/GLUEValidator]GlueValidator]]. | |||||||
> > | Glue 2 compliance of the information published by the gLite-CLUSTER resource bdii should be tested. This should be done using [[https://tomtools.cern.ch/confluence/display/IS/GLUEValidator]GlueValidator]]. | |||||||
Status: Implemented in the GlueValidator testsuite | ||||||||
Deleted: | ||||||||
< < | Inter-component testsTBD | |||||||
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Added: | ||||||||
> > |
gLite-CLUSTER Test work planUnit testsgLite-CLUSTER is just a set of yaim configuration scripts. So there are not unit tests.Deployment testsInstallationThe following should be tested:
ConfigurationThe configuration via yaim should be tested. The following scenarios should be tested:
System testsBasic functionality testsResource BDII testTBDRegression testsSee: http://wiki.italiangrid.it/twiki/bin/view/CREAM/RegressionTestWorkPlanPerformance and scalability testsNoneStandard compliance and conformance testsGlue 1 complianceGlue 1 compliance of the information published by the CREAM-CE resource bdii should be tested. This should be done using [[https://tomtools.cern.ch/confluence/display/IS/GLUEValidator]GlueValidator]]. Status: Implemented in the GlueValidator testsuiteGlue 2 complianceGlue 2 compliance of the information published by the CREAM-CE resource bdii should be tested. This should be done using [[https://tomtools.cern.ch/confluence/display/IS/GLUEValidator]GlueValidator]]. Status: Implemented in the GlueValidator testsuiteInter-component testsTBD -- MassimoSgaravatto - 2011-12-29 |