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

FESA3 Release on machine	DEV on asl73x	3.0.0 on vml00v	3.0.0 on asl733	3.1.0 on vml00v	3.1.0 on asl734
Issue
Unit Tests
Installation Issues
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 )
Editing of FESA classes' designs in design and source view
Display of FESA documentation according to selected element in FESA class design in Doc 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
Creation of base for HTML documentation (.xmldoc)
Creation of HTML documentation from base
Update of a FESA classes' FESA version (possible only if more than one FESA3 version exists)
Launch of migration script(s) during update from FESA version 2.x.2 to version 3.0.0 (3.0.0 to 3.1.0)
Creation of new FESA deploy-units
Inclusion of a local FESA class
Editing of FESA deploy-unit designs in design and source view
Display of FESA documentation according to selected element in FESA deploy-unit design in FESA Browser
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 (possible only if more than one FESA3 version exists)
Launch of migration script(s) during update from FESA version 2.x.2 to version 3.0.0 (3.0.0 to 3.1.0)
Launch of FESA deploy-units on development machine
Access running FESA deploy-unit via FESA Explorer
Validation of FESA instantiation documents
Editing / Extension of FESA instantiation documents in design, source and table view
Display of FESA documentation according to selected element in FESA instantiation document in doc view
Functionality of table editor for device instances (edit values, copy device-instances, edit multiple instances)
Update of a FESA instantiation document's FESA version (possible only if more than one FESA3 version exists)
Launch of migration script(s) during update from FESA version 2.x.2 to version 3.0.0 (3.0.0 to 3.1.0)
Launch of FESA Explorer
Creation of zip file containing instantiation document
Access of GSI-Standard-Property, e.g. Version via FESA Explorer
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
FFTCustomEvtSrc ( FFTCustomEvtSrc, FFTCustomEvtSrc_DU, testbed-testsuite) for 64-bit
fesa-core-test		-
fesa-core-gsi-test		-
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
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		-	-	-
WRTimingTest (WRTimingTest, WRTimingTestDU, !WRTimingTest-client) for 64-bit		-	(on scuxl)	-
FFTEventMapping ( FFTEventMapping, FFTEventMapping_DU, testbed-testsuite) for 64-bit				-
FFTEventSources ( FFTEventSources, FFTEventSources_DU, FFTOnSubscriptionSrc, !FFTOnSubscriptionSrc_DU, testbed-testsuite) for 64-bit				-
Availability of user/group fesa (groups; cat /etc/group <pipe> cut -d: -f1; usermod -G fesa <USER>)
Creation of log-file FesaPlugin.log in users home directory .logs
Installation of gsi-ctr-timing, cern-*, cern-cmw-*, fesa-*, availability for 64-bit
Installation of fesa-explorer
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)		-
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
CMW directory server environment variables in fesa3_environment.conf
Proper JAVA version (java -version)
Availability Eclipse Luna SR1 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
Availability of FESA3 cheat sheets
Creation of interface graphs (.png files in docs folder)
Multiple update of FESA projects (possible only if more than one FESA3 version exists)
Export of FESA class designs to database (requires expert option)
Automatic SVN integration of new FESA class projects
Creation of subsets
Usage of GSI's conditions (XML generation, DB update/insertion, throwing of condition without parameters in FESA class)		-	-
Creation of start script during source code generation, FEC / instantiation creation and delivery
Export of FESA deploy-unit designs to database (requires expert option)
Automatic SVN integration of new FESA deploy-unit projects
Access running FESA deploy-unit via C++ SimpleClient (RDA)
SVN repository check during delivery
Export of FESA instantiation documents to database
Update of FESA Explorer (reload zip)
Opening of shell at desired location (fec folder)
GSITemplateIntegrationTest class design
GSITemplateIntegrationTest class deployment-unit
GSITemplateIntegrationTest class instance-file			() See Bug 844 and FESA-6169
GSITemplate (GSITemplate, GSITemplateDU, !GSITemplate-test) for 64-bit
Launch of FESA deploy-units on remote location (binary: /common/export/fesa/local/<FEC>)				not testable without fully working delivery, fesa group required
Warning message if HTML documentation is not existing				not testable without fully working delivery, fesa group required
Copying of HTML documentation during delivery to https://www-acc.gsi.de/dav/fesa/classes		-	-	not testable without fully working delivery, fesa group required
Delivery to FEC location without mark as development		-	-	not testable without fully working delivery, fesa group required
Copying zip file to web access location during deploy-unit delivery (/common/usr/fesa/htdocs/fex)				not testable without fully working delivery, fesa group required
Delivery of FESA classes (relevant for remote accessability of inheritance/scheduling view)				not testable without group fesa
Delivery of FESA deploy-units including binary, instantiation files and start script (64-bit: CPU=x86_64)				not testable without group fesa