Ubuntu Wiki

• Launchpad Entry: lucid-qa-kernel-test-automation

• Created: 2009-11-09

• Contributors: AraPulido

• Packages affected: checkbox

Summary

The Kernel team has a set of automated tests that right now are not part of the tests run daily in the certification labs. We need to identify how they can be integrated and the steps to do it.

Release Note

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.

Rationale

This should cover the _why_: why is this change being proposed, what justifies it, where we see this justified.

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:

UI Changes

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

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

Objective: integrate kernel team tests into checkbox

Leann has been working on the scripts They should be integrate in a test suite

• kernel smoketests (run daily, as they go quickly)
• stress tests (run less frequently, more involved)

Problem: the kernel tests (most of them) need sudo

• workaround: in certification labs, we know the user/password and can hard-code it
  • we still need a good way to do this so the community can run these tests with proper credentials prompting

Tests in version control:

• Create a test suite
• Get the tree

The kernel team has around 4-5 testsuites wakealarm tests suspend/resume tests

Checkbox does not the concept of diverging from a previous snapshot Checkbox does not support yet the daily v.s. monthly idea (planned for Lucid)

NB: UEC and EC2 kernels are different -- testing UEC does not necessarily help EC2

LTP Autotest - it is available, but not enabled (it takes a long time to run)

ACTIONS

* Creating a blacklist of LTP tests * Fixing the LTP build * Evaluate EC2/UEC integration (cr3) * gcov kernel testing to evaluate kernel coverage (ogasawara to build kernel, talk to fader for testing) * Create a list of list of tests to run from autotest (ogasawara, cr3) * Clean up and commit kernel team scripts (ogasaware, cr3)

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