[skoll] GME

[Arvind S. Krishna]

Hi Don,

> > Looks like the test cases for the above three would be totally 
> > orthogonal to each other. You may want to pick and decide based on what
> > the ESHCER is supposed to be housing. The problem gets complicated since
> > GME AFAWK is not scriptable.  Just our $0.02.
> 
> Okay, and how does that effect the use of Skoll?
> 
> We provide a framework, the development team provides the tests.  If we
> need/want to test interoperability between disparate tools, we'll have to
> add tests.  I don't see this as any different from anything else.
> 
> But perhaps I've misunderstood.  Why do you think Skoll wouldn't be a good 
> tool to use to automate the GME nightly builds (that currently don't 
> exist)?
>

What we were discussing is the following: Will illustrate this with a 
scenario: 

When we wanted to integrate our tools with ESML we moved from GME 3 to GME 
4.1 to our surprise we could not even open our meta-model that had some 
libraries built with GME 3.0. How come the release version missed 
backward compatibility, you would ask this should have been spotted? The 
ANSWER:

GME is *NOT* scriptable i.e. we need a tester to manually do this for us 
unless the GME developers provide us hooks. I am really ignorant in this 
regard, but can GUITAR help? 

I understand what you are suggesting i.e have nightly build that will 
build GME to spot compile errors etc when GME developers commit stuff. But 
again, at this stage, I don't know if we can test *features* in a 
scriptable format. 

Thanks,

Arvind
 
> take care...
> don
> 
> > 
> > Thanks
> > Bala
> > 
> > > Here's a link to GME.  If you could download it and take a look, that
> > > would be great.  Also, we have access to the CVS repository on ESCHER
> > > (thought I may need to add you to the group).  Anyway, there are several 
> > > projects that need to be built, not just GME itself, but there are not 
> > > compile-time options to set, just a release and a debug target.
> > > 
> > > http://www.isis.vanderbilt.edu/Projects/gme/
> > > 
> > > It's VC6, so a windows skoll environment that uses VC6 and can invoke a 
> > > suite of projects as a group would be great.
> > > 
> > > As for testing, they don't really have any, but if we could come up with 
> > > an easy way for them to integrate them, we could test GME under 3 
> > > scenerios:
> > > 
> > > 1) the various GUI's
> > > 2) the COM APIs
> > > 3) interactions between the tools, a la, tool chains (a very important 
> > > concept in ESCHER)
> > > 
> > > thanks...
> > > don
> > > 
> > > _______________________________________________
> > > skoll mailing list
> > > skoll at list.isis.vanderbilt.edu
> > > http://list.isis.vanderbilt.edu/mailman/listinfo/skoll
> > > 
> > 
> 
> _______________________________________________
> skoll mailing list
> skoll at list.isis.vanderbilt.edu
> http://list.isis.vanderbilt.edu/mailman/listinfo/skoll
>