0.43
Released May 20., 2008Logging
The functionality of the log window was improved significantly by indenting the log messages according to the scope level of the step.
The log window also provides links to the steps, procedures and test suites used in the log messages.
Reporting
The reporting aspect of SeqZap has been improved significantly in the 0.43 release. We have added a template engine to SeqZap which makes it possible for users to design their own reports, or modify an existing report shipped with SeqZap.
Reports can be disabled/enabled by using the Configuration->Reports menu item. The disabled/enabled state of individual reports are saved in your .usersettings next to the .SeqZapProject.
Reports are opened inside SeqZap now, this provides a more consistent report usage, where the you do not have to "hunt" for the generated report.
The new reports should also make it much easier to pin-point the exact location where a test cases fails or reports an error state - this is done by inspecting the failure trace, reported for each test case.
Tool report progress
It is now possible for steps to show a progress bar to give the user a sense of how far along the current operation is.
New time steps
The Delay.Sleep ZapTool has been deprecated in favour of a general Delay step, this step allows the user to skip/break the delay without terminating the execution.
Another new step type that was added in release 0.43 is the time gate step, a step to ensure that the execution of a list of steps adheres to certain time restriction.
Above this paragraph is an example of time gate usage, this example ensures that the login procedures for a given service takes a maximum of 1 seconds.
Various
Bug fixes
| #127 | Right click->Delete in file editor does only deletes the first step, not all selected steps. |
|---|---|
| #130 | Pasting a step in the bottom of a procedure which already has steps in it, will insert the step at the top of the procedure. |
| #135 | Report parsing error when a procedure call's parameters does not match the procedure's actual parameters. |
| #149 | Clicking "Cancel" in add parameter to procedure dialog adds the parameter anyway. |
| #162 | Failure to instantiate a tool should set be marked as an error. |
| #172 | The "Record Results" button in the progress overview now records the results immediately. |
| #175 | Using multiline strings in expressions does not work. |
Deprecated API elements
The ICallContextSimple interface has been renamed to ICallContext, and the old ICallContext interface has been removed.
The Stream instance methods now takes an ICallContext parameter as the first parameter to all the methods, this is done to support that the stream instances can report their progress, vis-a-vie the new feature.

