How to prevent data logging into database?

[Rafi2003]

Hi,

I would like to prevent the automatic data logging from writing data into database upon certain conditions. An example will be an empty Serial Number field. My program exit with run-time-error but the data logging still logs...

I guess I could do it by messing around in the sequential model. But then, there is on-the-fly procedure and normal procedure which activating different sequences.

Is there a simple way to do it?

Thanks
Rafi

[Scott_Richardson]

Rafi -
There is no simple exported setting to do this. You will have to do this yourself using preconditions.

Note that with on-the-fly logging, if you have already executed some steps and then decide to not log, these step results cannot be removed from the database because the on-the-fly logging does not support transactions.

Scott Richardson (NI)

[Rafi2003]

Thanks Scott,

Is there any advantage to use on-the-fly over the logging at the end of the test?

I don't have any interest of watching data logging while the test is running...

Thanks
Rafi

[Scott_Richardson]

Rafi -
The only benefits of on-the-fly database logging are
1) If you are testing a UUT for a long time, the results are available while the test is running.
2) The result list can be discarded after being logged which can conserve memory.
3) If the UUT test crashes, your data in the database will not be lost.

The disadvantage is that on-the-fly is slower because you are calling a DLL after every step executes.

I recommend only using on-the-fly when necessary.

Scott Richardson (NI)