ldtprunner_XML - Linux Desktop Testing Project

ldtprunner Tags

We have the following tags in ldtprunner XML

ldtp - The complete XML are tagged under this <ldtp> and </ldtp> tag
logfileoverwrite # - Value 0 (append to existing log file, if its already available) or 1 (Truncate the existing file, if its already available and write the data from 0)
logfile - File name, where the log file has to be written. Log files are generated in XML format. Its preferred to give absolute path for the log file
appmapfile # - Optinal application map file name. This option is available only for backward compatibility. We recommend you not to use this option
category # - A category can contain one or more group(s). All the group entries in a category will be executed in sequence. This feature was requested by Palm Source.
group - A group can contain one or more scripts. All the scripts in a group will be executed in sequence. The purpose of group is, if one of the script fails, then the whole group is skipped
testcaseid - One testcase id per group, if available will be logged as part of log file
comment - Comments about the script, will not be logged in the log file
script - Script contains one script file name and optional data file name
- testcase # - A meaningful name of the test case that is going to be executed
- name - Script file name
- data # - Data file name (Data file content will be in XML format - Data_XML)

Note: # marked are optional fields

Following are the list of recommendations when generating ldtprunner XML

Group set of related test-scripts into one category
In a group if the current executing script fails, then rest of the scripts in the current group will be skipped and ldtprunner will start executing the next group
Each individual scripts can take optional Data_XML file as an argument
Same script can be called multiple times with different Data_XML file
Scripts can be grouped in any sequence. Based on the sequence, scripts will be executed

Obsolete