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 4.x.x

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

* 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]

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

-- SolveighMatthies - 08 Jul 2016