Page 896 - Cloud computing: From paradigm to operation
P. 896

5                                            Intercloud and interoperability


                                                      Appendix I


                                                  Test case template
                            (This appendix does not form an integral part of this Recommendation.)


            Table  I.1  provides  a  test  case  template  to  describe  cloud  computing  infrastructure  capability  type
            interoperability testing  between the CSC and CSP. The test case template is designed with reference to
            relevant technical specifications. As shown in the table, an interoperability test case consists of test purpose,
            reference, test sequence and test verdict.
            –       Test purpose is a statement that specifies which test case to verify.
            –       Reference of the test case provides list of references to the base specification clause(s), use case(s),
                    requirement(s), etc. which are either used in the test or define the functionality being tested.
            –       The test sequences provide the steps required to perform the test. There are two types of test step.
                    A stimulus corresponds to an event that triggers a specific action on the object under test. There is
                    no need to provide result for a stimulus step. A check consists of observing that the object under
                    test behaves as described. A result must be provided for every check step. If the object under test
                    behaves as described in the description of the check step, the result should be recorded as OK,
                    otherwise the result should be recorded as fail.
            –       For every test case, test verdict should be provided to indicate whether the test is passed.


                                               Table I.1 – Test case template

                                               Interoperability test description

             Test purpose         A concise summary of the test reflecting its purpose and allowing readers to easily
                                  distinguish this test from any other test in the document.
             Reference            List of references to the base specification clause(s), use case(s), requirement(s), etc.,
                                  which are either used in the test or define the functionality being tested.
             Test           Step      Type                    Description                      Result
             sequences
                            1     Stimulus      A stimulus corresponds to an event that   There is no need to
                                                triggers a specific action on the object under   provide 'Result' for a
                                                test. There is no need to provide 'Result' for a   stimulus step.
                                                stimulus step.

                            2     Check         A check consists of observing that the object   A result must be
                                                under test behaves as described. A result must  provided for every
                                                be provided for every check step. If the object   check step.
                                                under test behaves as described in the
                                                description of the check step, the result
                                                should be recorded as OK, otherwise the
                                                result should be recorded as fail.
             Test verdict   It is deemed as successfully terminated if all/or one check(s) is (are)
                            successful, otherwise it is deemed as failed.

















            888
   891   892   893   894   895   896   897   898   899   900   901