Garching, 08 July 2005 NRI (Night Reporting Infrastructure) for VLT Common Software Integration S. Feyrin, M. Zamparelli European Southern Observatory.

Slides:

Advertisements

Similar presentations

What is Test Director? Test Director is a test management tool

Advertisements

Automating Software Module Testing for FAA Certification Usha Santhanam The Boeing Company.

Configuration management

Software change management

Configuration management

DETAILED DESIGN, IMPLEMENTATIONA AND TESTING Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.

Automated Software Testing: Test Execution and Review Amritha Muralidharan (axm16u)

® IBM Software Group © 2010 IBM Corporation What’s New in Profiling & Code Coverage RAD V8 April 21, 2011 Kathy Chan

How to Optimize Your Existing Regression Testing Arthur Hicken May 2012.

Software. What Is Software? software –Also called Computer programs –Are a list of instructions –Instructions are called code –CPU performs the instructions.

Online Performance Auditing Using Hot Optimizations Without Getting Burned Jeremy Lau (UCSD, IBM) Matthew Arnold (IBM) Michael Hind (IBM) Brad Calder (UCSD)

03/09/2007CSCI 315 Operating Systems Design1 Memory Management Notice: The slides for this lecture have been largely based on those accompanying the textbook.

Testing an individual module

Systems Analysis and Design in a Changing World, 6th Edition

Copyright © 2006 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill Technology Education Copyright © 2006 by The McGraw-Hill Companies,

Automated Tests in NICOS Nightly Control System Alexander Undrus Brookhaven National Laboratory, Upton, NY Software testing is a difficult, time-consuming.

Chapter 13 Web Application Infrastructure. Objectives Explain the components and purpose of a web application platform Describe several common webapp.

ALMA SW Development Tools, Standards and Integration Procedures P. Sivera, M. Zamparelli European Southern Observatory Garching – ESO.

2007 Adobe Systems Incorporated. All Rights Reserved. 1 Joe Berkovitz VP Engineering Allurent, Inc. Continuous Integration with Flex, FlexUnit, and Ant.

10th TTCN-3 User Conference, 7-9 June 2011, Bled, Slovenia AUTOSAR Conformance Tests - Feedback on their development and utilization Alain Feudjio-Vouffo,

October 30, 2008 Extensible Workflow Management for Simmod ESUG32, Frankfurt, Oct 30, 2008 Alexander Scharnweber (DLR) October 30, 2008 Slide 1 > Extensible.

M. Taimoor Khan * Java Server Pages (JSP) is a server-side programming technology that enables the creation of dynamic,

© Janice Regan, CMPT 128, Jan CMPT 128 Introduction to Computing Science for Engineering Students Creating a program.

M. Zamparelli European Southern Observatory ACS Course Japan, July 2005 ALMA/ACS Software Engineering.

I. Pribela, M. Ivanović Neum, Content Automated assessment Testovid system Test generator Module generators Conclusion.

Framework for Automated Builds Natalia Ratnikova CHEP’03.

Project Source Code Structure and Build Process ● Remember consistency matters as source code structure, build process, and release processes are all intertwined.

Reporting and Build Statistics Using Business Intelligence By Naga Sowjanya Karumuri Build Team, VMware, Cambridge Summer Internship 2008.

© 2012 IBM Corporation Rational Insight | Back to Basis Series Chao Zhang Unit Testing.

M.Ellis 17th August MICE Software School Aims Course content –Management –Specifications –Design –Production –Testing –Use Information –Operation.

COMP-14: Automating your deployments using ANT Gary S Clink Business Consultant.

 To explain the importance of software configuration management (CM)  To describe key CM activities namely CM planning, change management, version management.

Software Engineering in Robotics Packaging and Deployment of Systems Henrik I. Christensen –

SDD/DFS L.K.Lundin VLT 2 nd Generation Instrumentation Pipelines, 19 Apr Pipeline Test methods Lars Kr. Lundin - CPL developer - NACO and VISIR.

Software Toolkits Building Communities Luis Ibáñez KITWARE, Inc.

Configuration Management (CM)

