ARMTestsuitesAndProfilers

Differences between revisions 1 and 2
⇤ ← Revision 1 as of 2010-04-29 14:31:18 →
Size: 2676
Editor: fw-tnat
Comment:
← Revision 2 as of 2010-05-03 15:42:19 → ⇥
Size: 2444
Editor: 75-27-138-126
Comment:
Deletions are marked like this. Additions are marked like this.
Line 7: Line 7:
 * '''Contributors''':  * '''Contributors''': PaulLarson
Line 12: Line 12:
This should provide an overview of the issue/functionality/change proposed here. Focus here on what will actually be DONE, summarising that so that other people don't have to read the whole spec. See also CategorySpec for examples. The purpose of this blueprint is to discuss, decide on, and prioritize the testsuites and profiling tools that would be most useful to run on ARM devices in an automated testing environment. Focus should be on what is gained by them, whether or not they work on arm, and how long they take to run.
Line 16: Line 16:
This section should include a paragraph describing the end-user impact of this change. It is meant to be included in the release notes of the first release in which it is implemented. (Not all of these will actually be included in the release notes, at the release manager's discretion; but writing them is a useful exercise.)

It is mandatory.		 No user visible change.
Line 22: Line 20:
This should cover the _why_: why is this change being proposed, what justifies it, where we see this justified. There are a lot of well-known testsuites already available that will cover much of the functional and performance testing we wish to perform. If these tests work and perform adequately on ARM, it makes sense to run them and track the results.
Line 35: Line 33:

=== UI Changes ===

Should cover changes required to the UI, or specific UI that is required to implement this

UNDER CONSTRUCTION

Summary

The purpose of this blueprint is to discuss, decide on, and prioritize the testsuites and profiling tools that would be most useful to run on ARM devices in an automated testing environment. Focus should be on what is gained by them, whether or not they work on arm, and how long they take to run.

Release Note

No user visible change.

Rationale

There are a lot of well-known testsuites already available that will cover much of the functional and performance testing we wish to perform. If these tests work and perform adequately on ARM, it makes sense to run them and track the results.

User stories

Assumptions

Design

You can have subsections that better describe specific parts of the issue.

Implementation

This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:

Code Changes

Code changes should include an overview of what needs to change, and in some cases even the specific details.

Migration

Include:

  • data migration, if any
  • redirects from old URLs to new ones, if any
  • how users will be pointed to the new way of doing things, if necessary.

Test/Demo Plan

It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during testing, and to show off after release. Please add an entry to http://testcases.qa.ubuntu.com/Coverage/NewFeatures for tracking test coverage.

This need not be added or completed until the specification is nearing beta.

Unresolved issues

This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.

BoF agenda and discussion

Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected.

CategorySpec

Specs/M/ARMTestsuitesAndProfilers (last edited 2010-06-03 16:13:14 by 75-27-138-126)