[fpc-devel] Re: FPCunit improvement ideas
brandys at o2.pl
Wed Jan 9 12:18:07 CET 2008
Graeme Geldenhuys wrote:
> More ideas....
> Other things that could be saved for Text Test Runner is the preferred
> output format (plain, xml, latex), show progress, stylesheet (if xml)
> and output file name.
> - Graeme -
> On 09/01/2008, Graeme Geldenhuys <graemeg.lists at gmail.com> wrote:
>> When using FPCunit with the GUI Test Runner (DUnit does this) you can
>> select a set of tests tests to run. You don't always have to run all
>> In the FPCUnit Text Test Runner it is always assumed that you want to
>> run *all* tests. This is not always desired - tests should normally
>> run quickly, but it isn't always the case.
>> My proposal is to implement a feature so that selected tests can be
>> run under both Text and GUI test runners - and that selection saved
>> for the next run. For example, select tests are stored in a INI file.
>> On consecutive runs, the INI file is read and only the enabled tests
>> are executed. If the INI file doesn't exist, all tests are run.
>> Any thoughts on this? Maybe somebody got a better solution?
>> - Graeme -
By the way : there is a little problem with fpcunit GUI runner with a
lot of tests - after Run or Run all tests treeview is fully expanded
which makes hard to find a particular test I'd like to run after.
An popup menu to fold all treeview items to the point where each test
class is visible but without detailed tests is highly needed.
More information about the fpc-devel