Lightning talk about ShiftlogTool(SLT) IRM meeting on Kyoko Nakamura

contents Objective of the ShiftlogTool Framework, architecture, database schema and deployment Core functionalities How to test List of regression tests

Objective of the ShiftlogTool  Recording all day and night observing activities Detailed list of all science observations Information about the environmental conditions Logs of technical operations on antennas and correlators  Generating a series of reports for any time interval or Projects or …  As a communication tool: OSF operators: to coordinate with colleagues over different shifts OSF staffs: to communicate with the ARC staffs ARC staffs: to report to the end users

Framework, architecture, database schema and deployment (1) Framework: Java application, and DB handlings are done by Hibernate and Spring The UIs are: Swing is for SLT GUI and ZK for WebSLT Architecture: SLT GUI / WebSLT Services DAO DB

Framework, architecture, database schema and deployment (2) Database schema: “alma” schema SLT own tables: shiftlog_entries, shiftlog_reply, slt_entry_attr, slt_entry_attach Deployment (for WebSLT): CAS server for authentication Tomcat for the application (webshiftlog.war)

Core functionalities A. Recording and updating (SLT GUI) Observing information and activities of the observatory Entries: ANTEN,AOG,ARRAY,CMDLN,DOWN,ENGIN,ENTRY,MMEX,SBEX,SHIFT,WEATH B. Searching (SLT GUI/WebSLT) C. Reporting (SLT GUI/WebSLT) Generic reports, Shift reports [PDF/HTML] Downtime statistics report [PDF/HTML/CSV] End of Night report [PDF/HTML/Twiki] Daily report Weather report [PDF/HTML] Project report [1] [2] [3]

How to test (1) 1) Migrate the DB if required 2) Deploy the build 2b) Deploy the webshiftlog.war to $CATALINA_HOME/webapps and start the tomcat 3) Run OMC and bring subsystems to operational 4) Launch shiftlog by almaproc in a command line or from the OMC plugin 4b) Login by a valid user for WebSLT 5) Do actions according to the test steps

How to test (2) In case an unexpected behavior happens, do the following actions * Double-check the test steps * Verify it can be reproduced or not and confirming the action * Check environments * Look into OBOPS log and catalina.out for WebSLT * Go back to the previous release and check the behavior * Look into the DB tables and modify it if needed * Verify with Aqua, protrack, etc. if needed …and so on

List of regression tests Throughout feature tickets in the past except obsolete ones regresson test with ICT Jira (43 tickets) regresson test with COMP Jira (40 tickets)