[Dev] Re: TestMaker Accessories specification

[Frank Cohen]

Hi William: Good questions. See below. -Frank

On Feb 15, 2007, at 12:07 PM, William Martinez Pomares wrote:

> Hello Frank.
>
> We are reviewing the specs. I have a couple of questions:
> 1. For the XML Schemas drivers, should we understand as a driver  
> the set
> of libraries you mention (DPL,DVL and the context check)? Should it be
> like a factory, where I write base libraries and then simply add the
> specific classes that the factory will instantiate (STAR, CDISC)?

Yes. The DPL is straight forward from our past projects for GM, BEA,  
Sun, and others. The DVL is a validation check so the API should have  
a few methods to validate a document. The context check is a little  
more complex in that it needs to provide methods to create notes,  
walk through an XML document in the schema's context, and insert/ 
update/delete. This is kind of an XML specific version of JDOM, but  
much more focused, and consequently smaller.

>
> 2. In the databaset and applications drivers: The normal methods for
> databases are easy to define, but applications are not. Which would be
> the things to test on an application server? Could they be different
> from one app server to the other?

Let's try for the most common app functions first, then we will add  
more functions that are specific to the application. For instance, I  
think that all of the applications will have:

log-in
log-out
create record
delete record
update record
search for records
select one record

> 3. The Industry Specific Test Kits spec is not clear. It seems we  
> should
> not do anyting in here, since it only asks for the test kit to be
> possible using the drivers. Cuold you expand the idea?

The test kits are a combination of drivers, plus the business logic  
defined in a use case. For example, if I was going to test a CDISC- 
based system for tracking clinical trials then I would write a Jython  
script that creates a patient record, inserts notice of a visit to a  
clinic, updates the patient's phone numbers, and then exists the  
application. The script would be very light weight with calls to the  
CDISC driver to interact with the clinical trial db. You should break  
down the project into two phases: 1) drivers, and 2) creating the  
kits. The experience of doing 1 will let me define the spec for 2.

>
> 4. The project contains then the installer and management console for
> the drivers, right?


Yes. The installer and console are for TestMaker. It's assumed that  
the customer already has the applications, dbs, etc.

>
> 5. Since it seems quite a few number of drivers, could we talk of an
> ongoing project where the drivers are created on demand? That is, to
> create the few more requested ones to make a first delivery and be  
> able
> to put those available, and then start working on the others and so.
>

Yes, exactly! This is a formalization of the one-by-one process we've  
been using for GM, BEA, Tibco, etc.


> Thanks.
>
> William.
>
> -----Original Message-----
> From: Frank Cohen [mailto:frank at pushtotest.com]
> Sent: Wednesday, February 14, 2007 5:56 PM
> To: William Martinez Pomares
> Cc: Mario Chavez
> Subject: TestMaker Accessories specification
>
>
> Hi William:
>
> Attached is a specification for the TestMaker Accessories.
> Accessories are the drivers for XML schemas, applications, and
> databases. I'm sending this to you so you will be able to come up
> with a good and general design for the DPL in TM5.
>
> Please forward this to the Avantica management as a request for
> proposal.
>
> Thanks.
>
> -Frank
>
> --
> Frank Cohen, PushToTest, http://www.PushToTest.com, phone 408 374 7426
> TestMaker: The open-source SOA test automation tool
>
>
>



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