Please enable JavaScript.
Coggle requires JavaScript to display documents.
OpenText v16 connector (Functional testing (Metadata Support (Check…
OpenText v16 connector
Functional testing
-
-
Crawling content
Ability to browse and process
the content with minimal rights (consult with DEV):
- non-admin-Read access (if process without DLS)
- non-admin-Full control (if process with DLS) :warning:
Containers/subcontainers
-
Transport warehouse
- Transport Packages
- Warehouse folders
-
-
-
-
-
-
Task lists, task groups, tasks
-
-
-
-
-
-
Metadata Support
After metadata for processing are defined and there are some custom metadata, which are not in Fields.config, so, prepare Metadata description file (inside connector), in order to add it by connector during processing, or add this metadata to Userfields.config/Fields.config :check:
Check correctness of processed metadata from
different Livelink objects - all that you have in
Livelink shall be processed according to mapping
All meaningful metadata is processed
-
-
Document Source, Document Type :check:
Using of metadata pre-filters for search, wildcard search if needed :check:
All meaningful metadata shall be processed
Further, BA and PO will decide which of metadata should be displayed in client. :check:
-
Using of facets created based on new metadata, search in facets if needed :check:
Handling Updates
if the body of the document is changed, the Document+Metadata shall be re-sent for processing :check:
if only metaDATA is changed for document, only Metadata shall be re-sent for processing :check:
if DLS for documents is changed, only metadata shall be re-sent for processing :check:
-
DLS Support
-
Inherited permissions (grant access for folders, users):
Child items' permissions are inherited
from Parent permissions :check:
As I explored in OpenText,
we have only ability to Grant access (positive scenario),
No ability to restrict some item for special user (to do it, we shall exclude such user from Granted Access for this item) :check:
Create meaningful content with
all special objects, metadata, DLS :check:
Performance testing
Throughput of the connector (how many documents processed and how much time spent during indexing of whole content)
-
-
-
Load testing
Process folders with more than N files,
where N > Opentext threshold limit setting.
-
-
-
-
-
ART
All basic functionality must be covered by ART tests (all tests determined as Acceptance tests)
Consult with manual QA about main use cases, that shall be covered
-
PROBLEMS
Risk of DLS testing: I have explored how to add permissions to Groups/users in Opentext. Also in OpenText I can create and add some user to group, ex. load_user1 (do it manually, no mathcing with AD users) . So, I hope OpenText user "load_user1" will be matched with our GFW user "Load_user1". :checkered_flag:
Verification of OpenText auth through Trusted Identity Providers (ADFS, SiteMinder, PingFederate) - need Dev help (after short consultation with Dev, it is unclear moment and seems, connector won't be workable in this case)
Some basic content will be created manually, but it is not enough for Load testing. Need developer's help to create some script for big data loading
Separate US shall be created :checkered_flag:
General moments
If some questionable moments appear, we shall compare the behavior with old connector.
-
-
Security
Security: pay attention on transferring sensitive information (passwords) between Connector and Goldfire server