This document describes test coverage provided by the Domino System Verification Test (SVT) team for the 8.5 release of Lotus Notes/Domino®. This document is specific to the Interoperability test coverage.
Interoperability is used to describe the capability of different products to coexist in an environment with the ability to exchange data. In order to be successful, the products must not adversely affect each other. SVT installs and operates various products in a full system environment including networks and coexisting software solutions, and operates the software with configurations that emulate likely customer usage of the product.
SVT Interoperability evaluates the system in the following 5 assessment areas
- Requirements Compliance
- Verify the overall system's compliance to specified operational and functional requirements in customer representative topology's
- Installation and configuration assessment - including vertically and horizontally scaled environments
- Verify that new functionality introduced into the system does not affect existing functions
- H/W & S/W Interactions
- Demonstrate that the entire enterprise infrastructure supports the stated Nonfunctional Attributes. Nonfunctional Attributes include supported OS platforms, client platforms, Third Party products, etc.
- Verify that the system is resilient to errors on the system and recover as designed.
- SVT uses the tools, procedures, and diagnostic capabilities shipped with the product(s) to debug and service the problems uncovered during SVT.
The SVT team worked with members of Quality Engineering, Development, Support, and Product/Project Management teams to identify feature/product areas to be tested by SVT. The Interoperability team identified 5 configurations to be tested in 3 phases.
The 5 configurations provided coverage for client and server platforms, browsers, Directory, and Security. Products tested include IBM® WebSphere® Portal 6.x, Lotus® Sametime® 8.0.1, Domino 8.5 server, Lotus Traveler Server, Notes 8.5 client (Basic and Standard configurations), IBM® Tivoli® Access Manager 6.0 (TAM), Netegrity SiteMinder 6.0 (SM), Lotus® Domino® Web Access 8.5 (iNotes), Microsoft® Internet Explorer 6.0, Internet Explorer 7.0, and Mozilla Firefox 2.0 and Safari 3.0
TAM 6.0 / AIX 6.1
TAM 6.0, remote Domino HTTP server (win2003), remote DB2 server (win2003), Activities servers (win2003 and RHEL4)
For additional information, please refer to the topic "Test Infrastructure: Domino 8.5 and Tivoli Access Manager (WebSEAL) Integration"
Domino 8.5 cluster, Portal cluster, ST cluster (external MUX's), LDAP cluster, DB2 cluster
For additional information, please refer to the topic "Test Infrastructure: High Availability Domino 8.5 server configuration "
Solaris SSL Proxy with IPV6
Edge 6.1 Proxy server, Domino 8.5 cluster, SSL enabled
For additional information, please refer to the topic "Test Infrastructure: Solaris, SSL, Reverse proxy with the use of IPV6 Domino 8.5 configuration"
Domino Directory 8.5
Domino 8.5 cluster, Portal cluster, ST cluster
For additional information, please refer to the topic "Test Infrastructure: Series i Domino 8.5 server configuration"
Windows 2003/SM 6.0
Active Directory 2003
remote IBM HTTP server (win2003), remote DB2 server (win2003)
For additional information, please refer to the topic "Test Infrastructure: Domino eTrust Netegrity SiteMinder Integration "
Use cases for each of the functional areas listed were executed against the test configurations identified in the table above.
Database - Domino/DB2
Feeds (RSS and Atom)
Mail (included different templates, mail threads, mail recall )
Calendar and scheduling ( included rooms&resources, out of office service)
SMTP, IMAP, POP3
Other – Mail Rules
Proxy Server (reverse, forward)
Portlets (iNotes, ST, CPP, NotesView)
Sametime Integration (IM and Web Conferences)
Single Sign On (SSO) - Basic, TAM, Siteminder
SSL (HTTPS, LDAPS)
System Verification identified and drove to resolution numerous defects throughout the testing cycles.
Issues that remain outstanding are being evaluated or are in plan to be resolved in future releases.