Elena,
Few comments :
* 3.1, Item 3 : " Differentiate complete failure of a command (which may
trigger a rollback) from a partial failure (the command failed in a
small subset of target only which may not require a rollback);"
-----What does the above mean ? The replication framework has the
feature to let commands rollback their changes in case of failures. But
so far only auth-realm related commands are planning to use this
"rollback" feature. So, you may want to set your plans clearly for the
above item.
* 3.1, Item 5 : Deployment does use supplemental command to send bits to
the instances but does not work as detailed here. Exact detail of how
deployment works is here
<
http://wikis.sun.com/display/GlassFish/V3.1Clustering#V3.1Clustering-Deploymentinclusteredenvironment>.
Having said that, how are you planning to test Supplemental commands
separately ? If your approach is to use CLIs or write some white box
kind of test cases ?
* 3.1, Item 6 : Note that target option is not mandatory. So if no
target option is specified, the behavior should be same as 3.0. You may
want to cover this also.
* (Tom probably already asked this Q) Do you plan to test multi machine
scenario also ? If so, do you have any info on the type of config you
are going use ?
Vijay
On 7/27/10 4:59 PM, Elena Asarina wrote:
> Hello,
>
> Please review Clustering Infrastructure (Syncronization, Dynamic
> reconfiguration) testing one pager:
>
> http://agni-1.sfbay.sun.com/net/asqe-logs/export1/v3.1/docs/sqe//ClusteringInfrastructure_one_pager.html
>
>
> Thank you,
> Elena
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>