19. Test, release and fix bugs

Test, release and fix bugs

A reliable report not only consists of the normal case, but also long texts, empty values, large amounts of data, other languages, several pages and different output channels.

Open Report designer on the desktop Administration.

Your goal

You can carry out a complete test plan, isolate typical errors and transfer a report template into productive use in a controlled manner.

Why this is crucial in the report designer

The final quality level determines trust. A properly tested report appears natural; a single incorrect total or truncated note calls the entire system into question.

Elements and settings at a glance

• Test matrix: List of data set, scenario, expectation, result and reviewer.
• Normal case: Typical, complete data set.
• Borderline case: Very long texts, many positions, high/negative/zero values, empty optional fields.
• Language case: Any productively used report localization.
• Output case: Preview, PDF, print and other productive export formats.
• Release status: Documented status from template, date, inspector and intended use.
• Fallback level: Exported, proven working predecessor template.

Here's how to do it

1. Save and export the version to be checked under a unique version name.
2. Run the test matrix with known setpoints.
3. First assign errors to a level: Data, Filter, Band, Expression, Format, Layout, or Output.
4. Correct only one cause at a time and repeat the affected and an adjacent test case.
5. Have the department and those responsible approved; Only then assign the template productively and keep the fallback level.

Exercise

Test your practice report with at least eight cases: normal, one record, no details, many details, long text, null/negative, second language, and PDF/print. Document expectations and results.

Check the result

• All mandatory information is available and technically correct.
• Totals match known X-ERP values.
• Authorized recipients will not see any additional confidential data.
• All languages and output channels pass the test.
• The original and released versions can be restored.

Typical errors and their solutions

• Empty value: Check field binding, filters, data members and parameter context.
• Double detail line: Control relationship, detail report and grouping.
• Additional blank page: Check overall width, margins, invisible elements and page break.
• Total wrong: Check expression, summary function and running area.
• Change gone after restart: Check active tab, report name and successful save.

Your result

Your own report template is not only designed, but also resilient: professionally tested, technically comprehensible and safe to use in X-ERP.

Further information / source

Related topics

1. For customizers – customize screens and forms › Report designer › 01. Getting started and secure workflow
2. For customizers – customize screens and forms › Report designer › 03. Open, copy and save report templates
3. For customizers – customize screens and forms › Report designer › 18. Preview, print and export

Frequently asked questions