13 Testing Your Integrated Excel Workbook

This chapter describes features in the Oracle ADF Desktop Integration module that help you test your integrated Excel workbook as you configure it. It includes the following sections:

13.1 Introduction to Testing Your Integrated Excel Workbook

Testing an integrated Excel workbook before you publish it and deploy it to your end users enables you to verify that the functionality you configure behaves as you intend. Before you test your integrated Excel workbook, test the Fusion web application with which you integrate the Excel workbook. Once your Fusion web application functions as you intend, use the test mode provided by the Oracle ADF Desktop Integration mode to test the functionality in your integrated Excel workbook.

13.2 Testing Your Fusion Web Application

Test the Fusion web application that you integrate your Excel workbook with before you start testing the integrated Excel workbook. For information about testing a Fusion web application, see the Oracle Fusion Middleware Fusion Developer's Guide for Oracle Application Development Framework. Verify that the Fusion web application you want to integrate an Excel workbook with supports the Oracle ADF Desktop Integration module by carrying out the procedure described in Section C.1, "Verifying That Your Fusion Web Application Supports Desktop Integration".

If you make changes to the Fusion web application to resolve problems identified by testing the application, you need to:

  • Rebuild the JDeveloper project where you develop the Fusion web application

  • Rerun the Fusion web application

  • Reload the page definition files that you associate with the integrated Excel workbook

This makes sure the changes in the Fusion web application are available to the integrated Excel workbook. For information about how to reload a page definition file, see Section 4.3.3, "Reloading a Page Definition File in an Excel Workbook".

13.3 Testing Your Integrated Excel Workbook

As you configure your Excel workbook to integrate with a Fusion web application, you can switch to test mode from design mode to test the functionality that you add to the workbook. You use the Oracle ADF Desktop Integration Designer toolbar to switch to test mode from design mode and from design mode to test mode.

Test mode allows you to test the functionality of your integrated Excel workbook as you configure it incrementally. It also allows you to view the integrated Excel workbook from an end user's perspective, as test mode corresponds to what end users see when they view and execute the published integrated Excel workbook. The difference between an integrated Excel workbook in test mode and a published integrated Excel workbook is that the Oracle ADF Desktop Integration Designer is not available to users of the published integrated Excel workbook.

For more information about test mode and design mode, see Section 5.1, "Introduction to the Development Tools".

The Oracle ADF Desktop Integration module can generate log files that capture information based on events triggered by an integrated Excel workbook. For more information about these log files, see Appendix C, "Troubleshooting an Integrated Excel Workbook".

To run an integrated Excel workbook in test mode:

  • In the integrated Excel workbook that you want to test, click the Run button on the Oracle ADF Desktop Integration Designer toolbar.

    The integrated Excel workbook switches to test mode from design mode.

To stop test mode and return the integrated Excel workbook to design mode:

  • In the integrated Excel workbook that you are testing, click the Stop button on the Oracle ADF Desktop Integration Designer toolbar.

    The integrated Excel workbook switches to design mode from test mode.

Note:

When an end user tries to close the integrated Excel workbook, Microsoft Excel prompts a message to save the workbook even if the end user has not modified it after opening it. This is an expected behavior because the Oracle ADF Desktop Integration module modifies an integrated Excel workbook each time an end user opens it.