Dashboard > CI Development > Home > Testing, Verification and Validation
Log In   View a printable version of the current page.
CI Development
Testing, Verification and Validation
Added by Michael Meisinger , last edited by Michael Meisinger on Feb 02, 2009  (view change)
Labels: 
(None)

This is the starting point for all CI internal V&V efforts and related processes

Process

  • Responsibilities
    • Development Team
      • Develop software to specification, requirements, use cases, agreements
      • Develop unit, integration and system tests
      • Document major architecture and design decisions and critical steps on the Wiki
      • Fix defects assigned to developers for targeted releases
      • Run existing test frequently
      • Before release, run existing tests on release candidate
      • Fix all blocker and critical defects before release
      • Document all open issues in Jira issue tracking system
      • Deliver release candidate to IVT for testing and keep untouched during test period
      • After IVT testing, fix blocker and critical issue; don't introduce new code
      • Report on software/release/defect status in development team meeting
    • Integration, Verification and Test Team (IVT) carried out by architecture team 
      • Receive release candidate from development team
      • Perform system and acceptance test
      • Document all open issues in Jira issue tracking system
      • Report on acceptance test status in development team meeting
      • Issue improvement and new feature requests as needed to maintain a sustainable architecture and user requensts
      • Document system architecture
      • Provide user documentation
    • Development Team Lead
      • Conduct weekly development team meetings
      • Keep track of assigned action items
      • Make release and defect fix decisions
      • Develop statements of work, assign tasks
      • Facilitate information exchange across team

Conventions

  • Issue Tracking using Jira
    • Fill in component, version and other available attributes
    • Be as lucid but also as specific as possible to describe the defect
    • Use consistent and clearly defined terminology. If in doubt, refer to a definition or provide one
    • Crash: The system or one of its components fails and stops and is unavailable subsequently.
    • Failure: An error occurs when executing a certain function

Powered by Atlassian Confluence 2.7.1, the Enterprise Wiki. Bug/feature request - Atlassian news - Contact administrators