WebVizOr: A Fault Detection Visualization Tool for Web Applications Goal: Illustrate and evaluate the uses of WebVizOr, a new tool to aid web application.

CPRG 215 Introduction to Object-Oriented Programming with Java Module 1-Introduction to Java Topic 1.1 Basics of Java Produced by Harvey Peters, 2008 Copyright.

Copyright © 2007 Addison-Wesley. All rights reserved.1-1 Reasons for Studying Concepts of Programming Languages Increased ability to express ideas Improved.

Security - Why Bother? Your projects in this class are not likely to be used for some critical infrastructure or real-world sensitive data. Why should.

Slide 12.1 Chapter 12 Implementation. Slide 12.2 Learning outcomes Produce a plan to minimize the risks involved with the launch phase of an e-business.

TEST-1 6. Testing & Refactoring. TEST-2 How we create classes? We think about what a class must do We focus on its implementation We write fields We write.

An OBSM method for Real Time Embedded Systems Veronica Eyo Sharvari Joshi.

ASP (Active Server Pages) by Bülent & Resul. Presentation Outline Introduction What is an ASP file? How does ASP work? What can ASP do? Differences Between.

Confidential Continuous Integration Framework (CIF) 5/18/2004.

Software Development COMP220/COMP285 Seb Coope Introducing Ant These slides are mainly based on “Java Development with Ant” - E. Hatcher & S.Loughran.

CISC Machine Learning for Solving Systems Problems Presented by: Suman Chander B Dept of Computer & Information Sciences University of Delaware Automatic.

Application Software System Software.

 Programming - the process of creating computer programs.

Test and Verification Solutions128 October 2009 Test and Verification Solutions Improved time to market through automated software testing Mike Bartley,

Yannick Patois - Datagrid Software Repository Presentation - March, n° 1 Datagrid Software Repository Presentation CVS, packages and automatic.

EGEE is a project funded by the European Union under contract IST GLite Integration Infrastructure Integration Team JRA1.

SPI NIGHTLIES Alex Hodgkins. SPI nightlies  Build and test various software projects each night  Provide a nightlies summary page that displays all.

Dynamic Testing.

T EST T OOLS U NIT VI This unit contains the overview of the test tools. Also prerequisites for applying these tools, tools selection and implementation.

Color Palette To use or remove these color palettes, go to View/Master/Slide Master Optional logo for your notes/handouts slides APPLYING THESE COLORS.

SOFTWARE TESTING LECTURE 9. OBSERVATIONS ABOUT TESTING “ Testing is the process of executing a program with the intention of finding errors. ” – Myers.

Cofax Scalability Document Version Scaling Cofax in General The scalability of Cofax is directly related to the system software, hardware and network.

Comments on SPI. General remarks Essentially all goals set out in the RTAG report have been achieved. However, the roles defined (Section 9) have not.

Chapter 5: Coding Ronald J. Leach Copyright Ronald J. Leach, 1997, 2009, 2014,

1 March 12, Testing William Cohen NCSU CSC 591W March 12, 2008.

SOFTWARE TESTING TRAINING TOOLS SUPPORT FOR SOFTWARE TESTING Chapter 6 immaculateres 1.

Chapter 13 Web Application Infrastructure

CIS 375 Bruce R. Maxim UM-Dearborn

Agenda:- DevOps Tools Chef Jenkins Puppet Apache Ant Apache Maven Logstash Docker New Relic Gradle Git.

Current Generation Hypervisor Type 1 Type 2.

Types for Programs and Proofs

CS5123 Software Validation and Quality Assurance

Human Complexity of Software

Presentation transcript:

Garching, 08 July 2005 NRI (Night Reporting Infrastructure) for VLT Common Software Integration S. Feyrin, M. Zamparelli European Southern Observatory

Garching, 08 July 2005NRI for VLTSW2 Contents 1.NRI Generalities : NRI/dynamic: motivation and requirements NRI Layout 2.NRI for vltsw 3.Possible changes and extensions

