Introduction

Purpose

The purpose of this document is to explain the different testing efforts for Unity in the Natty cycle. It is designed to prescribe the scope, approach, resources, and schedule for all testing activities during this cycle.

This document will be modified and enhanced as required throughout the verification testing engagement. The purpose of this document:

• Defines the overall test approach.
• Identifies software and system hardware to be tested.
• Identifies hardware, software, and tools to be used to support the testing efforts.
• Defines the types of tests to be performed.

Note: Specific effort for regression testing ?

Scope

The testing tasks for the components of Ubuntu includes:

• Functional testing of the applications (automated and manual - Desktop Testing initiative)
• Integration with the desktop environment
  • Unity
  • 2D Desktop (gnome fallback when 3D support is not available)
• Server Testing
• ISO Testing
• Hardware Testing
• Additional Testing: i18n, a11y, printing

For each testing task we will also:

• Collect, provide and review Test Cases that uncover new bugs or cover existing known issues.
• Collect test data and review testing results.
• Reporting of all test results.
• Risk analysis and communication of the blocking issues.

Testing will be performed all along during the development cycle of Natty. The main milestones of the test plan are aligned on the Release Schedule and Natty Release Interlock Testing is a very dependant activity, As a result, test planning is a continuing activity performed throughout the system development life cycle.

Note: HW Testing -> Cert Team: to be included in this doc ?

Project Milestones / Schedule

• Release Schedule

• Natty Release Interlock

Test Items and Features

New Features in Natty Narwhal (Ubuntu 11.04)

List the new features that need extensive testing

• GTK 3.0 with GObject Introspection is still a fairly young technology which is still in flux, so we need to regularly test our applications which got ported to it:

  • Apport: Try ubuntu-bug audio and select the "record" case, then follow the steps, and finally check if you get a reasonable output and behaviour of the details window (like unreasonable window size, or unreadable text). Please make sure to open the Details expander.