[Etester-devel] Re: eTester

[<dm...@cs...>]

Hi:

I have no objections to these points.

Cheers,

DM


Quoting Gunnar Gotshalks <gu...@cs...>:

> Hi All,
> 
> Bil pointed out the following and I have some comments as a result of 
> working with students in the Prism lab.
> 
> At 4:12 PM -0400 9/15/03, Vassilios Tzerpos wrote:
> >    1. The blurb on etester at the web page is outdated. Unfo, I 
> >don't have permission to change it. We should probably mention that 
> >etester 2.1.2 is the official 3311 version. I would personally 
> >favour putting the etester2.1.2.zip file as well as the etester-gui 
> >one on the course web page, but if you feel otherwise, no problem.
> 
> Yes I agree with standardizing eTester and will try to
> 
> 1 -- I am now totally against any changes in what students are to use 
> after ONE MONTH BEFORE CLASSES BEGIN.   I guess I will have to put in 
> emergency time yet again but no more.  Changes are at least as time 
> consuming as doing the original and many more errors result.  As I 
> said to Jonathan the other day, eTester is taking up the majority 
> part of my time with Eiffel and the course and I do not see that it 
> is such a significant topic to take up so much effort.   It is 
> confusing to me, students get confusing messages which lowers their 
> confidence in the quality and benefit of the course.
> 
> 2 -- I now do not think that having etester precompiled is a good 
> idea.  The Prism ace files are different from what they have at home 
> and are different from my examples.   We should strive that our use 
> of Eiffel, Estudio and eTester are as identical as possible on all 
> environments.   Aside from path names, the same ace file should be 
> usable. If Eiffel can handle relative path names, which I did not 
> know it could as examples from a few years ago did not have relative 
> paths, then we should set up the template for Eiffel projects where 
> the root class and etester have the same relative path on all systems.
> 
> 3 -- Students are now getting confusing messages.  On Prism, eTester 
> comes automatically with the precompile and they are shown that in 
> the report 1 get started files.  In my examples and on their PCs they 
> will have to have eTester as a separate cluster.   The latter are 
> described in the www page that Dave wrote, and are in my slides so I 
> can discuss it in class.
> 
> 4 -- The precompile has a different cluster structure than what 
> happens on their PCs.  It is different from what I see on the Mac and 
> on Prism if I include my own eTester; at least it did when I 
> installed and tested using eTester 2.1.2.
> 
> 5 -- I, not to mention the students, get confused when there are 
> differences between systems.  When I saw, what to me was a complex 
> collection of clusters  with about 6-8 clusters at the upper level, 
> at first I did not even understand that the students were running 
> report 1.  I thought they were running a different system that I did 
> not know about and did not understand.    All I have is base, root 
> cluster and eTester.  That is all students see in my in class demos.
> 
> 6 -- Now my discussion and slides have to present two different views 
> of the  world.  I vote that we get rid of the precompiled eTester and 
> have all systems look the same.
> 
> Cheers ... Gunnar
> 




----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.