Garching, 08 July 2005NRI for VLTSW3 NRI/dynamic: motivation 1.shorten the feedback loops from manual integration 2.bring to the attention of the developers software modules with missing or insufficient testing 3.bring to the attention of the developers software modules with suspect memory fingerprint 4.diminish the labor pain when migrating to new compiler version or OS release 5.have minimal trend analysis for various performance indicators

Garching, 08 July 2005NRI for VLTSW4 Requirements on NRI 1.Build environment should be the correct one 2.All applicable platforms should be exercised 3.Static and dynamic reports should correspond to the same version of the software 4.The build should take place from scratch 5.Tests should be executed in isolation (FIFO) 6.Ease of access to reports on the web for diagnosis 7.Tests running amock should not halt the integration

Garching, 08 July 2005NRI for VLTSW5 Configuration Management Static Inspection host 1 Database WebServer host 3 host 2 (dynamic inspection machines) Codewizard JTest sloccount cmt/cmtjava JDepend doxygen graphviz Purify/Valgrind splint JContract source reports NRI Layout

Garching, 08 July 2005NRI for VLTSW6 Machines HOSTPROJECTOSWHATTOOLS te64VLTSL3APPLIC.Purify SCI/OCI te53VLTSL4CSPurify OCI te26VLTHP-UX 11CSPurify OCI te44ALMARH9/rtaiAPPLIC. Purify SCI valgrind te31ALMARH9/rtaiCS Purify SCI valgrind te48ALMARH Ent. 4CSPurify SCI te58ALMASunOSCSPurify OCI te89ALMARH9/rtaiAPPLIC.Purify SCI

Garching, 08 July 2005NRI for VLTSW7 Integration Steps 1: normal build 2: normal test (TAT or otherwise based) 2,5: additional purify and test (if applicable) 3: purified build (vltMakefile based)vltMakefile 4: purified test (TAT or otherwise based)

Garching, 08 July 2005NRI for VLTSW8 PurifyPlus for Linux C/C++/JavaC/C++ SCIOCI Coverage Inspection Memory Inspection Good Bad Missing Available batch granularity

Garching, 08 July 2005NRI for VLTSW9 1.Dynamic ( build and test) Adapt NRI to work with non Makefile based approach of VLTSW Align results of automated integration and tests with the manual ones Solve problems related on LCU availability and usage Solve display related problems 2.Dynamic ( coverage and memory reports ) Run through PureCoverage and get consistent results!! Improve layout and readability of coverage reports Separate the weed from the crop in memory reports 3.Notification (responsibility assignment) 4.Static part

Garching, 08 July 2005NRI for VLTSW10 Links to the Web Reports/TestCoverage-Linuxhttp://websqa.hq.eso.org/vlt/snapshot3/vltsw- Reports/TestCoverage-Linux /

Garching, 08 July 2005NRI for VLTSW11 Purify CompiledTest DIR Makefile test target make test test output UNDETERMINED FAILEDPASSED UNDETERMINED TAT TAT signature Test result determination

Garching, 08 July 2005NRI for VLTSW12 Problems and Solutions (?) Execution time on HP-UX is prohibitive LAST or non LAST ? How frequently should it run ? Tools license availability ? pkingBuild should build a partition of the CMM modules space ( )

Garching, 08 July 2005NRI for VLTSW13 NRI: dynamic + static Implementation of Integration steps on a “daily” basis Daily build report on appropriate OS from last code revision Coding Standards (actually industry best practices) reports (VLTSW VLTSW )VLTSW VLTSW Naming conventions, dependency diagrams, subsystem partition in modules. McCabe Cyclomatic Complexity and Halstead Volume, in-line documentation sufficency in-line documentation Lines of code at subsystem and global level test lines of code at subsystem level Unit test coverage amount of check-in operations SPRs per subsystem

Garching, 08 July 2005NRI for VLTSW14 RESERVE SLIDES FOLLOW

Garching, 08 July 2005NRI for VLTSW15 Night Reporting Infrastructure Limitations: no check for C++ VxWorks LCU code yet (missing compiler for Linux) avoid false positives handling exceptions is difficult inspection is only possible for compilable (C++) or compiled (Java) code avoid collecting info on generated code, not always trivial Tcl/Tk missing and in general weak on scripting languages