1 / 29

Space Network Access System (SNAS) Test Readiness Review

Space Network Access System (SNAS) Test Readiness Review. August 12, 2010 NASA Code 452 Space Network (SN) Project. Purpose of Review. The objectives of the review d emonstrate readiness to support SNAS Release 4 acceptance testing at WSC. Readiness criteria

midori
Download Presentation

Space Network Access System (SNAS) Test Readiness Review

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Space Network Access System (SNAS) Test Readiness Review August 12, 2010 NASA Code 452 Space Network (SN) Project

  2. Purpose of Review • The objectives of the review demonstrate readiness to support SNAS Release 4 acceptance testing at WSC. • Readiness criteria • All applicable functional, unit, subsystem testing, etc. has been successfully completed. • Test objectives clear, system and environment configured and all test documentation complete • All RFAs / issues from previous reviews have been satisfied according to plan. • All known significant system discrepancies have been identified and dispositioned • Interfaces under configuration management or as specified in test plan • Testers identified, trained and ready

  3. TRR Agenda • Summary of Release 4 Dave Warren • Contents • System Level Testing Dave Warren • Acceptance Test Plan Mike Miller • SNAS Next Steps Rose Pajerski

  4. Summary of Release 4 Contents Dave Warren

  5. Release 4 Contents • 17 Wishlist enhancements • JSC (5), HST (2), WSC O&M (6), NOMs (4) • 22 Operational Discrepancies • JSC (10), HST (2), WSC O&M (8), NOMs (2) • 4 IDRs changes carried from Release 3 • JSC (1), HST (1), WSC O&M (2) • 64 Bugs from various users

  6. Release 4 Content Details (1 of 10) • 17 Wishlist enhancements • W/L 21: Filter TUT report for mission defaults of TDRS(s) and services. • W/L 35: Change PRINT characteristics • W/L 49: Display of all services for SAR on the SAR panel w/o scrolling • W/L 64: User control over transmission of TSW’s • W/L 66: Switch User Identification • W/L 67: Change Password Feedback • W/L 69: OAM Client: "MOC Client Activity Log" Window: improvements • W/L 70: More details needed for return-receipt related messages • W/L 75: Transmission Status of TSW to NCC/ANCC • W/L 81: Automated Option for Re-create USMs Function • W/L 82: TUT filter for the graphical timeline • W/L 84: Implement the "all-SICs" user setting. • W/L 85: Ingest TSWs without transmitting them • W/L 87: Adjust usage and display of request & event start/stop time • *W/L 62: SvE reset from O&M Client • *W/L 72: Add TDRS SN Payload Status to SNAS • *W/L 77: Receive EPS style reports on TCP/IP interface • * Planned for Candidate 2

  7. Release 4 Content Details (2 of 10) • 22 Operational Discrepancy fixes • *DR 55689: OAM client application level keep-alive • DR 58091: Errors While Running SNAS Purge Data • DR 58107: JSC Scheduling Connection problem • DR 58129: Directory warning for TCP/IP node • DR 58130: TCP/IP Node stopped receiving SRMs when sFTP node • DR 58131: Events marked complete prior to execution time • DR 58133: Shift Change Does not always take effect • DR 58233: Unable to Approve or Reject MOC SSC Modification • DR 58711: TSW Generation Problem (AR #097044) • DR 58712: SNAS would not complete TSW process (AR #094678) • DR 58722: Slow SNAS response during THEMIS support (10.1-patch 2) • DR 58822: Incorrect Antenna Numbers in confirmed Events listing • DR 58829: Difficulty logging in to SNAS • DR 58850: Incorrect Antenna Gain Values in confirmed Event Details • DR 59159: CNOFS socket inactive • DR 59104: SNAS O&M Client Dialog Box Not Dismissed • DR 59195: Output Connectivity inactive alert when client not logged in * Planned for Candidate 2  

  8. Release 4 Content Details (3 of 10) • Operational DRs to verify and close administratively (due to NCC distribution, duplicate Request ID, client.prop setup anomalies) • DR 58108: Invalid DEL status on Active Events Summary • DR 58132: Bulk modify time slip processes events incompletely • DR 58676: SRMs error off due to request ID's that are already in the system • DR 58686: SNAS UPD Status timeouts • DR 58760: Scheduling Anomaly - SARs Completed" before "Granted" (AR097135) • 4 Interim Discrepancy Fixes (from Release 3) • IDR 27378: O&M Ingest TSWs without transmitting them • IDR 27396: IP GUI doesn't show all IPs • IDR 27503: SRMs not going to TCP • IDR 27609: The Graphic Timeline needs to also show AltSARs

  9. Release 4 Content Details (4 of 10) • 64 Bugs • 143 Change PRINT Characteristics • 458 Replacing Client IP • 475 More details needed for return-receipt related messages • 508 Graphical Timeline-Rejected Event prevents access to lower events • 603 Concurrent Modification Exceptions in Client Summary displays • 607 PurgeDatabases utility needs to be built/installed • *686 EPS style reports on TCP/IP interface • *716 Several Issues with Reports (Confirmed Event Listing) • 733 Overlapping TDRS events scheduled on different TDRS • 734 Unsuccessful User Interface Channel Request • 736 Inconsistent Sched. Data display for 2 users/same Supiden • 744 Automated Option for Re-create USMs Function * Planned for Candidate 2

  10. Release 4 Content Details (5 of 10) • Bugs (cont’d) • 748 Mis-counting in Submission Progress Window • 753 EPS Interface will not accept both TCWs and TSWs. • 755 Filter TUT report for mission defaults of TDRS(s) and services. • 756 SDIF null pointer exception in infinite loop • 763 Events incorrectly marked Completed (or NCCQueued) • 764 Archived Alert Logs Missing Data • 767 SAM’s “Forced Logoff” of MOC/OAM Client • 770 Orbital Parameters can't be saved unless S/C Characteristic data has been entered • 771 MOC and OAM Clients display DAS SSCs differently when values are missing from database • 772 DAS Playback Search always shows bogus error dialog because of cleanup code • 774 User-defined TDRS Constraint Panel delete failures

  11. Release 4 Content Details (6 of 10) • Bugs (cont’d) • 775 Unreadable characters in active schedule upload file • 776 Both SAR Panels have trouble with blank in Nominal Duration/Stop • 778 Memory leak in MOC Client—dataStore in DataManager • 780 pop-up notification during EPS processing are confusing • 781 PSAT and UAV files can't be imported simultaneously • 782 Limitation on Setting Re-Specifiable Parameters in SSCs • 784 TutRetrievalProcessor no longer handles on-the-fly changes to HourlyTutActivated property • 787 Comm Type column in EPS Setup GUI should be removed • 788 OPS SvE properties file has an EIF reference • 789 Order of tracking services are changed in SARs generated by Recurrent Scheduling

  12. Release 4 Content Details (7 of 10) • Bugs (cont’d) • 790 Missing USMs & SRMs in EPS Node Export Folder • 791 Timestamps in report file names have different frames of reference • 792 Inconsistent Implementation of Time Stamp in File Names • 793 Client reconnect fails due to “not active” timeout with crazy value • 794 Commanded option to re-create USMs • 796 Built-from-scratch database is incomplete • 797 Minor changes to Delete User Account Panel • 798 Some Native Data doesn't get sent to EPS FTP if EPS TCP handled it • 799 SystemEventNotification not always sent for SUPIDEN changes • 801 Replace Requests should not be allowed against Waitlisted SARs

  13. Release 4 Content Details (8 of 10) • Bugs (cont’d) • 802 List of classes in DataManager are not synchronized properly • 804 NullPointerException in Timeline Panel when there are no USMs • 806 ASAR menu option doesn't do anything on Timeline Panel • 807 Erroneous window for Invalid Nominal Duration • 808 Discrepancy between Full Details and the Detail Pane on Graphic Timeline • 810 File size validation needed for TCW files • 812 SDIF broadcast alerts are excluded from logon alert list, even if DAS SICs are selected (in IDR 27269) • 813 Typo in message description in EPS FTP Setup page • 815 Empty String not allowed for minimum duration for Prototype Events • 816 Define Prototype Event Panel doesn't show aliases for SSCs

  14. Release 4 Content Details (9 of 10) • Bugs (cont’d) • 817 Modifying a TSW Set ID name creates a new object but does not delete the old one • 818 EPS TCP/IP does not update data structures properly when users disconnect from ports • 819 Editing Prototype Events in OAM Client kills DSDM-to-SVE writer thread • 820 OAM Client PurgeProcessor doesn't handle Active Event Purge properly • 821 If Add User fails once, subsequent attempts also fail • 822 Results for two different reports are mixed up together in one file. • 823 ASARs are not plotted in graphical timeline • 824 OAM Client Define Prototype Event panel allows adding DAS SSC to a PE • 827 Referenced Request ID Selection Panel "Print Full Details" doesn't print data

  15. Release 4 Content Details (10 of 10) • Bugs (cont’d) • 828 Use of Bulk Modify to Update Stored Only Requests • 829 Status on TSW Summary does not update after TSWs are transmitted • 830 Remove SNIF code that was supposed to change RR to SAR when granted

  16. Release 4 System Level Testing Dave Warren

  17. System Testing • Started June 10th with 1st build of integrated developer changes • Incorporated updates every few weeks as developers completed items, pulling new code from CM tool and rebuilding application • Developed test cases to test each ER, DR, and Bug • 11 test cases specific to MOC Client, O&M Client, and server processes • 5 test cases for external interface and regression testing • Beta Testing on I&T servers • 10.2.candidate.0 built on 7/06 • Initial checkouts by HST and GPM • Only two issues were noted and fixed (TSW and Bulk Modify) • 10.2.candidate.1 built on 8/03 • All but six items included (W/L 62, W/L 72, W/L 77, DR 55689, Bug 716, Bug 686) • Beta evaluation started 8/4 • 10.2.candidate.2 to be built upon final four completions

  18. Release 4 Acceptance Testing Plan Mike Miller

  19. AT Plan- Overview • Initial Test Baseline – 10.2 Candidate 1 • Six open items to be delivered in a Candidate 2 • Isolated functions with minimal regression testing of Candidate 1 • Test Documentation - NENS- CCE-ATP-0321 Four test groups: • Group 1 (SNAS MOC) • G1.1. SNAS-MOC-TUT • G1.2. SNAS-MOC-TSW-RS • G1.3. SNAS-MOC-SCHED-GEN • G1.4. SNAS-MOC-PROC • G1.5. SNAS-MOC-SCHED-CONFLICTS • G1.6. SNAS-MOC-SCHED-DAS • G1.7. SNAS-MOC-SCHED-SUMMARY • G1.8. SNAS-MOC-SYSTEM • G1.9. SNAS-MOC-EPS (* JSC Test support- TCP/IP functions)

  20. Test Plan • Group 2 (O&M Client) • G2.1. SNAS-OAM-PROC • Group 3 (client-Server) • G3.1. SNAS-SYS-CONNECTIONS • Group 4 (System)–Regression and Performance/Loading tests • G4.1. SNAS-DAS-VECTOR • G4.2. SNAS-DAS-OPERATIONS • G4.3 SNAS-DAS-PLAYBACK • G4.4 SNAS-ETE-OPERATIONS • G4.5 SNAS-PERFORM-LOADING

  21. Test Reporting • AT Discrepancy Reporting • SN Comprehensive Discrepancy System (CDS) • Internal Discrepancy Report (IDR) Database • Test Status Meetings • Weekly tag-ups – planned for Weds. 11pm MDT (1pm EDT) • Review discrepancies found in Acceptance Testing and determine plan for resolution • Review discrepancies found in concurrent Beta testing (Customer evaluation) • Coordinate Candidate 2 delivery to OPS EIF – 4 remaining items added • No other patches delivered unless required to continue AT or determine as minimal impact to testing (I.e., minimal Candidate regression testing, invalidate previous test results)

  22. Test Environment • SNAS Servers – EIF String for AT • Connections to ANCC and DAS HMD • Software Release 4 (10.2.candidate.1) • SNAS Database configured - populated with test SICs, mission configurations, and SSCs (same SICs as in Release 3 AT)

  23. Test Environment • ANCC configuration – shared SN resource • No interactive UPD updates however, able to validate SNAS UPD functionality • DAS HMD – shared SN resource • Connections to WSC servers and/or SNAS Beta servers will be coordinated with DAS HMD personnel, WSC testers, and SNAS system administrators • Client Platforms –platforms available to AT testers • MOC Client on test platforms- both from Open and Closed • O&M Client on test platforms • WSC TO&A Testing – not able to test TCP/IP functions • JSC Testers to test and verify TCP/IP fixes and enhancements

  24. Configuration Control • Changes controlled using CM tool • Concurrent Versioning System (CVS) setup on development server/Beta Server • Eclipse IDE environment established on developer workstations connected to CVS • Code checked into CVS after successfully compiled/linked and unit tested by developers and then system tested on Beta servers • Version can be tagged at specific Build milestones • Build scripts were developed and executed on development server and then Beta Servers to create new server processes and client executables • Clients are copied to remote computers and tested

  25. Test Resources/Schedule • Resources • WSC TO&A and JSC • AT Testers have begun Release 4 Beta (10.2.candidate.1) evaluation • Test Schedule • Release 4 AT duration is planned for 6 calendar weeks Target date to deliver Release 4 – 10.2 to Operations is between Oct. 15 and Oct. 18 . This has been coordinated with JSC/STS Mission Support. (WSC to issue a NAM – warning of impending new Client download required – plan for an NET October 15 SNAS delivery).

  26. Risks Risk #1: If Candidate 2 is delivered to WSC Servers/EIF for Acceptance Testing late in the testing period, then there may not be sufficient time to complete regression testing of Candidate 1. Rating: Likelihood = 2 (low), code partially implemented in Candidate 1 Consequence = 2 (low), code is isolated and would require minimal regression testing Mitigation: Deliver Candidate 2 no later than 2 weeks into test period.

  27. Follow-up Rose Pajerski 27

  28. Next Steps Release 4 Acceptance testing: 8/16 – 9/24 (6 weeks) Operational phase in: NET 10/18/10 (10/18 - 11/12/10) Delivery Readiness Review: 9/29 Release 5 Sustaining Engineering New and remaining Wishlist enhancements Operational Discrepancies Delivery cycle Critical operational problems analyzed and delivered as patches Full Release delivery for 4thQtr 2011 28

  29. In Closing Summary of review action items identified SNAS team will write RFAs w/ originator’s approval Other action-pending items Approval to begin AT? 29

More Related