Justin McCarty NASA IV&V Program Justin.McCarty@tmctechnologies

Please download to get full document.

View again

of 21
5 views
All materials on our website are shared by users. If you have any questions about copyright issues, please report us to resolve them. We are always happy to assist you.

Download

Document Related
Document Description
NMotion A Continuous Integration System for NASA Software http://www.nasa.gov/centers/ivv/JSTAR/ITC.html. Justin McCarty NASA IV&V Program Justin.McCarty@tmctechnologies.com. NASA IV&V Facility 100 University Drive Fairmont, WV 26554. Agenda. ITC Background Motivation Implementation
Document Share
Document Transcript
NMotionA Continuous Integration System for NASA Softwarehttp://www.nasa.gov/centers/ivv/JSTAR/ITC.htmlJustin McCartyNASA IV&V ProgramJustin.McCarty@tmctechnologies.comNASA IV&V Facility 100 University DriveFairmont, WV 26554AgendaITC BackgroundMotivationImplementationChallengesGoing ForwardConclusionITC BackgroundIndependent Test Capability (ITC)NASA IV&V Independent Test Capability
  • ITC Develops System Simulators
  • Experts in Hardware Modeling and Distributed Simulation
  • Experts in Simulator & Software Integration
  • NOS Architecture
  • Reusable Hardware Models
  • Custom Middleware
  • System Test Automation
  • Typical NOS Users
  • V&V Engineers
  • Project Developers
  • Operators and Testers
  • Mission Support
  • Past Support
  • Juno
  • Automated Flight Safety System (AFSS)
  • Global Precipitation Measurement (GPM)
  • Current Support
  • Deep Space Climate Observatory (DSCOVR)
  • James Webb Space Telescope (JWST)
  • MotivationMotivations
  • Simulation Verification
  • Developers can focus on Development
  • System tests can take a long time
  • Test processes are repetitive
  • Tests are executed more often
  • Better Testing means Better Software
  • Significant overlap between projects
  • Testers can focus on tests
  • Test Complexity ExampleNASA IV&V Independent Test Capability
  • SSRM Test Script
  • Verifies all testable requirements
  • Very complex, over 8000 lines
  • 282 Commands
  • Over 36 unique commands
  • 106 number of suspends
  • 382 waits (without loops)
  • 10902 seconds of wait (over 3 hours!)
  • Test log shows test requires over 8 hours of human testing time
  • As developed, the test builds upon itself
  • Difficult to split and run in parallel
  • ImplementationImplementation
  • JWST Integrated Simulation and Test (JIST) used as the prototype
  • Developed with Java and C/C++
  • Automated unit level tests for developed components
  • Three Phase Test Processing
  • System Adaptation
  • Test Execution
  • Result Analysis
  • Cloud Based Deployment
  • No end user code required
  • Basic LayoutUser Test FileTest LogsOperational Ground SystemNOS MiddlewareAutomated Test ConductorCommand ProcessorInstruction Set SimulatorCommand ProcessorCommand ProcessorConductor I/O ControlProcessor LogicAPI 1API 2API 3Data FlowUserTest ConductorCommand ProcessorTest to RunStart CommandsSetup/Start CommandsApplication StatusApplication LogsTest ResultsTest LogsSystem Adaptation
  • Preprocessing of existing test scripts
  • Remove Automation Deterrents (Automated)
  • User acknowledgement
  • Convert Raw Commands
  • Ensure all required files are found
  • Ensure results can be processed
  • Ensure all components can be interacted with remotely
  • Start/Stop of process
  • Command injection if required
  • Execution and ProcessingTest scripts run are the same as system developers and operatorsThe system is reset in between each testTest conductor ensures applications are brought up in any required orderUsers provide a list of test cases to execute to the conductorApplication health is monitoredTest logs are collected from all applicationsTest logs are parsed for any failuresChallengesChallenges
  • Culture
  • Tests must be developed with automation in mind
  • Developers and testers are primarily only concerned with their environment
  • Lack of reuse between missions
  • Project Infrastructure and tools are not always developed with automation or remote interaction in mind
  • Going ForwardGoing ForwardIntegrate the autonomous system test execution into our continuous build serverAllow users to inject faults to test off nominal scenariosCode refinementIntegration into other simulationsSupport the scripting of environment setupIntegrate earlier into the development processConclusions
  • Enables higher level of automated testing (System)
  • Provides more testing (tests are more often)
  • Plan expand the system to other simulations
  • Plugin Based Operation
  • Who Benefits
  • Testers
  • Simulation Developers
  • Project Developers
  • If tools and tests are developed with automation in mind, new project adaptations become faster.
  • Contact InformationNASA IV&V Independent Test Capability
  • Web Page
  • http://www.nasa.gov/centers/ivv/jstar/JSTAR.html
  • E-Mail
  • Justin.R.Morris@nasa.gov
  • Team Mailing List: ivv-itc@lists.nasa.gov
  • Search Related
    We Need Your Support
    Thank you for visiting our website and your interest in our free products and services. We are nonprofit website to share and download documents. To the running of this website, we need your help to support us.

    Thanks to everyone for your continued support.

    No, Thanks