RoutineBot – GUI Test Automation Robot

GUI Test Automation – How-To Tips! Download How-To Tips Now!

While conducting GUI Automation Load Tests is a must in order to identify any unexpected UI bugs and crashes under varying loads, keeping track of such issues is far from easy. The inherent nature of load tests (high traffic and quick execution speed) makes it a daunting task to capture GUI bugs. Therefore, it’s recommended to log all UI failures (Error Windows, Warning Pop-ups, Crash Dialogs, Exceptions stack traces, Windows fatal error dialogues) to an external log file. Further, it’s a good practice to log the loading time to identify any potential performance or UI resource crunch issues.

The external log file must be used for reconciliation while replaying the recording of your application’s automated GUI test cases.

admin Uncategorized

As RoutineBot uses FastScript as script engine, there are 2 restrictions:

1.  If you use units in you project, you must use quoted names in uses-decalartion.

E.g.  in PascalScript these syntax is invalid:

uses unit1;

instead use syntax

uses 'unit1';
2. Unit structure must be same as default script. E.g. in pure Pascal structure of unit is
Unit unitname;
interface
function, procedures,constant and other declarations
implementation
realization of function and procedures declared in interface section
end.

In PascalScript you must use these syntax for units
function unitfunction1 : integer;
begin
realization of unitfunction1
end;
function unitfunction2 : string;
begin
realization of unitfunction2
end;
procedure unitprocedure3;
begin
realization of unitprocedure3
end;
begin
initialization io unit
end.

Here you can download example unit.

Developer Uncategorized