[Chandler-dev] Script-recording/playback as test framework
Grant Baillie
grant at osafoundation.org
Tue Dec 26 18:04:50 PST 2006
On 26 Dec, 2006, at 18:01, John Anderson wrote:
>>> So there shouldn't be any api learning for people writing tests,
>>> because writing tests shouldn't require any code writing. The
>>> script recorder will output a test a file with a "run" method
>>> that contains everything needed to run the test.
>>
>> How are you supposed to verify the data without writing code? And
>> you said '"run" method' -- what class is that method defined on?
>> If you're spitting out a script anyway, it's just as easy to stick
>> in the class definition and "def runTest(self)".
>
> We can compare the state of the UI and data to their values when
> the script is recorded.
Have you tried this? It seems to me that there are enough cases where
the state of the UI depends on the current date/time that this would
be difficult.
> Currently run is a function, not a method on a class, however it
> doesn't matter too much how we invoke the scripts.
True.
--Grant
More information about the chandler-dev
mailing list