Re: test dir name (WAS: Re: [Phpwiki-talk] cvs access to dfrankow)

[Reini U. <ru...@x-...>]

Dan Frankowski wrote:
> I am blocked on this until we choose a name for 'testbox'.
> Comments?

let's just keep "testbox" then.

> Dan Frankowski wrote:
>> Reini Urban wrote:
>>> Dan Frankowski schrieb:
>>>
>>>> One of the changes is to add an error handler (instead of just an 
>>>> assert handler). This is useful because then if there is incorrect 
>>>> PHP syntax, vars missing, etc., the tests don't run. In other words, 
>>>> the tests get more picky, which is good. When they get more picky, 
>>>> they want an existing testbox with some stuff in it (InterWikiMap, 
>>>> global_data, a few other things). Thus, I want to make a "testbox" 
>>>> in CVS with the right stuff and check it in, as I did on our local 
>>>> copy.
>>>>
>>>> Since I do not wish to make changes that you don't want, please tell 
>>>> me that you approve. Then I'll go ahead and make the unit test 
>>>> changes, including adding a CVS-tracked "testbox" with stuff in it.
>>>
>>>
>>>
>>>
>>> approved.
>>
>>
>>
>>
>> Cool. I won't add it until we have a name you like (see below).
>>
>>> but the name "testbox" compared to out intermediate ".testbox"
>>> might not fully understandable. can you think of a better name?
>>
>>
>>
>>
>> I'm sorry, I didn't understand this.
>>
>> I picked "testbox" to mean a "test sandbox." I agree it is not a great 
>> name, but I'm having a hard time thinking of better ones. A list of 
>> possibilities:
>>
>> 1. testbox
>> 2. test_sandbox
>> 3. sandbox
>> 4. backend_dir
>> 5. backend_data
>> 6. testdb
>>
>> Any preferences? I'm not sure any are very good.
>>
>>> In a perl CPAN test framework the call it "t" (for the logic) and 
>>> "output" (for the output which should be tested against).
>>
>>
>>
>>
>> Neither "t" nor "output" is appropriate here. It's more like "input". 
>> I guess that's another possibility.
>>
>>> i'm not quite accustomed to the java unittest structure.
>>
>>
>>
>>
>> Java has no standard proposal for the input data upon which to base 
>> unit tests.
>>
>> Dan
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/