← KReport/Autotests You do not have permission to edit this page, for the following reason: The action you have requested is limited to users in one of the groups: Users, Administrators, trusted, KDEDevelopers. You can view and copy the source of this page. We use the ''autotests'' term because these are not always just unit tests but also functional. ==Location== *All stored in SRC/autotests/ (subdirs). *Data for given group of tests stored in a data subdir. ==The .kreport format== Code stored in SRC/autotests/format. Data in SRC/autotests/format/data. Types of tests identified: #Inserts some elements onto the report sections, save to the .kreport design format, then the markup is compared with the sample #Opposite direction: load .kreport designs, verify if report elements and their properties are as expected #Roundtrip: load the .kreport designs, save back immediately, compare with the original Special: *Collect .kreport samples for test cases for legacy elements/formats, use above tests with them **Example: the field element ==Writers== For KReportWriter implementations. #Load a sample, load some data, write using a KReportWriter, verify the result ==Scripting== Kexi 2.x Reports offered some limited scripting. The task is to collect all supported cases for that in a form of .kreport samples. Testing can be identical to the ''Writers'' autotests explained above. Return to KReport/Autotests. Retrieved from "https://community.kde.org/KReport/Autotests"