[Dev] TM5 example scenarios

[Frank Cohen]

Good point. The scenarios are meant to be instructive, not actual. So  
they will use the services on examples.pushtotest.com and not a real  
bank. -Frank



On May 27, 2007, at 1:34 PM, William Martinez wrote:

> On Sun, 27 May 2007 08:40:09 -0700
> Hi.
> I'm not clear about the simulation of the banking portal using the  
> functions at PTT. On the other hand, using the TG4W script in a  
> real bank poses some problems, the first one being that TG4W  
> registers the passwords in the scripts, so don't use the real ones.
>
> William.
>   Frank Cohen <fcohen at pushtotest.com> wrote:
>> I asked Brady Morgan to build several example test scenarios. Here  
>> is  a summary of the examples:
>>> Hi Brady: Here's what I am thinking are the example scenarios we   
>>> will need for PushToTest TestMaker 5:
>>>
>>> 1) Testing a Web browser-based application using TestGen4Web
>>>
>>> Scenario: You need to do a functional test of a banking portal.  
>>> The  portal lets you look up information, transfer funds, and  
>>> view the  latest news.
>>>
>>> Brady, please use the functions at:
>>> http://examples.pushtotest.com/responder/htmlresponder
>>>
>>> and
>>>
>>> Please use the TestGen4Web plug-in to Firefox to record the  
>>> script,  and then use the Tools menu -> Transform to Jython  
>>> function to  create a Jython script.
>>>
>>> 2) Expanding the test to include a DPL
>>>
>>> Scenario: Add the ability to the Scenario 1 banking portal   
>>> functional test a means to transfer funds multiple times  
>>> according  to a comma-separated-value file that tells you which  
>>> account to use  and how much to transfer.
>>>
>>> Brady, this requires a Data Production Library (DPL) and  
>>> <arguments>. See these for examples:
>>> /tm5/TestMaker/example_agents/dplExample/testDPL.xml           
>>> Example
>>> /tm5/TestMaker/example_agents/dplExample/dplExamples.jar      One  
>>> DPL
>>> /tm5/TestMaker/example_agents/dplExample/dplSimple.jar         
>>> The  test
>>> class
>>>
>>> 3) Turn a functional test into a scalability test
>>>
>>> Scenario: The bank from Scenario 1 now wants to know how if the   
>>> portal can handle up to 30 concurrent virtual users.
>>>
>>> Brady, please reuse the Scenario 1 functional test as a  
>>> scalability  test. Please use the following CR levels: 10, 20,  
>>> 30, and no  message size levels.
>>>
>>> 4) Turn a functional test into a service monitor
>>>
>>> Scenario: The bank from Scenario 1 wants to know if the bank is   
>>> delivering service as agreed-to in their Service Level Agreement   
>>> (SLA.) The SLA requires the site to respond to requests in no  
>>> more  than 2 seconds.
>>>
>>> 5) Testing a SOAP-based Web Service application
>>>
>>> Scenario: A manufacturing organization uses a SOAP-based Web   
>>> service to order parts and needs to do a functional test of the   
>>> service.
>>>
>>> Brady, please use our examples service. A WSDL description of  
>>> the  example service is at:
>>> http://examples.pushtotest.com/axis/services/MessageService?wsdl
>>>
>>> Please use the soapUI function in TM5 to accomplish this  
>>> scenario.  See tm5/TestMaker/example_agents/soapUIexample
>>>
>>> 6) Multi-protocol test
>>>
>>> Scenario: The manufacturing company in Scenario 5 added a  
>>> browser  based interface and an email interface to their system.
>>>
>>> Brady, this test needs to show how multiple protocols (SOAP,  
>>> HTTP,  POP3) may be used in one test.
>>>
>>> 7) Implementing a test in multiple languages
>>>
>>> Scenario: A developer needs to write a functional test of the   
>>> Banking portal from Scenario 1 in the Ruby language.
>>>
>>> Brady, see tm5/TestMaker/example_agents/rubyExample
>>>
>>> For each of them I am looking for a) a summary of the scenario  
>>> in  1-2 paragraphs, b) the implemented scenario code, and c) a   
>>> "developer journal" explaining step-by-step what you did to   
>>> implement the code. The journal should be 1-3 pages max.
>>>
>>> Thank you for taking this on. You're literally TM5's first user.   
>>> Ask lots of questions, point out the problems you find, and make   
>>> suggestions on how to make TM5 easier. Thank you!
>>>
>>> -Frank
>>>
>>>
>> Feel free to add your own ideas to this list, and to point out   
>> problems, and corrections. Thanks.
>> -Frank
>> --
>> Frank Cohen, PushToTest, http://www.PushToTest.com, phone 408 374  
>> 7426
>> TestMaker: The open-source SOA governance and test automation tool
>> --
>> Frank Cohen, PushToTest, http://www.PushToTest.com, phone 408 374  
>> 7426
>> TestMaker: The open-source SOA test automation tool
>> _______________________________________________
>> Dev mailing list
>> Dev at lists.pushtotest.com
>> http://lists.pushtotest.com/mailman/listinfo/dev
>
> _______________________________________________
> Dev mailing list
> Dev at lists.pushtotest.com
> http://lists.pushtotest.com/mailman/listinfo/dev
>



--
Frank Cohen, PushToTest, http://www.PushToTest.com, phone 408 374 7426
TestMaker: The open-source SOA test automation tool