[Editor: This article was contributed by Prasanti Madireddi, Sr. Director, EBS Quality Assurance]
We introduced Oracle E-Business Suite Extensions for Oracle Endeca in 2013. These EBS Extensions provide selected EBS applications with Oracle Endeca-based capabilities. What is the best approach for testing your Endeca-based content for the E-Business Suite?
Overall testing strategy
The primary goal is to test Endeca's integration with the EBS application. Customers should be able to use EBS products alongside the Endeca search features to search and summarize EBS data.
Testing access to Endeca Applications
You must complete Endeca's role based access control (RBAC) before testing Endeca applications. You must create users, responsibilities and roles after the Endeca installation. After the RBAC setup is run, users can open Endeca pages and search for EBS data.
Testing Endeca integration with EBS products
Open Endeca pages from EBS. Verify the navigation from Endeca pages to self service pages and other windows, and also check the navigation back to the Endeca pages. Verify if the context is being set appropriately while navigating from one page to another.
Test key flows
Test all key flows in the Endeca products that you've integrated with the E-Business Suite. For example, if you've installed the Endeca extensions for iProcurement, the key flow in Oracle iProcurement would be to search for items in the Endeca page, compare the items, select some items and add them to cart and create a requisition.
Test data synchronization
Endeca maintains its own operational data store. This database needs to be synchronized with the E-Business Suite database. Data synchronization is key to the functioning of Endeca pages. Run the full data synchronization for your installed Endeca extensions and verify that the data is loaded appropriately. Open Endeca pages to verify that the synchronized data is accurate and is displayed properly.
Some of the products control the data to be loaded through a profile option wherein a cut-off date can be specified. The full load process pulls in data entered after the cut-off date specified.
For example: in the Project Procurement - Supplier & Item Analysis dashboard, you can use the profile "PO: Item and Supplier Analysis Data-load Cut-off" to restrict the data that is sent to Endeca.
Test your full load processes to verify that the data is synchronized based on product-specific profiles.
You can run the Incremental Synchronization tools to keep the Endeca database updated after new changes have been made to the EBS database. Test this by creating, updating, or deleting data from EBS and then running the incremental graph to verify that the changes are reflected in Endeca pages.
Test all search components and capabilities
Endeca provides several options for filtering and searching data.
Use these search features to verify that your data is filtered appropriately. Choose a small well-defined set of data for testing.
After you enter the search criteria, check that all Endeca components are refreshed appropriately with the queried data. This includes metric bars, result tables, record details and charts.
Most components have additional search capabilities, e.g. clicking on a value in a chart will further filter the data based on the clicked value. Check that those additional search features also show the latest synchronized data.
Endeca provides additional features: Metrics, Compare, and Export. The Metrics component provides a summary of the selected data. This component can be configured to highlight the data in different colors based on some specific conditions. Test Metrics to verify the accuracy and the format of the summarized data.
The Compare feature is used to compare two objects, for example, to compare two items before adding them to a cart in iProcurement. Test the Compare feature to verify that the selected objects are compared appropriately.
Test the Export option to verify that the displayed data can be exported and saved in Excel spreadsheets.
Test your RBAC setup by verifying that only authorized users can access Endeca pages.
Test your RBAC setup by verifying that only authorized users can see the data that they're authorized to access in Endeca. For example, if a user is allowed to see data from Organization A but not Organization B, verify that the appropriate Endeca pages also honor this data security check.
Descriptive Flex fields
Descriptive Flex fields (DFF) provide customizable expansion space on the EBS Endeca user interfaces and are used to track additional information. Endeca allows users to search on DFF attributes.
Test DFFs by creating new DFF definitions and then running the full load process to populate the DFF details. Search for the DFF values in the guided navigation.
Browser and mobile device compatibility
Test Endeca pages in the certified browsers that you've deployed in your organization.
Endeca pages should open in desktop clients, tablets, and mobile devices. Some components behave differently when opened in mobile devices. For example, the Guided Navigator is not rendered automatically in tablets and mobile devices; users open the Guided Navigator by clicking a button.