FESA3 Tests

Issues to consider, test and check on a fresh FESA3 installation (local in the developer's workspace as well as on test machines as on the asl cluster). To be extended...

FESA3 7.x.x

FESA3 Release on machine	7.x.x installation on vmla005	7.x.x installation on asl744	5.0.2 installation on vmlb020
Availability Eclipse 2019-03 with CDT***
CompositionTest (Compose1, Compose2, ComposeDU, !Compose-client) for 64-bit
CustomEvtSourceTest (CustomEvtSource, CustomEvtSourceDU, !CustomEvtSource-test) for 64-bit
FFTEventMapping ( FFTEventMapping, FFTEventMapping_DU, testbed-testsuite) for 64-bit		simulated timing selectors problem
FFTEventSources ( FFTEventSources, FFTEventSources_DU, FFTOnSubscriptionSrc, !FFTOnSubscriptionSrc_DU, testbed-testsuite) for 64-bit		simulated timing selectors problem
GSITemplate (GSITemplate, GSITemplateDU, !GSITemplate-test) for 64-bit
GSITemplateIntegrationTest class deployment-unit
GSITemplateIntegrationTest class design
GSITemplateIntegrationTest class instance-file
RDADataTypes (RDADataTypes, RDADataTypesDU, !RDADataTypes-test) for 64-bit
SubsetTest (Subset, SubsetDU, !Subset-test) for 64-bit
WRTimingTest (WRTimingTest, WRTimingTestDU, !WRTimingTest-client) for 64-bit (three selectors: SEQ (sequence), BP (beam process), BPC (chain) Multiplexing)
Access of GSI-Standard-Property, e.g. Version via FESA Explorer	- requires access to Haralds installation
Access running FESA deploy-unit via FESA Explorer	-^
Access running FESA deploy-unit via C++ SimpleClient (RDA)
Add new instance by cloning an existing instance file (device-instances will be renamed by appending _new)
Automatic GIT integration of new FESA deploy-unit projects
Automatic creation of default deploy-unit along with new FESA class
Automatic GIT integration of new FESA class projects
Availability of FESA perspective with views FESA Workspace, Make Targets, Outline, Project Explorer and the Eclipse views Console and Problems
Availability of desired make targets (64-bit: CPU=x86_64, clean)
Availability of desired make targets (64-bit: CPU=x86_64, clean)
Availability of doxygen documentation on webdav server for fesa-core and fesa-core-gsi (visible via https://www-acc.gsi.de/data/documentation/fesa(-gsi)/doxygen/<version>/index.html )			-
Availability of FESA class / deploy-unit / instantiation documentation on webdav server (visible via e.g. https://www-acc.gsi.de/data/documentation/fesa-gsi/metamodel/<version>/design-doc.html)			-
Availability of FESA3 cheat sheets
Availability of user/group fesa (groups; cat /etc/group <pipe> cut -d: -f1; usermod -G fesa <USER>)
Availabilty of C++ code templates
Build complete chain (included classes and deploy-unit itself)
Build complete chain (included classes and deploy-unit itself)
Code compilation of FESA classes for 64-bit
Code compilation of FESA deploy-units for 64-bit
Code generation for FESA classes
Code generation for FESA deploy-units
Configuration Issues
Configuration of secure storage password
Copying of HTML documentation during delivery to https://www-acc.gsi.de/dav/fesa/classes/<classname>.html (visible from within asl cluster)
Copying zip file to web access location during deploy-unit delivery (/common/usr/fesa/htdocs/fex)
Creation and adaption of FESA instantiation documents
Creation of FECs (including automatic creation of instance documents)
Creation of HTML documentation from base
Creation of base for HTML documentation (.xmldoc)
Creation of interface graphs (.png files in docs folder)
Creation of log-file FesaPlugin.log in users home directory ~/.logs
Creation of new FESA classes with empty template
Creation of new FESA classes with GSI template
Creation of new FESA deploy-units
Creation of start script during source code generation, FEC / instantiation creation and delivery
Creation of subsets
Creation of zip file containing instantiation document
DB Export of relevant design and instantiation files
Delivery of FESA classes (relevant for remote accessability of scheduling view)
Delivery of FESA deploy-units including binary, instantiation files and start script (64-bit: CPU=x86_64)
Delivery of FESA deploy-units including binary, instantiation files and start script (64-bit: CPU=x86_64) for several FECs
Delivery to FEC location without mark as development (<DUname-d>)
Depending on launch option -rbac: usage of RBAC or not		Not Supported
Depending on timing domain in instance file: usage or WR timing or not
Display of FESA documentation according to selected element in FESA class design in Doc view	-*
Display of FESA documentation according to selected element in FESA deploy-unit design in FESA Browser	-*
Display of FESA documentation according to selected element in FESA instantiation document in doc view	-*
Display of warning message when HTML documentation is not existing
Eclipse Issues
Editing / Extension of FESA instantiation documents in design, source and table view
Editing of FESA classes' designs in design and source view
Editing of FESA deploy-unit designs in design and source view
Export of FESA class designs to database (requires expert option during delivery)
Export of FESA deploy-unit designs to database (requires expert option during delivery)
Export of FESA instantiation documents to database
fesa-codegen (python tests)			-
fesa-codegen-gsi (python tests)			-
fesa-core-gsi-test			-
fesa-core-test			-
FESA3 Eclipse Plug-In Issues
Folder permission set for group fesa in /common/usr/fesa/htdocs			not available
Folder permissions set for group fesa in /common/export/fesa			not available
Functionality of multi file table editor for device instances (edit values, copy device-instances, edit instances)
Functionality of table editor for device instances (edit values, copy device-instances, edit instances)
Inclusion of a local FESA class
Installation Issues
Installation of fesa-explorer
Installation of gsi-ctr-timing, cern-*, cern-cmw-*, fesa-*, availability for 64-bit
Installation possible via (local) update site
Integration Tests Core ( package: fesa-core-integration-test )
Integration Tests GSI ( package: fesa-core-gsi-integration-test )
Issue
Launch of FESA deploy-units on development machine
Launch of FESA deploy-units on FEC (e.g. SCU) manually
Launch of FESA deploy-units on FEC (e.g. SCU) with daemon
Launch of FESA deploy-units on remote location (binary: /common/export/fesa/local/<FEC>-d)
Launch of FESA Explorer	- requires access to Haralds installation
Launch of deploy-unit in /common/export/fesa/local/<vmla005/asl744>/<deploy-unit name>/
Launch of migration script(s) during update from FESA version 5.0.1 to version X.x.x
Launch of migration script(s) during update from FESA version 5.0.1 to version X.x.x
Launch of migration script(s) during update from FESA version 5.0.2 to version X.x.x
Migration from previous version to current version ( package: fesa-core-gsi-integration-test )
Multiple update of FESA projects
Opening of shell/terminal window at desired location (=!FEC folder)
Operating System Issues
Parallel compile using at least make option -j4
Parallel compile using at least Make option -j4
Possibility to configure FESA preferences
Possibility to configure access to GSI's GIT repository
Promotion of updated FESA class configuration to instantiation document
Proper JAVA version (java -version)			, Java11
Repository check during delivery
Run of post installation script to install the configuration files (*.cfg, *.conf in /common/usr/export/fesa/global/etc/fesa/<VERSION>/)
Successful validation of new FESA class design using GSI template
Switching release environment
Synchronizing sources, build of software independent of expert preferences
Tests for FESA instantiation documents
Tests for FESA3 classes
Tests for FESA3 deploy-units
Tests for operational FESA classes/deploy-units
Unit Tests
Update of FESA Explorer (reload zip)	- requires access to Haralds installation
Update of a FESA classes' FESA version
Update of a FESA deploy-unit's FESA version including automatic update of instantiation document version
Update of a FESA instantiation document's FESA version
Usage of GSI's conditions (XML generation, DB update/insertion, throwing of condition without parameters in FESA class)
Validation of FESA class designs
Validation of FESA deploy-unit documents
Validation of FESA instantiation documents
Validation of subsets of a class

* Bug: No more handles [Browser style SWT.MOZILLA and Java system property org.eclipse.swt.browser.DefaultType=mozilla are not supported with GTK 3 as XULRunner is not ported for GTK 3 yet]
org.eclipse.swt.SWTError: No more handles [Browser style SWT.MOZILLA and Java system property org.eclipse.swt.browser.DefaultType=mozilla are not supported with GTK 3 as XULRunner is not ported for GTK 3 yet]

* FESA Eclipse Plug-In not fully working yet (20.08.2019, FESA Console output still missing)

^ Feature: Fesa Explorer FEX is installed by HaraldBraeuning in /common/usr/lobi/htdocs/applications/fesa-explorer/