Testing methods for migrating to Spire

[sxi123123123]

We operate an application with the following configuration. The application creates Excel/Word/PDF files.

OS: Windows Server 2016
Office: Office 2016

We are currently testing a migration from Office 2016 to Spire. Because the expectation is that the Excel/Word/PDF files produced after switching to Spire will not change, we are testing by producing the same files with the current (Office 2016) and the new (Spire) setups and verifying that the contents are identical.

During this process, we detected unexpected differences as described in the inquiry below.
https://www.e-iceblue.com/forum/issue-with-unstable-strikethrough-display-in-conditional-for-t13683.html
https://www.e-iceblue.com/forum/how-calculate-value-for-merged-cells-t13676.html
https://www.e-iceblue.com/forum/the-print-object-setting-is-not-enabled-t13646.html
https://www.e-iceblue.com/forum/smart-art-disappearing-in-pdf-conversion-with-spire-doc-t13531.html

We plan to extend the checks to other files as a horizontal rollout; however, there are about 10,000 target files.
We believe other users may also be migrating from Office products to Spire. If there are any case studies from other companies on how to guarantee identical behavior between the current and new solutions, could you share them? Alternatively, please tell us any verification points or best practices for ensuring consistent behavior.

Our application is a critical system that affects our customers’ operations, and behavioral differences are essentially unacceptable. In the current state, we may judge the potential defects to be too risky and abandon the Spire adoption, so we would appreciate your cooperation.

[talia.liu]

Hello,

Thank you for your inquiry.
Please note that Spire.Office and Microsoft Office are different products: Microsoft Office is a client-based end-user application, while Spire.Office is a developer-oriented middleware offering API services without dependency on Microsoft Office and aims to achieve the same effects as Microsoft Office through programming. Therefore, we have no case studies to offer. Regarding the issues you raised, we've fixed them and provided corresponding versions. For your scenario, we recommend that you do more testing and evaluation. If you encounter any issues during the evaluation phase, please feel free to contact us and we will provide timely assistance.