[Lazarus] Testing process for new LCL widgetsets?

[Mehmet Erol Sanliturk]

Graeme Geldenhuys wrote:
> Hi,
> 
> If I want to start implementing the LCL-fpGUI widgetset, is there a test
> process or automated or manual list of tests I could follow to see where
> there are still issues? Maybe a set of test projects testing all
> properties of each component somewhere?
> 
> If not, how do you guys know what works and what doesn't between all the
> various LCL-xxx widgetsets? Plus how consistent applications behave
> between widgetsets (thinking in line of order of events being fired etc.)?
> 
> Regards,
>   - Graeme -
> 



One of the testing facility may be ability of script processing .
Assume a program has been developed , and it is necessary to test it 
exhaustively .

By clicking every possible point in the input interface is nearly very 
difficult and time consuming . Instead of doing that , incorporating a 
script application facility may help very much .

Sometimes key-press macro applicability may be sufficient , but 
personally I do not like key-press macros because they are cryptic ( to 
understand what they are doing , to modify them is difficult ) .

Scripts may be prepared in such a way that they exercises every part of 
the program in any combination sequence .

Main logic will be as follows : Script processing part will scan a 
script file and apply statements written in them by using processing 
parts of the program . If script can be completed successfully it may be 
said that the program is working correctly on this script . When the 
scripts are a representative sample of user applications and they are 
completed successfully , the same will be possible for the users also .


To my knowledge there is no such a scripting facility in Lazarus 
Components incorporated into Lazarus IDE . As an example fpmake may be 
used as a part .

(1)
A script starts by generating a new project , designs some forms , saves 
them , compiles them .

(2)
The compiled program starts a script and tries to complete it .


It may be said that a debugger is doing the similar tasks . In all of my 
life I used a debugger only first and then last time at least 25 years 
ago ( means I can not say anything about that ) .


Thank you very much .

Mehmet Erol Sanliturk