[kepler-dev] Actor testing question
Matt Jones
jones at nceas.ucsb.edu
Tue Apr 4 14:13:29 PDT 2006
I agree with Tim. There may be actors in a test workflow that are
performing a supporting role and aren't in fact tested. I think that
only the actors whose output is directly verified should be listed in
the coverage list.
Matt
Timothy McPhillips wrote:
> Hi Dan,
>
> We could write such a script. My understanding, though, was that
> actor tests would be designed specifically to test one or a small
> number of particular actors, and that each actor would have at least
> one test that verified its behavior. The list would declare which
> actors are under test in this sense.
>
> The list would also make it easier for others to verify that the test
> does indeed test the declared actors effectively.
>
> What do you think?
>
> Tim
>
> On Apr 4, 2006, at 1:24 PM, Dan Higgins wrote:
>
>
>>Tim,
>> You are correct. The nightly build does NOT yet handle the list
>>of tested actors following each test.
>>
>> (Just a thought: Do we really need this? Could we not write a
>>script that pulls a list of actors from the workflow itself?)
>>
>>Dan
>>
>>Timothy McPhillips wrote:
>>
>>
>>>Hi Ilkay (and other actor test writers),
>>>
>>>There are updated instructions for writing actor tests in lib/
>>>actor_test_instructions.txt, and a new file for listing actors
>>>that cannot be effectively tested according to these instructions
>>>(but nevertheless should be included in the release) in lib/
>>>untestable_actors.txt.
>>>
>>>Both files reflect the updates to the actor testing procedure
>>>agreed upon during the March 22 conference call.
>>>
>>>I don't believe the nightly build script yet handles a list of
>>>tested actors following each test specified in test-
>>>workflows.lst. (Is this correct, Dan?) However, this is not a
>>>reason to avoid contributing tests at this time.
>>>
>>>Please let me know if you have any questions or run into
>>>difficulties.
>>>
>>>Cheers,
>>>
>>>Tim
>>>
>>>
>>>On Apr 3, 2006, at 12:16 PM, Ilkay Altintas wrote:
>>>
>>>
>>>
>>>>Hi Tim and others involved in actor testing,
>>>>
>>>>Are there any updates on actor testing that we need to do before
>>>>the release?
>>>>
>>>>Thanks,
>>>>-ilkay
>>>>
>>>>_______________________________________________
>>>>Kepler-dev mailing list
>>>>Kepler-dev at ecoinformatics.org
>>>>http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/
>>>>kepler-dev
>>>>
>>>
>>>_______________________________________________
>>>Kepler-dev mailing list
>>>Kepler-dev at ecoinformatics.org
>>>http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/
>>>kepler-dev
>>>
>>
>>
>>--
>>*******************************************************************
>>Dan Higgins higgins at nceas.ucsb.edu
>>http://www.nceas.ucsb.edu/ Ph: 805-893-5127
>>National Center for Ecological Analysis and Synthesis (NCEAS)
>>Marine Science Building - Room 3405
>>Santa Barbara, CA 93195
>>*******************************************************************
>>
>>
>
>
> _______________________________________________
> Kepler-dev mailing list
> Kepler-dev at ecoinformatics.org
> http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/kepler-dev
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Matt Jones Ph: 907-789-0496
jones at nceas.ucsb.edu SIP #: 1-747-626-7082
National Center for Ecological Analysis and Synthesis (NCEAS)
UC Santa Barbara http://www.nceas.ucsb.edu/ecoinformatics
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
More information about the Kepler-dev
mailing list