Unit Test Process Authors:Sergey Fedorov, Dmitry Balkin, Dmitry Korenkov June 2005.

Slides:



Advertisements
Similar presentations
Testing Relational Database
Advertisements

Configuration Management
Project Analysis Course ( ) Final Project Report Overview.
Configuration Management
Ch-11 Project Execution and Termination. System Testing This involves two different phases with two different outputs First phase is system test planning.
System Integration Verification and Validation
XML/EDI Overview West Chester Electronic Commerce Resource Center (ECRC)
Tutorial 8: Developing an Excel Application
1 Software Engineering Lecture 11 Software Testing.
Alternate Software Development Methodologies
Requirements Engineering n Elicit requirements from customer  Information and control needs, product function and behavior, overall product performance,
1 Software Requirement Analysis Deployment Package for the Basic Profile Version 0.1, January 11th 2008.
Chapter 14 Requirements and Specifications. Copyright © 2005 Pearson Addison-Wesley. All rights reserved Software Engineering The implementation.
Copyright © 2006 Software Quality Research Laboratory DANSE Software Quality Assurance Tom Swain Software Quality Research Laboratory University of Tennessee.
Lecture 13 Revision IMS Systems Analysis and Design.
System Development Life Cycle (SDLC)
Software engineering Olli Alm Lecture 2: requirements, modelling & representation.
Process, Communication, and Certification Padma Venkata
 QUALITY ASSURANCE:  QA is defined as a procedure or set of procedures intended to ensure that a product or service under development (before work is.
Quality Manual for Interoperability Testing Morten Bruun-Rasmussen Presented by Jos Devlies, Eurorec.
S R S S ystem R equirements S pecification Specifying the Specifications.
Software Documentation Written By: Ian Sommerville Presentation By: Stephen Lopez-Couto.
Project Execution & Termination Life Cycle Execution Presented by: Basker George.
Software Configuration Management
Release & Deployment ITIL Version 3
Chapter 6– Artifacts of the process
What is Business Analysis Planning & Monitoring?
S/W Project Management
CaDSR Software Development Update Denise Warzel Semantic Infrastructure Operations Team Presented to caDSR Content team November 2012.
Database testing Prepared by Saurabh sinha. Database testing mainly focus on: Data integrity test Data integrity test Stored procedures test Stored procedures.
Ken Weinberg El Segundo, CA November 19, 2003 Adapting Small Projects Processes to CMMI.
Requirements Analysis
Software Quality Assurance Lecture #4 By: Faraz Ahmed.
K-12 Web Content Development Process
Independent User Acceptance Test Process (IUAT)
Understand Application Lifecycle Management
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
CCRS Comprehensive Conference Registration System Detailed Design March 6 th,
S Q A.
Web Analysis CIS 376 Bruce R. Maxim UM-Dearborn. Web Formulation Activities Identify business need for WebApp Work with stakeholders to describe WebApp.
CEN rd Lecture CEN 4021 Software Engineering II Instructor: Masoud Sadjadi Phases of Software.
1.  Describe an overall framework for project integration management ◦ RelatIion to the other project management knowledge areas and the project life.
SEPO Training - Code Review & Design Review by Amanda.
ISYS 562 Microcomputer Business Applications David Chao.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
© Copyright 2011 John Wiley & Sons, Inc.
Current and Future Applications of the Generic Statistical Business Process Model at Statistics Canada Laurie Reedman and Claude Julien May 5, 2010.
Software Development Cycle What is Software? Instructions (computer programs) that when executed provide desired function and performance Data structures.
Eurostat Expression language (EL) in Eurostat SDMX - TWG Luxembourg, 5 Jun 2013 Adam Wroński.
INFO 637Lecture #101 Software Engineering Process II Review INFO 637 Glenn Booker.
1 System for Administration, Training, and Educational Resources for NASA Introduction for SATERN Administration.
Historical Aspects Origin of software engineering –NATO study group coined the term in 1967 Software crisis –Low quality, schedule delay, and cost overrun.
6 th Annual Focus Users’ Conference 6 th Annual Focus Users’ Conference Import Testing Data Presented by: Adrian Ruiz Presented by: Adrian Ruiz.
Software Requirements: A More Rigorous Look 1. Features and Use Cases at a High Level of Abstraction  Helps to better understand the main characteristics.
Healthy Futures Performance Measures Session. Session Overview Combination of presentation and interactive components Time at the end of the session for.
G.Govi CERN/IT-DB 1 September 26, 2003 POOL Integration, Testing and Release Procedure Integration  Packages structure  External dependencies  Configuration.
Requirement engineering & Requirement tasks/Management. 1Prepared By:Jay A.Dave.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
IAEA International Atomic Energy Agency Development of the Basis Document for Periodic Safety Review for Research Reactors William Kennedy Research Reactor.
HUMANITARIAN RESPONSE MONITORING. HOW TO USE THIS PRESENTATION This presentation contains a complete overview of all aspects of Response Monitoring Presenting.
Requirement Elicitation Review – Class 8 Functional Requirements Nonfunctional Requirements Software Requirements document Requirements Validation and.
Testing and delivery Web design principles. Web development is software development.
CPMGT 300 Week 3 Learning Team Planning Process Groups and Developing the Scope Check this A+ tutorial guideline at
Software Specification Tools
Software Documentation
Roberta Roth, Alan Dennis, and Barbara Haley Wixom
Increased Efficiency and Effectiveness
Engineering Processes
Product Development Scenario Overview
Software Reviews.
Presentation transcript:

Unit Test Process Authors:Sergey Fedorov, Dmitry Balkin, Dmitry Korenkov June 2005

2 Definition and Scope of Unit Testing Unit Test Process (UTP) describes the usage of unit testing at the stage of component design and coding. UTP focused on test –Preparation, –Execution and –Follow-up activities UTP guards the correctness of the source code frozen as: –General –Restricted –Hot-fix “… unit test is a method of testing the correctness of a particular module of source code. The idea is to write test cases for every non-trivial function or method in the module so that each test case is separate from the others if possible.” (Wikipedia:

3 Reason for Unit Test Process  What are we trying to fix? –Process/procedure needs to be clearly understood Procedure is not clearly defined –UT reports are not produced consistently Output is not standard  What CMM KPA justify the change? –Level 3 Software Product Engineering

4 Unit Test Process Actors  Development Manager  Developer  QA Manager  QA Engineer  Project Manager  WIS - Business Applications

5 UTP Timeline Gate 0+ Gate 1Gate 2Gate 3 Preparation Execution Content Freeze Note: presented timelines are just recommendations and in each case Development Manager will set up the exact schedule depending on project specifics. Internal Freeze Unit Test Results Correction Freeze 1 Correction Freeze 2 Correction Freeze 3 Follow-up: Provide Unit Test Results to QA Unit Test Report Development Start

6 Process Overview Unit Testing is the part of Development, it consists of three activities:  Preparation resulted to  Execution resulted to  Follow-up Coordinated by Freezes Development coordination Freeze type Internal Project coordination Freeze type General, Restricted Content and Correction freeze in IPP Validated at Gate 2, finalized at Gate 3 Release coordination Freeze type Hot-fix, Restricted, General Hot-fix, Pre-release, CD-Refresh Follow-up Preparation Execution Freeze UT Results UT Report Development Start

7 UTP Preparation Activity Input: Siebel ERs Development documents, design, specs Source Code Output: T est cases Owner/Actor: Development Manager, Developer Development Manager: Coordinating preparation activity among development team members Developer: Develops test case, Updates development environment Documenting test case, updating ER in Siebel

8 UTP Execution Activity Input: Test Case, Development Environment, Component Module(s) Output: test case results for given input combination Owner/Actor: Development Manager, Developer Actions to perform: Development Manager: Coordinating execution activity among development team members Developer: Executing test case, Adjusting development environment Documenting test case results, updating ER in Siebel

9 UTP Follow-up Activity Input : Test case results Output: Freeze form  For project coordination: Unit Test Info field in Freeze form provides environment information XING Unit Test report generated and published/updated in DL Unit Test Results documents published/updated in DL or Frozen ERs updated with test cases information in Siebel  For release coordination: Unit Test Info field in Freeze form provides environment information Frozen ERs updated with test cases information in Siebel Owner/Actor: Development Manager, Developer Actions performed: Development Manager: Generates and publishes unit test reports, Consolidates and publishes unit test results Developer: Issues freeze form, updates Unit Test Info in a freeze form with Environment information

10 Documenting of Unit Test Cases Option 1: Unit Test Results document Using generic Test Case form, see "Unit Test Guidelines" or Table/text format, agreed by development team Mandatory fields/paragraphs are: –ER number –Test Case number (unique in document scope) –Input description and –Expected output description Option 2: ER updates in Siebel (recommended) Using Test Instructions or Specific tags, agreed by development team Mandatory fields are –Test Case Number (unique in ER scope) –Input description and –Expected output description

11 Generation of Unit Test Report 1.Navigate to XING/Reports/Unit Test 2.Type text and search for components 3.Select component 4.Select Family and Freeze type 5.Generate report Note: XING generated Unit Test Report includes link to Siebel ERs that allows interactive access to ER- level information directly from report (test case documenting Option 2).

12 Standard Unit Test Report Unit Test Report should be published in DL project repository, Unit Test sub-folder. Publish button may not work, in this case please save generated report and publish it through standard publishing interface of DL. Report Structure: Link to Freeze form Freeze type Unit Test Info From freeze form Link to Siebel ER ER Status/Sub- status Short Description

UTP Roles and Responsibilities  Development Manager: c oordinating unit test preparation and execution activities in development team, generates and publishes unit test reports, consolidates and publishes unit test results  Developer: developing, executing and documenting test cases, updating and adjusting development environment, updating ERs in Siebel, issues freeze forms, updates Unit Test Info in a freeze form with Environment information

Thank you!