Status |
---|
subtle | true |
---|
colour | Blue |
---|
title | administrator |
---|
|
Due to the almost inexhaustible list of environmental variables and customer use cases, it isn't possible for Aegis to test every single function and feature without severely impacting the release cycle and subsequent delivery of FactoryLogix software to the customer base. This gap is a common occurrence among large enterprise software systems. We strongly encourage you to build a pre-upgrade test plan to help you validate the software in your usage scenarios on a test system before upgrading your production system with a new release of FactoryLogix.
While customer test plans are developed in-house, each plan should (at minimum) contain the following practices. These practices will be familiar to system "power users" who are instrumental in building and evolving customer-specific test plans.
Info |
---|
Important During testing, be sure to monitor the software for any significant impact on performance that cannot be directly associated with the system environment. |
Task | Description |
---|
Test the physical upgrade process to ensure all components are installed and running correctly. | - Are the services installed on the test system servers started?
Note The xLink service should be disabled on the test system and the adapters disabled once the database backup is restored. This prevents problems with two services trying to harvest from the same equipment. - Are the services installed on the test system servers started?
- If a database upgrade is required as part of the upgrade process, can you upgrade a recent backup of the production database successfully?
- Can you access licensed tools in use, for example NPI, Production, Analytics and Logistics client applications?
- Can you log into to each application with a system administrator and a normal user account?
- In NPI, can you access active projects including CAD, BOM, and visual aids?
- Can you also access Settings menus such as the user setup area, xLink, and xTend setup tools and view existing adapter setups?
- In the Production client application, can you access batches and search functions?
- Can you open and view operations correctly?
- Does the Trace area return the correct traceability data?
- In the Analytics client application, can you access existing templates and run reports?
- Are data sets returned without errors and can you view and edit dashboards?
|
Check the NPI client application for core functionality and check specific features to ensure they function properly. | - Can you access existing products and view the BOM, CAD, and visual aid instructions in the process?
- Can you edit an existing project, save changes, and sign it off for production?
- Can you create a new project from scratch, importing a CAD, BOM, and an existing process flow?
- Can you update the revision of an existing project and save the changes?
- Can you access, edit, and save a process flow, visual aids, and operator interface templates?
- Can you access Settings menus such as users, xLink and xTend and view current settings?
|
Check the Production client application for core functionality and check specific features to ensure they function properly. | - Can you access the batch search functions and confirm that impacted batches are returned?
- Can you open an existing batch and move products through the process?
- Can you create a new batch against an existing project and move a product through the process, including operations such as Initialization and Packout?
- Can you move a product through all steps in a standard process flow and confirm that all required activities can be completed?
- Can you create, repair, and close defects on several assemblies and view the defects at other operations carrying the defect gadget?
|
Check the Analytics client application to ensure you can run stored templates and report data sets and generate reports. | - Stored real-time dashboards should be available and you should be able to view and edit them. Check a test of loading a dashboard in the viewer by connecting the test system to the real-time service.
|
xTend integration services are designed to be backward compatible, meaning no structural changes should be made that would affect existing integrations. | - Test file-based integrations by running the integration service on the test system with a test route folder structure to drop the files into.
|
Disable xLink services during the initial setup of the test system. Test so that production issues are not caused by two xLinks harvesting data from the same system. | - Test file-based adapters the same way as the xTend services by duplicating the folder structure and manually dropping some test files into it.
Note You cannot validate real-time adapters on a test platform. |
...