Such unit tests could verify the reports rendering, using a ReportProcessor
instance. This class allows to render a report
in a specified format and returns a RenderingResult
instance which can be checked for errors and also contains the bytes of the output file, if the rendering is successful. We actually use exactly this approach in our own unit tests to make sure the reports are consistently rendered.
Hope this helps.
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Feedback Portal
and vote to affect the priority of the items