[INSTRM-718] Pre-shipping procedures for SM1 Created: 25/Jul/19 Updated: 22/Oct/19 Resolved: 22/Oct/19 |
|
| Status: | Done |
| Project: | Instrument control development |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Story | Priority: | Normal |
| Reporter: | hassan | Assignee: | fmadec |
| Resolution: | Done | Votes: | 0 |
| Labels: | SM1, SPS | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Story Points: | 2 |
| Sprint: | SM1-2019 L, SM1-2019 M, SM1-2019 N, SM1-2019 O, SM1-2019 P |
| Description |
|
Following today's ICS/DRP+SpS telecon: Fabrice will put together a set of procedures that should be followed to ensure that the SM1 software is acceptable before shipping. |
| Comments |
| Comment by fmadec [ 02/Aug/19 ] |
|
What was discussed was to identify what could be done daily, that might not be sufficient for the preship review. here is a first list of tests that could be done daily: Infrastructure
1. Tron hub 2. Alerts (STS) 3. Logging (ActorCore library). Can’t test in the absence of rsyslog. 4. File I/O (checking NFS mounting etc) /data and /software Hardware
|
| Comment by hassan [ 22/Oct/19 ] |
|
SM1 pre-ship software test campaign completed and draft report being circulated. |