MeeGo wiki - User contributions [en]

Quality/TestSuite/Framebuffer Test Specification

2010-12-20T14:25:15Z

Mikan: /* Troubleshooting */

= Introduction =

== Overview ==

The framebuffer device is a device-independent interface for reading and writing raw data to the video memory. Uses of the device typically include things like text consoles, graphical boot progress indicators and so on. It is also possible to use the framebuffer device as a X11 window system display device.

The framebuffer device is typically used by memory-mapping the device file. The fbdev kernel driver translates any operations to the device-specific display driver. The blts-fbdev-tests asset tests the functionality and performance of this subsystem.

The display backlight driver registers a sysfs based directory upon device activation. This is how the blts-fbdev-tests asset uses the backlight system to change display brightness.

== Getting the Latest Version ==

Sources can be found in gitorius:
* http://gitorious.org/qa-tools/mcts/trees/master/mcts-blts/blts-fbdev

To clone a copy of the repository, see guides in:
* http://gitorious.org/qa-tools/mcts

Latest binary release is planned to be available via MeeGo OBS, see [[Build_Infrastructure|MeeGo Build Infrastructure]] for more information.

== Support & Contacts ==

* IRC: miniinis in #meego-qa-mcts on irc.freenode.org
* Maintainer: [mailto:mika.niinisto@digia.com Mika Niinisto]
* Substitute: [mailto:jussi.saavalainen@digia.com Jussi Saavalainen]
* Bugs should be reported to MeeGo Bugzilla:
** [http://bugs.meego.com/enter_bug.cgi?product=MeeGo%20QA%20Test%20Suite Enter a MeeGo QA Test Suite bug], select component MeeGo Core Test Suite
** [[Quality/How_To_Report_Bugs | How to report bugs]]

== Documentation ==

Check the package README file (essentially contains same info as this page):
* [http://gitorious.org/qa-tools/mcts/blobs/master/mcts-blts/blts-fbdev/README README]

== Licensing ==
* Please see the file called COPYING

== Supported Devices and SW ==

The framebuffer tests should work with almost anything, that supports a framebuffer device. Given that the configuration is up to date and pointing to right framebuffer and backlight devices and limit values. The asset has been test to work with at least following Linux kernel versions: 2.6.28, 2.6.31 and 2.6.32.

== Test Cases ==

# Core-Framebuffer read frame buffer information with ioctl
#: Reads variant and fixed screen information from frame buffer device(s).
# Core-Framebuffer set blanking levels
#: Tests each of the blanking levels on all configured framebuffer devices.
# Core-Framebuffer 1-pixel uncached read
#: Performance test of reading visible framebuffer pixel by pixel. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured framebuffer devices.
# Core-Framebuffer 1-pixel uncached write
#: Performance test of writing into visible framebuffer pixel by pixel. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer device into the log and standard output. Done for all configured framebuffer devices.
# Core-Framebuffer 1-pixel uncached modify
#: Performance test of both reading and vriting into visible framebuffer pixel by pixel. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and and stadard output. Done for all configured framebuffer devices.
# Core-Framebuffer fullscreen buffer read
#: Performance test of reading a fullscreen framebuffer at once. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured devices.
# Core-Framebuffer fullscreen buffer write
#: Performance test of writing into a fullscreen framebuffer at once. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured devices.
# Core-Framebuffer fullscreen buffer modify
#: Performance test of both reading and writing into a fullscreen framebuffer at once. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured devices.
# Core-Backlight verify backlight levels
#: Verify backlight system's backlight level limits against configured limits. Tests the limit values, by using the actual limit and going one step over it.
# Core-Backlight linear backlight level changes
#: Linearly goes through all values between configured minimum and maximum values, by first going from min -> max and then from max -> min. NOTE: This case can timeout if the min and max are very big. The case sleeps for two seconds between each step.
# Core-Backlight logarithmic backlight level changes
#: Goes through all values between configured minimum and maximum values, by going from min -> max. The values are increased by following pattern: (max light / log10 (max light)) * log10 (between min and max). NOTE: This case can timeout if the min and max are very big. The case sleeps for two seconds between each step.

== Coverage ==

blts-fbdev-tests (0.0.8) is testing Linux kernel framebuffer ioctls and backlight subsystem via sysfs. The test driver accesses /dev/fbX directly with open(), close(), ioctl() and m(un)map(). Sysfs is accessed directly via fopen(), fprintf(), fscanf() and fclose().

Hardware coverage is device-dependent, but includes at least the data path diplay device - video memory - system memory.

Current framebuffer coverage matrix:

* [http://gitorious.org/qa-tools/mcts-coverage/blobs/master/Framebuffer-coverage.ods Framebuffer Coverage]

= Running the Tests =

== Hardware setup and test environment ==

The device, be it a notebook or N900 or Ubuntu, needs to have following packages installed:

* libbltscommon1
* blts-fbdev-tests-config (or something that provides this)
*: blts-fbdev-tests-config-example provides this, but does not work as such. '''You will need to edit the configuration file.'''

It is recommended that you configure your device not to automatically dim the screen when it becomes idle. This is because of the backlight tests, which will fail if something else changes the backlight while the tests are running.

== Building packages ==

The build environment must have the following packages installed:

;* [[../BLTS Common Library | libbltscommon-devel]]

{{:Quality/TestSuite/Building_BLTS_Packages}}

== Running test cases ==

The tests can be run with

<code>$ blts-fbdev-tests</code>

Command line arguments:

<code>
USAGE: blts-fbdev-tests [-l mylog.txt] [-e test1,test2...] [-en "my test"] [-s] [-?] [-v] [-C variation_config.cnf] [-auto|-v|-vv] [-xml|-axml filename]
-l: Used log file, default blts-fbdev-log.txt
-e: Execute single or multiple selected tests, for example -e 1,4,5.
-en: Execute test by name, for example -en "My test X"
-s: Show list of all tests
-C: Used parameter configuration file
-?: This message
-xml, -axml: Create result XML. -axml appends results to an existing XML file.
-auto: Silent logging for test automation. Only the results are printed to stdout.
-v: Verbose logging (default)
-vv: Even more verbose logging
</code>

Test cases must be run with root priviliges.

== Test result analysis ==

Results are typically printed into stdout and stderr. If -axml or -xml parameter is used, then the result will be printed as xml into the pointed file.

Log file is typically written into /var/log/tests/ dir. Default log file name is blts-fbdev-tests.txt. This can be tuned with -l command line parameter.

== Troubleshooting ==

If something fails, then first thing to do is to check the configuration. It's likely that in case of backlight, the backlight path is incorrect, or the minimum and maximum lights in configuration are out of range.

If a framebuffer device fails to map into memory, it might be due to wrong used device. Check with other frame buffer devices. List of devices is easiest to get with "ls /dev/fb*".

If none of these work, file a bug with the test case logs. It is preferred that the test case is run with -vv command line parameter in this case to get as much information as possible.

== Configuration file examples ==

To run test case with variable data you need to specify where configuration file is located. You can edit the configuration file yourself.

To run "Core-Backlight linear backlight level changes" case you can use:

<code>$ blts-fbdev-tests -l /var/log/tests/Core-Backlight_linear_backlight_level_changes.log -en "Core-Backlight linear backlight level changes" -C /etc/blts/blts-fbdev-tests.cnf</code>

Example of a configuration file (blts-fbdev-tests.cnf):

<pre>
# Parameter configuration for blts-fbdev

# Valid framebuffer devices for HW.
[parameter]
name framebuffer_device
const "/dev/fb0"
[end_parameter]

# Valid backlight subsystem for HW
[parameter]
name backlight_subsystem
const "/sys/class/backlight/<enter_valid_sysfs_entry_here>"
[end_parameter]

# Minimum light level
[parameter]
name minimum_level
const 0
[end_parameter]

# Maximum light level
[parameter]
name maximum_level
const 255
[end_parameter]

# Minimum light level for logarithmic tests
[parameter]
name logarithmic_min
const 1
[end_parameter]

# Maximum light level for logarithmic tests
[parameter]
name logarithmic_max
const 255
[end_parameter]

# Test case configurations
[test]
name "Core-Framebuffer read frame buffer information with ioctl"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer set blanking levels"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer 1-pixel uncached read"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer 1-pixel uncached write"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer 1-pixel uncached modify"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer fullscreen buffer read"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer fullscreen buffer write"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer fullscreen buffer modify"
params framebuffer_device
[end_test]

[test]
name "Core-Backlight verify backlight levels"
params backlight_subsystem minimum_level maximum_level
[end_test]

[test]
name "Core-Backlight linear backlight level changes"
params backlight_subsystem minimum_level maximum_level
[end_test]

[test]
name "Core-Backlight logarithmic backlight level changes"
params backlight_subsystem logarithmic_min logarithmic_max
[end_test]
</pre>

Replace "/sys/class/backlight/<enter_valid_sysfs_entry_here>" with a valid path to the backlight system your device registers.

= Module Design and Architecture =

== Architecture ==

The test asset (blts-fbdev-tests) is built directly on top of the Linux kernel. Backlight tests use sysfs to test the functionality.

= Known issues =
* The backlight cases take a lot of time. These cases try to go through all defined backlight levels. Might be better to define amount of steps or something similar into configuration.
* Check for open bugs: [http://bugs.meego.com/buglist.cgi?classification=MeeGo%20Projects&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&component=MeeGo%20Core%20Test%20Suite&product=MeeGo%20QA%20Test%20Suite MeeGo Core Test Suite Bugs]

= Future improvements =
The test driver should attemp to access the edges of the reported display area. Advanced improvements might include things like external camera use to determine whether the output from the test driver matches the actual on-screen results, aka test automation.

= References =
* [http://www.kernel.org Linux Kernel]
* [http://en.wikipedia.org/wiki/Framebuffer Framebuffer on Wikipedia]
* [http://www.linux-fbdev.org/ http://www.linux-fbdev.org]

Quality/TestSuite/Framebuffer Test Specification

2010-12-20T14:21:01Z

Mikan: /* Test result analysis */

= Introduction =

== Overview ==

The framebuffer device is a device-independent interface for reading and writing raw data to the video memory. Uses of the device typically include things like text consoles, graphical boot progress indicators and so on. It is also possible to use the framebuffer device as a X11 window system display device.

The framebuffer device is typically used by memory-mapping the device file. The fbdev kernel driver translates any operations to the device-specific display driver. The blts-fbdev-tests asset tests the functionality and performance of this subsystem.

The display backlight driver registers a sysfs based directory upon device activation. This is how the blts-fbdev-tests asset uses the backlight system to change display brightness.

== Getting the Latest Version ==

Sources can be found in gitorius:
* http://gitorious.org/qa-tools/mcts/trees/master/mcts-blts/blts-fbdev

To clone a copy of the repository, see guides in:
* http://gitorious.org/qa-tools/mcts

Latest binary release is planned to be available via MeeGo OBS, see [[Build_Infrastructure|MeeGo Build Infrastructure]] for more information.

== Support & Contacts ==

* IRC: miniinis in #meego-qa-mcts on irc.freenode.org
* Maintainer: [mailto:mika.niinisto@digia.com Mika Niinisto]
* Substitute: [mailto:jussi.saavalainen@digia.com Jussi Saavalainen]
* Bugs should be reported to MeeGo Bugzilla:
** [http://bugs.meego.com/enter_bug.cgi?product=MeeGo%20QA%20Test%20Suite Enter a MeeGo QA Test Suite bug], select component MeeGo Core Test Suite
** [[Quality/How_To_Report_Bugs | How to report bugs]]

== Documentation ==

Check the package README file (essentially contains same info as this page):
* [http://gitorious.org/qa-tools/mcts/blobs/master/mcts-blts/blts-fbdev/README README]

== Licensing ==
* Please see the file called COPYING

== Supported Devices and SW ==

The framebuffer tests should work with almost anything, that supports a framebuffer device. Given that the configuration is up to date and pointing to right framebuffer and backlight devices and limit values. The asset has been test to work with at least following Linux kernel versions: 2.6.28, 2.6.31 and 2.6.32.

== Test Cases ==

# Core-Framebuffer read frame buffer information with ioctl
#: Reads variant and fixed screen information from frame buffer device(s).
# Core-Framebuffer set blanking levels
#: Tests each of the blanking levels on all configured framebuffer devices.
# Core-Framebuffer 1-pixel uncached read
#: Performance test of reading visible framebuffer pixel by pixel. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured framebuffer devices.
# Core-Framebuffer 1-pixel uncached write
#: Performance test of writing into visible framebuffer pixel by pixel. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer device into the log and standard output. Done for all configured framebuffer devices.
# Core-Framebuffer 1-pixel uncached modify
#: Performance test of both reading and vriting into visible framebuffer pixel by pixel. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and and stadard output. Done for all configured framebuffer devices.
# Core-Framebuffer fullscreen buffer read
#: Performance test of reading a fullscreen framebuffer at once. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured devices.
# Core-Framebuffer fullscreen buffer write
#: Performance test of writing into a fullscreen framebuffer at once. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured devices.
# Core-Framebuffer fullscreen buffer modify
#: Performance test of both reading and writing into a fullscreen framebuffer at once. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured devices.
# Core-Backlight verify backlight levels
#: Verify backlight system's backlight level limits against configured limits. Tests the limit values, by using the actual limit and going one step over it.
# Core-Backlight linear backlight level changes
#: Linearly goes through all values between configured minimum and maximum values, by first going from min -> max and then from max -> min. NOTE: This case can timeout if the min and max are very big. The case sleeps for two seconds between each step.
# Core-Backlight logarithmic backlight level changes
#: Goes through all values between configured minimum and maximum values, by going from min -> max. The values are increased by following pattern: (max light / log10 (max light)) * log10 (between min and max). NOTE: This case can timeout if the min and max are very big. The case sleeps for two seconds between each step.

== Coverage ==

blts-fbdev-tests (0.0.8) is testing Linux kernel framebuffer ioctls and backlight subsystem via sysfs. The test driver accesses /dev/fbX directly with open(), close(), ioctl() and m(un)map(). Sysfs is accessed directly via fopen(), fprintf(), fscanf() and fclose().

Hardware coverage is device-dependent, but includes at least the data path diplay device - video memory - system memory.

Current framebuffer coverage matrix:

* [http://gitorious.org/qa-tools/mcts-coverage/blobs/master/Framebuffer-coverage.ods Framebuffer Coverage]

= Running the Tests =

== Hardware setup and test environment ==

The device, be it a notebook or N900 or Ubuntu, needs to have following packages installed:

* libbltscommon1
* blts-fbdev-tests-config (or something that provides this)
*: blts-fbdev-tests-config-example provides this, but does not work as such. '''You will need to edit the configuration file.'''

It is recommended that you configure your device not to automatically dim the screen when it becomes idle. This is because of the backlight tests, which will fail if something else changes the backlight while the tests are running.

== Building packages ==

The build environment must have the following packages installed:

;* [[../BLTS Common Library | libbltscommon-devel]]

{{:Quality/TestSuite/Building_BLTS_Packages}}

== Running test cases ==

The tests can be run with

<code>$ blts-fbdev-tests</code>

Command line arguments:

<code>
USAGE: blts-fbdev-tests [-l mylog.txt] [-e test1,test2...] [-en "my test"] [-s] [-?] [-v] [-C variation_config.cnf] [-auto|-v|-vv] [-xml|-axml filename]
-l: Used log file, default blts-fbdev-log.txt
-e: Execute single or multiple selected tests, for example -e 1,4,5.
-en: Execute test by name, for example -en "My test X"
-s: Show list of all tests
-C: Used parameter configuration file
-?: This message
-xml, -axml: Create result XML. -axml appends results to an existing XML file.
-auto: Silent logging for test automation. Only the results are printed to stdout.
-v: Verbose logging (default)
-vv: Even more verbose logging
</code>

Test cases must be run with root priviliges.

== Test result analysis ==

Results are typically printed into stdout and stderr. If -axml or -xml parameter is used, then the result will be printed as xml into the pointed file.

Log file is typically written into /var/log/tests/ dir. Default log file name is blts-fbdev-tests.txt. This can be tuned with -l command line parameter.

== Troubleshooting ==

* What to do if something fails?
* What to check first?

== Configuration file examples ==

To run test case with variable data you need to specify where configuration file is located. You can edit the configuration file yourself.

To run "Core-Backlight linear backlight level changes" case you can use:

<code>$ blts-fbdev-tests -l /var/log/tests/Core-Backlight_linear_backlight_level_changes.log -en "Core-Backlight linear backlight level changes" -C /etc/blts/blts-fbdev-tests.cnf</code>

Example of a configuration file (blts-fbdev-tests.cnf):

<pre>
# Parameter configuration for blts-fbdev

# Valid framebuffer devices for HW.
[parameter]
name framebuffer_device
const "/dev/fb0"
[end_parameter]

# Valid backlight subsystem for HW
[parameter]
name backlight_subsystem
const "/sys/class/backlight/<enter_valid_sysfs_entry_here>"
[end_parameter]

# Minimum light level
[parameter]
name minimum_level
const 0
[end_parameter]

# Maximum light level
[parameter]
name maximum_level
const 255
[end_parameter]

# Minimum light level for logarithmic tests
[parameter]
name logarithmic_min
const 1
[end_parameter]

# Maximum light level for logarithmic tests
[parameter]
name logarithmic_max
const 255
[end_parameter]

# Test case configurations
[test]
name "Core-Framebuffer read frame buffer information with ioctl"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer set blanking levels"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer 1-pixel uncached read"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer 1-pixel uncached write"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer 1-pixel uncached modify"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer fullscreen buffer read"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer fullscreen buffer write"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer fullscreen buffer modify"
params framebuffer_device
[end_test]

[test]
name "Core-Backlight verify backlight levels"
params backlight_subsystem minimum_level maximum_level
[end_test]

[test]
name "Core-Backlight linear backlight level changes"
params backlight_subsystem minimum_level maximum_level
[end_test]

[test]
name "Core-Backlight logarithmic backlight level changes"
params backlight_subsystem logarithmic_min logarithmic_max
[end_test]
</pre>

Replace "/sys/class/backlight/<enter_valid_sysfs_entry_here>" with a valid path to the backlight system your device registers.

= Module Design and Architecture =

== Architecture ==

The test asset (blts-fbdev-tests) is built directly on top of the Linux kernel. Backlight tests use sysfs to test the functionality.

= Known issues =
* The backlight cases take a lot of time. These cases try to go through all defined backlight levels. Might be better to define amount of steps or something similar into configuration.
* Check for open bugs: [http://bugs.meego.com/buglist.cgi?classification=MeeGo%20Projects&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&component=MeeGo%20Core%20Test%20Suite&product=MeeGo%20QA%20Test%20Suite MeeGo Core Test Suite Bugs]

= Future improvements =
The test driver should attemp to access the edges of the reported display area. Advanced improvements might include things like external camera use to determine whether the output from the test driver matches the actual on-screen results, aka test automation.

= References =
* [http://www.kernel.org Linux Kernel]
* [http://en.wikipedia.org/wiki/Framebuffer Framebuffer on Wikipedia]
* [http://www.linux-fbdev.org/ http://www.linux-fbdev.org]

Quality/TestSuite/Framebuffer Test Specification

2010-12-20T13:25:31Z

Mikan: /* Supported Devices and SW */

= Introduction =

== Overview ==

The framebuffer device is a device-independent interface for reading and writing raw data to the video memory. Uses of the device typically include things like text consoles, graphical boot progress indicators and so on. It is also possible to use the framebuffer device as a X11 window system display device.

The framebuffer device is typically used by memory-mapping the device file. The fbdev kernel driver translates any operations to the device-specific display driver. The blts-fbdev-tests asset tests the functionality and performance of this subsystem.

The display backlight driver registers a sysfs based directory upon device activation. This is how the blts-fbdev-tests asset uses the backlight system to change display brightness.

== Getting the Latest Version ==

Sources can be found in gitorius:
* http://gitorious.org/qa-tools/mcts/trees/master/mcts-blts/blts-fbdev

To clone a copy of the repository, see guides in:
* http://gitorious.org/qa-tools/mcts

Latest binary release is planned to be available via MeeGo OBS, see [[Build_Infrastructure|MeeGo Build Infrastructure]] for more information.

== Support & Contacts ==

* IRC: miniinis in #meego-qa-mcts on irc.freenode.org
* Maintainer: [mailto:mika.niinisto@digia.com Mika Niinisto]
* Substitute: [mailto:jussi.saavalainen@digia.com Jussi Saavalainen]
* Bugs should be reported to MeeGo Bugzilla:
** [http://bugs.meego.com/enter_bug.cgi?product=MeeGo%20QA%20Test%20Suite Enter a MeeGo QA Test Suite bug], select component MeeGo Core Test Suite
** [[Quality/How_To_Report_Bugs | How to report bugs]]

== Documentation ==

Check the package README file (essentially contains same info as this page):
* [http://gitorious.org/qa-tools/mcts/blobs/master/mcts-blts/blts-fbdev/README README]

== Licensing ==
* Please see the file called COPYING

== Supported Devices and SW ==

The framebuffer tests should work with almost anything, that supports a framebuffer device. Given that the configuration is up to date and pointing to right framebuffer and backlight devices and limit values. The asset has been test to work with at least following Linux kernel versions: 2.6.28, 2.6.31 and 2.6.32.

== Test Cases ==

# Core-Framebuffer read frame buffer information with ioctl
#: Reads variant and fixed screen information from frame buffer device(s).
# Core-Framebuffer set blanking levels
#: Tests each of the blanking levels on all configured framebuffer devices.
# Core-Framebuffer 1-pixel uncached read
#: Performance test of reading visible framebuffer pixel by pixel. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured framebuffer devices.
# Core-Framebuffer 1-pixel uncached write
#: Performance test of writing into visible framebuffer pixel by pixel. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer device into the log and standard output. Done for all configured framebuffer devices.
# Core-Framebuffer 1-pixel uncached modify
#: Performance test of both reading and vriting into visible framebuffer pixel by pixel. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and and stadard output. Done for all configured framebuffer devices.
# Core-Framebuffer fullscreen buffer read
#: Performance test of reading a fullscreen framebuffer at once. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured devices.
# Core-Framebuffer fullscreen buffer write
#: Performance test of writing into a fullscreen framebuffer at once. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured devices.
# Core-Framebuffer fullscreen buffer modify
#: Performance test of both reading and writing into a fullscreen framebuffer at once. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured devices.
# Core-Backlight verify backlight levels
#: Verify backlight system's backlight level limits against configured limits. Tests the limit values, by using the actual limit and going one step over it.
# Core-Backlight linear backlight level changes
#: Linearly goes through all values between configured minimum and maximum values, by first going from min -> max and then from max -> min. NOTE: This case can timeout if the min and max are very big. The case sleeps for two seconds between each step.
# Core-Backlight logarithmic backlight level changes
#: Goes through all values between configured minimum and maximum values, by going from min -> max. The values are increased by following pattern: (max light / log10 (max light)) * log10 (between min and max). NOTE: This case can timeout if the min and max are very big. The case sleeps for two seconds between each step.

== Coverage ==

blts-fbdev-tests (0.0.8) is testing Linux kernel framebuffer ioctls and backlight subsystem via sysfs. The test driver accesses /dev/fbX directly with open(), close(), ioctl() and m(un)map(). Sysfs is accessed directly via fopen(), fprintf(), fscanf() and fclose().

Hardware coverage is device-dependent, but includes at least the data path diplay device - video memory - system memory.

Current framebuffer coverage matrix:

* [http://gitorious.org/qa-tools/mcts-coverage/blobs/master/Framebuffer-coverage.ods Framebuffer Coverage]

= Running the Tests =

== Hardware setup and test environment ==

The device, be it a notebook or N900 or Ubuntu, needs to have following packages installed:

* libbltscommon1
* blts-fbdev-tests-config (or something that provides this)
*: blts-fbdev-tests-config-example provides this, but does not work as such. '''You will need to edit the configuration file.'''

It is recommended that you configure your device not to automatically dim the screen when it becomes idle. This is because of the backlight tests, which will fail if something else changes the backlight while the tests are running.

== Building packages ==

The build environment must have the following packages installed:

;* [[../BLTS Common Library | libbltscommon-devel]]

{{:Quality/TestSuite/Building_BLTS_Packages}}

== Running test cases ==

The tests can be run with

<code>$ blts-fbdev-tests</code>

Command line arguments:

<code>
USAGE: blts-fbdev-tests [-l mylog.txt] [-e test1,test2...] [-en "my test"] [-s] [-?] [-v] [-C variation_config.cnf] [-auto|-v|-vv] [-xml|-axml filename]
-l: Used log file, default blts-fbdev-log.txt
-e: Execute single or multiple selected tests, for example -e 1,4,5.
-en: Execute test by name, for example -en "My test X"
-s: Show list of all tests
-C: Used parameter configuration file
-?: This message
-xml, -axml: Create result XML. -axml appends results to an existing XML file.
-auto: Silent logging for test automation. Only the results are printed to stdout.
-v: Verbose logging (default)
-vv: Even more verbose logging
</code>

Test cases must be run with root priviliges.

== Test result analysis ==

* Where are the results?
* Log files?

== Troubleshooting ==

* What to do if something fails?
* What to check first?

== Configuration file examples ==

To run test case with variable data you need to specify where configuration file is located. You can edit the configuration file yourself.

To run "Core-Backlight linear backlight level changes" case you can use:

<code>$ blts-fbdev-tests -l /var/log/tests/Core-Backlight_linear_backlight_level_changes.log -en "Core-Backlight linear backlight level changes" -C /etc/blts/blts-fbdev-tests.cnf</code>

Example of a configuration file (blts-fbdev-tests.cnf):

<pre>
# Parameter configuration for blts-fbdev

# Valid framebuffer devices for HW.
[parameter]
name framebuffer_device
const "/dev/fb0"
[end_parameter]

# Valid backlight subsystem for HW
[parameter]
name backlight_subsystem
const "/sys/class/backlight/<enter_valid_sysfs_entry_here>"
[end_parameter]

# Minimum light level
[parameter]
name minimum_level
const 0
[end_parameter]

# Maximum light level
[parameter]
name maximum_level
const 255
[end_parameter]

# Minimum light level for logarithmic tests
[parameter]
name logarithmic_min
const 1
[end_parameter]

# Maximum light level for logarithmic tests
[parameter]
name logarithmic_max
const 255
[end_parameter]

# Test case configurations
[test]
name "Core-Framebuffer read frame buffer information with ioctl"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer set blanking levels"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer 1-pixel uncached read"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer 1-pixel uncached write"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer 1-pixel uncached modify"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer fullscreen buffer read"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer fullscreen buffer write"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer fullscreen buffer modify"
params framebuffer_device
[end_test]

[test]
name "Core-Backlight verify backlight levels"
params backlight_subsystem minimum_level maximum_level
[end_test]

[test]
name "Core-Backlight linear backlight level changes"
params backlight_subsystem minimum_level maximum_level
[end_test]

[test]
name "Core-Backlight logarithmic backlight level changes"
params backlight_subsystem logarithmic_min logarithmic_max
[end_test]
</pre>

Replace "/sys/class/backlight/<enter_valid_sysfs_entry_here>" with a valid path to the backlight system your device registers.

= Module Design and Architecture =

== Architecture ==

The test asset (blts-fbdev-tests) is built directly on top of the Linux kernel. Backlight tests use sysfs to test the functionality.

= Known issues =
* The backlight cases take a lot of time. These cases try to go through all defined backlight levels. Might be better to define amount of steps or something similar into configuration.
* Check for open bugs: [http://bugs.meego.com/buglist.cgi?classification=MeeGo%20Projects&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&component=MeeGo%20Core%20Test%20Suite&product=MeeGo%20QA%20Test%20Suite MeeGo Core Test Suite Bugs]

= Future improvements =
The test driver should attemp to access the edges of the reported display area. Advanced improvements might include things like external camera use to determine whether the output from the test driver matches the actual on-screen results, aka test automation.

= References =
* [http://www.kernel.org Linux Kernel]
* [http://en.wikipedia.org/wiki/Framebuffer Framebuffer on Wikipedia]
* [http://www.linux-fbdev.org/ http://www.linux-fbdev.org]

Quality/TestSuite/Framebuffer Test Specification

2010-12-20T13:25:10Z

Mikan: /* Architecture */

= Introduction =

== Overview ==

The framebuffer device is a device-independent interface for reading and writing raw data to the video memory. Uses of the device typically include things like text consoles, graphical boot progress indicators and so on. It is also possible to use the framebuffer device as a X11 window system display device.

The framebuffer device is typically used by memory-mapping the device file. The fbdev kernel driver translates any operations to the device-specific display driver. The blts-fbdev-tests asset tests the functionality and performance of this subsystem.

The display backlight driver registers a sysfs based directory upon device activation. This is how the blts-fbdev-tests asset uses the backlight system to change display brightness.

== Getting the Latest Version ==

Sources can be found in gitorius:
* http://gitorious.org/qa-tools/mcts/trees/master/mcts-blts/blts-fbdev

To clone a copy of the repository, see guides in:
* http://gitorious.org/qa-tools/mcts

Latest binary release is planned to be available via MeeGo OBS, see [[Build_Infrastructure|MeeGo Build Infrastructure]] for more information.

== Support & Contacts ==

* IRC: miniinis in #meego-qa-mcts on irc.freenode.org
* Maintainer: [mailto:mika.niinisto@digia.com Mika Niinisto]
* Substitute: [mailto:jussi.saavalainen@digia.com Jussi Saavalainen]
* Bugs should be reported to MeeGo Bugzilla:
** [http://bugs.meego.com/enter_bug.cgi?product=MeeGo%20QA%20Test%20Suite Enter a MeeGo QA Test Suite bug], select component MeeGo Core Test Suite
** [[Quality/How_To_Report_Bugs | How to report bugs]]

== Documentation ==

Check the package README file (essentially contains same info as this page):
* [http://gitorious.org/qa-tools/mcts/blobs/master/mcts-blts/blts-fbdev/README README]

== Licensing ==
* Please see the file called COPYING

== Supported Devices and SW ==

The framebuffer tests should work with almost anything, that supports a framebuffer device. Given that the configuration is up to date and pointing to right framebuffer and backlight devices and limit values.

== Test Cases ==

# Core-Framebuffer read frame buffer information with ioctl
#: Reads variant and fixed screen information from frame buffer device(s).
# Core-Framebuffer set blanking levels
#: Tests each of the blanking levels on all configured framebuffer devices.
# Core-Framebuffer 1-pixel uncached read
#: Performance test of reading visible framebuffer pixel by pixel. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured framebuffer devices.
# Core-Framebuffer 1-pixel uncached write
#: Performance test of writing into visible framebuffer pixel by pixel. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer device into the log and standard output. Done for all configured framebuffer devices.
# Core-Framebuffer 1-pixel uncached modify
#: Performance test of both reading and vriting into visible framebuffer pixel by pixel. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and and stadard output. Done for all configured framebuffer devices.
# Core-Framebuffer fullscreen buffer read
#: Performance test of reading a fullscreen framebuffer at once. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured devices.
# Core-Framebuffer fullscreen buffer write
#: Performance test of writing into a fullscreen framebuffer at once. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured devices.
# Core-Framebuffer fullscreen buffer modify
#: Performance test of both reading and writing into a fullscreen framebuffer at once. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured devices.
# Core-Backlight verify backlight levels
#: Verify backlight system's backlight level limits against configured limits. Tests the limit values, by using the actual limit and going one step over it.
# Core-Backlight linear backlight level changes
#: Linearly goes through all values between configured minimum and maximum values, by first going from min -> max and then from max -> min. NOTE: This case can timeout if the min and max are very big. The case sleeps for two seconds between each step.
# Core-Backlight logarithmic backlight level changes
#: Goes through all values between configured minimum and maximum values, by going from min -> max. The values are increased by following pattern: (max light / log10 (max light)) * log10 (between min and max). NOTE: This case can timeout if the min and max are very big. The case sleeps for two seconds between each step.

== Coverage ==

blts-fbdev-tests (0.0.8) is testing Linux kernel framebuffer ioctls and backlight subsystem via sysfs. The test driver accesses /dev/fbX directly with open(), close(), ioctl() and m(un)map(). Sysfs is accessed directly via fopen(), fprintf(), fscanf() and fclose().

Hardware coverage is device-dependent, but includes at least the data path diplay device - video memory - system memory.

Current framebuffer coverage matrix:

* [http://gitorious.org/qa-tools/mcts-coverage/blobs/master/Framebuffer-coverage.ods Framebuffer Coverage]

= Running the Tests =

== Hardware setup and test environment ==

The device, be it a notebook or N900 or Ubuntu, needs to have following packages installed:

* libbltscommon1
* blts-fbdev-tests-config (or something that provides this)
*: blts-fbdev-tests-config-example provides this, but does not work as such. '''You will need to edit the configuration file.'''

It is recommended that you configure your device not to automatically dim the screen when it becomes idle. This is because of the backlight tests, which will fail if something else changes the backlight while the tests are running.

== Building packages ==

The build environment must have the following packages installed:

;* [[../BLTS Common Library | libbltscommon-devel]]

{{:Quality/TestSuite/Building_BLTS_Packages}}

== Running test cases ==

The tests can be run with

<code>$ blts-fbdev-tests</code>

Command line arguments:

<code>
USAGE: blts-fbdev-tests [-l mylog.txt] [-e test1,test2...] [-en "my test"] [-s] [-?] [-v] [-C variation_config.cnf] [-auto|-v|-vv] [-xml|-axml filename]
-l: Used log file, default blts-fbdev-log.txt
-e: Execute single or multiple selected tests, for example -e 1,4,5.
-en: Execute test by name, for example -en "My test X"
-s: Show list of all tests
-C: Used parameter configuration file
-?: This message
-xml, -axml: Create result XML. -axml appends results to an existing XML file.
-auto: Silent logging for test automation. Only the results are printed to stdout.
-v: Verbose logging (default)
-vv: Even more verbose logging
</code>

Test cases must be run with root priviliges.

== Test result analysis ==

* Where are the results?
* Log files?

== Troubleshooting ==

* What to do if something fails?
* What to check first?

== Configuration file examples ==

To run test case with variable data you need to specify where configuration file is located. You can edit the configuration file yourself.

To run "Core-Backlight linear backlight level changes" case you can use:

<code>$ blts-fbdev-tests -l /var/log/tests/Core-Backlight_linear_backlight_level_changes.log -en "Core-Backlight linear backlight level changes" -C /etc/blts/blts-fbdev-tests.cnf</code>

Example of a configuration file (blts-fbdev-tests.cnf):

<pre>
# Parameter configuration for blts-fbdev

# Valid framebuffer devices for HW.
[parameter]
name framebuffer_device
const "/dev/fb0"
[end_parameter]

# Valid backlight subsystem for HW
[parameter]
name backlight_subsystem
const "/sys/class/backlight/<enter_valid_sysfs_entry_here>"
[end_parameter]

# Minimum light level
[parameter]
name minimum_level
const 0
[end_parameter]

# Maximum light level
[parameter]
name maximum_level
const 255
[end_parameter]

# Minimum light level for logarithmic tests
[parameter]
name logarithmic_min
const 1
[end_parameter]

# Maximum light level for logarithmic tests
[parameter]
name logarithmic_max
const 255
[end_parameter]

# Test case configurations
[test]
name "Core-Framebuffer read frame buffer information with ioctl"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer set blanking levels"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer 1-pixel uncached read"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer 1-pixel uncached write"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer 1-pixel uncached modify"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer fullscreen buffer read"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer fullscreen buffer write"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer fullscreen buffer modify"
params framebuffer_device
[end_test]

[test]
name "Core-Backlight verify backlight levels"
params backlight_subsystem minimum_level maximum_level
[end_test]

[test]
name "Core-Backlight linear backlight level changes"
params backlight_subsystem minimum_level maximum_level
[end_test]

[test]
name "Core-Backlight logarithmic backlight level changes"
params backlight_subsystem logarithmic_min logarithmic_max
[end_test]
</pre>

Replace "/sys/class/backlight/<enter_valid_sysfs_entry_here>" with a valid path to the backlight system your device registers.

= Module Design and Architecture =

== Architecture ==

The test asset (blts-fbdev-tests) is built directly on top of the Linux kernel. Backlight tests use sysfs to test the functionality.

= Known issues =
* The backlight cases take a lot of time. These cases try to go through all defined backlight levels. Might be better to define amount of steps or something similar into configuration.
* Check for open bugs: [http://bugs.meego.com/buglist.cgi?classification=MeeGo%20Projects&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&component=MeeGo%20Core%20Test%20Suite&product=MeeGo%20QA%20Test%20Suite MeeGo Core Test Suite Bugs]

= Future improvements =
The test driver should attemp to access the edges of the reported display area. Advanced improvements might include things like external camera use to determine whether the output from the test driver matches the actual on-screen results, aka test automation.

= References =
* [http://www.kernel.org Linux Kernel]
* [http://en.wikipedia.org/wiki/Framebuffer Framebuffer on Wikipedia]
* [http://www.linux-fbdev.org/ http://www.linux-fbdev.org]

Quality/TestSuite/Framebuffer Test Specification

2010-12-20T13:24:42Z

Mikan: /* Supported Devices and SW */

= Introduction =

== Overview ==

The framebuffer device is a device-independent interface for reading and writing raw data to the video memory. Uses of the device typically include things like text consoles, graphical boot progress indicators and so on. It is also possible to use the framebuffer device as a X11 window system display device.

The framebuffer device is typically used by memory-mapping the device file. The fbdev kernel driver translates any operations to the device-specific display driver. The blts-fbdev-tests asset tests the functionality and performance of this subsystem.

The display backlight driver registers a sysfs based directory upon device activation. This is how the blts-fbdev-tests asset uses the backlight system to change display brightness.

== Getting the Latest Version ==

Sources can be found in gitorius:
* http://gitorious.org/qa-tools/mcts/trees/master/mcts-blts/blts-fbdev

To clone a copy of the repository, see guides in:
* http://gitorious.org/qa-tools/mcts

Latest binary release is planned to be available via MeeGo OBS, see [[Build_Infrastructure|MeeGo Build Infrastructure]] for more information.

== Support & Contacts ==

* IRC: miniinis in #meego-qa-mcts on irc.freenode.org
* Maintainer: [mailto:mika.niinisto@digia.com Mika Niinisto]
* Substitute: [mailto:jussi.saavalainen@digia.com Jussi Saavalainen]
* Bugs should be reported to MeeGo Bugzilla:
** [http://bugs.meego.com/enter_bug.cgi?product=MeeGo%20QA%20Test%20Suite Enter a MeeGo QA Test Suite bug], select component MeeGo Core Test Suite
** [[Quality/How_To_Report_Bugs | How to report bugs]]

== Documentation ==

Check the package README file (essentially contains same info as this page):
* [http://gitorious.org/qa-tools/mcts/blobs/master/mcts-blts/blts-fbdev/README README]

== Licensing ==
* Please see the file called COPYING

== Supported Devices and SW ==

The framebuffer tests should work with almost anything, that supports a framebuffer device. Given that the configuration is up to date and pointing to right framebuffer and backlight devices and limit values.

== Test Cases ==

# Core-Framebuffer read frame buffer information with ioctl
#: Reads variant and fixed screen information from frame buffer device(s).
# Core-Framebuffer set blanking levels
#: Tests each of the blanking levels on all configured framebuffer devices.
# Core-Framebuffer 1-pixel uncached read
#: Performance test of reading visible framebuffer pixel by pixel. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured framebuffer devices.
# Core-Framebuffer 1-pixel uncached write
#: Performance test of writing into visible framebuffer pixel by pixel. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer device into the log and standard output. Done for all configured framebuffer devices.
# Core-Framebuffer 1-pixel uncached modify
#: Performance test of both reading and vriting into visible framebuffer pixel by pixel. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and and stadard output. Done for all configured framebuffer devices.
# Core-Framebuffer fullscreen buffer read
#: Performance test of reading a fullscreen framebuffer at once. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured devices.
# Core-Framebuffer fullscreen buffer write
#: Performance test of writing into a fullscreen framebuffer at once. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured devices.
# Core-Framebuffer fullscreen buffer modify
#: Performance test of both reading and writing into a fullscreen framebuffer at once. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured devices.
# Core-Backlight verify backlight levels
#: Verify backlight system's backlight level limits against configured limits. Tests the limit values, by using the actual limit and going one step over it.
# Core-Backlight linear backlight level changes
#: Linearly goes through all values between configured minimum and maximum values, by first going from min -> max and then from max -> min. NOTE: This case can timeout if the min and max are very big. The case sleeps for two seconds between each step.
# Core-Backlight logarithmic backlight level changes
#: Goes through all values between configured minimum and maximum values, by going from min -> max. The values are increased by following pattern: (max light / log10 (max light)) * log10 (between min and max). NOTE: This case can timeout if the min and max are very big. The case sleeps for two seconds between each step.

== Coverage ==

blts-fbdev-tests (0.0.8) is testing Linux kernel framebuffer ioctls and backlight subsystem via sysfs. The test driver accesses /dev/fbX directly with open(), close(), ioctl() and m(un)map(). Sysfs is accessed directly via fopen(), fprintf(), fscanf() and fclose().

Hardware coverage is device-dependent, but includes at least the data path diplay device - video memory - system memory.

Current framebuffer coverage matrix:

* [http://gitorious.org/qa-tools/mcts-coverage/blobs/master/Framebuffer-coverage.ods Framebuffer Coverage]

= Running the Tests =

== Hardware setup and test environment ==

The device, be it a notebook or N900 or Ubuntu, needs to have following packages installed:

* libbltscommon1
* blts-fbdev-tests-config (or something that provides this)
*: blts-fbdev-tests-config-example provides this, but does not work as such. '''You will need to edit the configuration file.'''

It is recommended that you configure your device not to automatically dim the screen when it becomes idle. This is because of the backlight tests, which will fail if something else changes the backlight while the tests are running.

== Building packages ==

The build environment must have the following packages installed:

;* [[../BLTS Common Library | libbltscommon-devel]]

{{:Quality/TestSuite/Building_BLTS_Packages}}

== Running test cases ==

The tests can be run with

<code>$ blts-fbdev-tests</code>

Command line arguments:

<code>
USAGE: blts-fbdev-tests [-l mylog.txt] [-e test1,test2...] [-en "my test"] [-s] [-?] [-v] [-C variation_config.cnf] [-auto|-v|-vv] [-xml|-axml filename]
-l: Used log file, default blts-fbdev-log.txt
-e: Execute single or multiple selected tests, for example -e 1,4,5.
-en: Execute test by name, for example -en "My test X"
-s: Show list of all tests
-C: Used parameter configuration file
-?: This message
-xml, -axml: Create result XML. -axml appends results to an existing XML file.
-auto: Silent logging for test automation. Only the results are printed to stdout.
-v: Verbose logging (default)
-vv: Even more verbose logging
</code>

Test cases must be run with root priviliges.

== Test result analysis ==

* Where are the results?
* Log files?

== Troubleshooting ==

* What to do if something fails?
* What to check first?

== Configuration file examples ==

To run test case with variable data you need to specify where configuration file is located. You can edit the configuration file yourself.

To run "Core-Backlight linear backlight level changes" case you can use:

<code>$ blts-fbdev-tests -l /var/log/tests/Core-Backlight_linear_backlight_level_changes.log -en "Core-Backlight linear backlight level changes" -C /etc/blts/blts-fbdev-tests.cnf</code>

Example of a configuration file (blts-fbdev-tests.cnf):

<pre>
# Parameter configuration for blts-fbdev

# Valid framebuffer devices for HW.
[parameter]
name framebuffer_device
const "/dev/fb0"
[end_parameter]

# Valid backlight subsystem for HW
[parameter]
name backlight_subsystem
const "/sys/class/backlight/<enter_valid_sysfs_entry_here>"
[end_parameter]

# Minimum light level
[parameter]
name minimum_level
const 0
[end_parameter]

# Maximum light level
[parameter]
name maximum_level
const 255
[end_parameter]

# Minimum light level for logarithmic tests
[parameter]
name logarithmic_min
const 1
[end_parameter]

# Maximum light level for logarithmic tests
[parameter]
name logarithmic_max
const 255
[end_parameter]

# Test case configurations
[test]
name "Core-Framebuffer read frame buffer information with ioctl"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer set blanking levels"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer 1-pixel uncached read"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer 1-pixel uncached write"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer 1-pixel uncached modify"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer fullscreen buffer read"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer fullscreen buffer write"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer fullscreen buffer modify"
params framebuffer_device
[end_test]

[test]
name "Core-Backlight verify backlight levels"
params backlight_subsystem minimum_level maximum_level
[end_test]

[test]
name "Core-Backlight linear backlight level changes"
params backlight_subsystem minimum_level maximum_level
[end_test]

[test]
name "Core-Backlight logarithmic backlight level changes"
params backlight_subsystem logarithmic_min logarithmic_max
[end_test]
</pre>

Replace "/sys/class/backlight/<enter_valid_sysfs_entry_here>" with a valid path to the backlight system your device registers.

= Module Design and Architecture =

== Architecture ==

The test asset (blts-fbdev-tests) is built directly on top of the Linux kernel. Backlight tests use sysfs to test the functionality. The asset has been test to work with at least following Linux kernel versions: 2.6.28, 2.6.31 and 2.6.32.

= Known issues =
* The backlight cases take a lot of time. These cases try to go through all defined backlight levels. Might be better to define amount of steps or something similar into configuration.
* Check for open bugs: [http://bugs.meego.com/buglist.cgi?classification=MeeGo%20Projects&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&component=MeeGo%20Core%20Test%20Suite&product=MeeGo%20QA%20Test%20Suite MeeGo Core Test Suite Bugs]

= Future improvements =
The test driver should attemp to access the edges of the reported display area. Advanced improvements might include things like external camera use to determine whether the output from the test driver matches the actual on-screen results, aka test automation.

= References =
* [http://www.kernel.org Linux Kernel]
* [http://en.wikipedia.org/wiki/Framebuffer Framebuffer on Wikipedia]
* [http://www.linux-fbdev.org/ http://www.linux-fbdev.org]

Quality/TestSuite/Framebuffer Test Specification

2010-12-20T13:23:10Z

Mikan: /* Hardware setup and test environment */

= Introduction =

== Overview ==

The framebuffer device is a device-independent interface for reading and writing raw data to the video memory. Uses of the device typically include things like text consoles, graphical boot progress indicators and so on. It is also possible to use the framebuffer device as a X11 window system display device.

The framebuffer device is typically used by memory-mapping the device file. The fbdev kernel driver translates any operations to the device-specific display driver. The blts-fbdev-tests asset tests the functionality and performance of this subsystem.

The display backlight driver registers a sysfs based directory upon device activation. This is how the blts-fbdev-tests asset uses the backlight system to change display brightness.

== Getting the Latest Version ==

Sources can be found in gitorius:
* http://gitorious.org/qa-tools/mcts/trees/master/mcts-blts/blts-fbdev

To clone a copy of the repository, see guides in:
* http://gitorious.org/qa-tools/mcts

Latest binary release is planned to be available via MeeGo OBS, see [[Build_Infrastructure|MeeGo Build Infrastructure]] for more information.

== Support & Contacts ==

* IRC: miniinis in #meego-qa-mcts on irc.freenode.org
* Maintainer: [mailto:mika.niinisto@digia.com Mika Niinisto]
* Substitute: [mailto:jussi.saavalainen@digia.com Jussi Saavalainen]
* Bugs should be reported to MeeGo Bugzilla:
** [http://bugs.meego.com/enter_bug.cgi?product=MeeGo%20QA%20Test%20Suite Enter a MeeGo QA Test Suite bug], select component MeeGo Core Test Suite
** [[Quality/How_To_Report_Bugs | How to report bugs]]

== Documentation ==

Check the package README file (essentially contains same info as this page):
* [http://gitorious.org/qa-tools/mcts/blobs/master/mcts-blts/blts-fbdev/README README]

== Licensing ==
* Please see the file called COPYING

== Supported Devices and SW ==

* List of supported (+ not supported devices, if needed for clarity)
** Versions
** Info about what is known to work

Supported
* N900
* nCDK Medfield (starting from version x.z)

Not supported
* Netbook

* Info about supported MeeGo releases (?)

== Test Cases ==

# Core-Framebuffer read frame buffer information with ioctl
#: Reads variant and fixed screen information from frame buffer device(s).
# Core-Framebuffer set blanking levels
#: Tests each of the blanking levels on all configured framebuffer devices.
# Core-Framebuffer 1-pixel uncached read
#: Performance test of reading visible framebuffer pixel by pixel. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured framebuffer devices.
# Core-Framebuffer 1-pixel uncached write
#: Performance test of writing into visible framebuffer pixel by pixel. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer device into the log and standard output. Done for all configured framebuffer devices.
# Core-Framebuffer 1-pixel uncached modify
#: Performance test of both reading and vriting into visible framebuffer pixel by pixel. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and and stadard output. Done for all configured framebuffer devices.
# Core-Framebuffer fullscreen buffer read
#: Performance test of reading a fullscreen framebuffer at once. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured devices.
# Core-Framebuffer fullscreen buffer write
#: Performance test of writing into a fullscreen framebuffer at once. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured devices.
# Core-Framebuffer fullscreen buffer modify
#: Performance test of both reading and writing into a fullscreen framebuffer at once. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured devices.
# Core-Backlight verify backlight levels
#: Verify backlight system's backlight level limits against configured limits. Tests the limit values, by using the actual limit and going one step over it.
# Core-Backlight linear backlight level changes
#: Linearly goes through all values between configured minimum and maximum values, by first going from min -> max and then from max -> min. NOTE: This case can timeout if the min and max are very big. The case sleeps for two seconds between each step.
# Core-Backlight logarithmic backlight level changes
#: Goes through all values between configured minimum and maximum values, by going from min -> max. The values are increased by following pattern: (max light / log10 (max light)) * log10 (between min and max). NOTE: This case can timeout if the min and max are very big. The case sleeps for two seconds between each step.

== Coverage ==

blts-fbdev-tests (0.0.8) is testing Linux kernel framebuffer ioctls and backlight subsystem via sysfs. The test driver accesses /dev/fbX directly with open(), close(), ioctl() and m(un)map(). Sysfs is accessed directly via fopen(), fprintf(), fscanf() and fclose().

Hardware coverage is device-dependent, but includes at least the data path diplay device - video memory - system memory.

Current framebuffer coverage matrix:

* [http://gitorious.org/qa-tools/mcts-coverage/blobs/master/Framebuffer-coverage.ods Framebuffer Coverage]

= Running the Tests =

== Hardware setup and test environment ==

The device, be it a notebook or N900 or Ubuntu, needs to have following packages installed:

* libbltscommon1
* blts-fbdev-tests-config (or something that provides this)
*: blts-fbdev-tests-config-example provides this, but does not work as such. '''You will need to edit the configuration file.'''

It is recommended that you configure your device not to automatically dim the screen when it becomes idle. This is because of the backlight tests, which will fail if something else changes the backlight while the tests are running.

== Building packages ==

The build environment must have the following packages installed:

;* [[../BLTS Common Library | libbltscommon-devel]]

{{:Quality/TestSuite/Building_BLTS_Packages}}

== Running test cases ==

The tests can be run with

<code>$ blts-fbdev-tests</code>

Command line arguments:

<code>
USAGE: blts-fbdev-tests [-l mylog.txt] [-e test1,test2...] [-en "my test"] [-s] [-?] [-v] [-C variation_config.cnf] [-auto|-v|-vv] [-xml|-axml filename]
-l: Used log file, default blts-fbdev-log.txt
-e: Execute single or multiple selected tests, for example -e 1,4,5.
-en: Execute test by name, for example -en "My test X"
-s: Show list of all tests
-C: Used parameter configuration file
-?: This message
-xml, -axml: Create result XML. -axml appends results to an existing XML file.
-auto: Silent logging for test automation. Only the results are printed to stdout.
-v: Verbose logging (default)
-vv: Even more verbose logging
</code>

Test cases must be run with root priviliges.

== Test result analysis ==

* Where are the results?
* Log files?

== Troubleshooting ==

* What to do if something fails?
* What to check first?

== Configuration file examples ==

To run test case with variable data you need to specify where configuration file is located. You can edit the configuration file yourself.

To run "Core-Backlight linear backlight level changes" case you can use:

<code>$ blts-fbdev-tests -l /var/log/tests/Core-Backlight_linear_backlight_level_changes.log -en "Core-Backlight linear backlight level changes" -C /etc/blts/blts-fbdev-tests.cnf</code>

Example of a configuration file (blts-fbdev-tests.cnf):

<pre>
# Parameter configuration for blts-fbdev

# Valid framebuffer devices for HW.
[parameter]
name framebuffer_device
const "/dev/fb0"
[end_parameter]

# Valid backlight subsystem for HW
[parameter]
name backlight_subsystem
const "/sys/class/backlight/<enter_valid_sysfs_entry_here>"
[end_parameter]

# Minimum light level
[parameter]
name minimum_level
const 0
[end_parameter]

# Maximum light level
[parameter]
name maximum_level
const 255
[end_parameter]

# Minimum light level for logarithmic tests
[parameter]
name logarithmic_min
const 1
[end_parameter]

# Maximum light level for logarithmic tests
[parameter]
name logarithmic_max
const 255
[end_parameter]

# Test case configurations
[test]
name "Core-Framebuffer read frame buffer information with ioctl"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer set blanking levels"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer 1-pixel uncached read"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer 1-pixel uncached write"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer 1-pixel uncached modify"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer fullscreen buffer read"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer fullscreen buffer write"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer fullscreen buffer modify"
params framebuffer_device
[end_test]

[test]
name "Core-Backlight verify backlight levels"
params backlight_subsystem minimum_level maximum_level
[end_test]

[test]
name "Core-Backlight linear backlight level changes"
params backlight_subsystem minimum_level maximum_level
[end_test]

[test]
name "Core-Backlight logarithmic backlight level changes"
params backlight_subsystem logarithmic_min logarithmic_max
[end_test]
</pre>

Replace "/sys/class/backlight/<enter_valid_sysfs_entry_here>" with a valid path to the backlight system your device registers.

= Module Design and Architecture =

== Architecture ==

The test asset (blts-fbdev-tests) is built directly on top of the Linux kernel. Backlight tests use sysfs to test the functionality. The asset has been test to work with at least following Linux kernel versions: 2.6.28, 2.6.31 and 2.6.32.

= Known issues =
* The backlight cases take a lot of time. These cases try to go through all defined backlight levels. Might be better to define amount of steps or something similar into configuration.
* Check for open bugs: [http://bugs.meego.com/buglist.cgi?classification=MeeGo%20Projects&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&component=MeeGo%20Core%20Test%20Suite&product=MeeGo%20QA%20Test%20Suite MeeGo Core Test Suite Bugs]

= Future improvements =
The test driver should attemp to access the edges of the reported display area. Advanced improvements might include things like external camera use to determine whether the output from the test driver matches the actual on-screen results, aka test automation.

= References =
* [http://www.kernel.org Linux Kernel]
* [http://en.wikipedia.org/wiki/Framebuffer Framebuffer on Wikipedia]
* [http://www.linux-fbdev.org/ http://www.linux-fbdev.org]

Quality/TestSuite/Framebuffer Test Specification

2010-12-20T13:22:01Z

Mikan: /* Hardware setup and test environment */

= Introduction =

== Overview ==

The framebuffer device is a device-independent interface for reading and writing raw data to the video memory. Uses of the device typically include things like text consoles, graphical boot progress indicators and so on. It is also possible to use the framebuffer device as a X11 window system display device.

The framebuffer device is typically used by memory-mapping the device file. The fbdev kernel driver translates any operations to the device-specific display driver. The blts-fbdev-tests asset tests the functionality and performance of this subsystem.

The display backlight driver registers a sysfs based directory upon device activation. This is how the blts-fbdev-tests asset uses the backlight system to change display brightness.

== Getting the Latest Version ==

Sources can be found in gitorius:
* http://gitorious.org/qa-tools/mcts/trees/master/mcts-blts/blts-fbdev

To clone a copy of the repository, see guides in:
* http://gitorious.org/qa-tools/mcts

Latest binary release is planned to be available via MeeGo OBS, see [[Build_Infrastructure|MeeGo Build Infrastructure]] for more information.

== Support & Contacts ==

* IRC: miniinis in #meego-qa-mcts on irc.freenode.org
* Maintainer: [mailto:mika.niinisto@digia.com Mika Niinisto]
* Substitute: [mailto:jussi.saavalainen@digia.com Jussi Saavalainen]
* Bugs should be reported to MeeGo Bugzilla:
** [http://bugs.meego.com/enter_bug.cgi?product=MeeGo%20QA%20Test%20Suite Enter a MeeGo QA Test Suite bug], select component MeeGo Core Test Suite
** [[Quality/How_To_Report_Bugs | How to report bugs]]

== Documentation ==

Check the package README file (essentially contains same info as this page):
* [http://gitorious.org/qa-tools/mcts/blobs/master/mcts-blts/blts-fbdev/README README]

== Licensing ==
* Please see the file called COPYING

== Supported Devices and SW ==

* List of supported (+ not supported devices, if needed for clarity)
** Versions
** Info about what is known to work

Supported
* N900
* nCDK Medfield (starting from version x.z)

Not supported
* Netbook

* Info about supported MeeGo releases (?)

== Test Cases ==

# Core-Framebuffer read frame buffer information with ioctl
#: Reads variant and fixed screen information from frame buffer device(s).
# Core-Framebuffer set blanking levels
#: Tests each of the blanking levels on all configured framebuffer devices.
# Core-Framebuffer 1-pixel uncached read
#: Performance test of reading visible framebuffer pixel by pixel. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured framebuffer devices.
# Core-Framebuffer 1-pixel uncached write
#: Performance test of writing into visible framebuffer pixel by pixel. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer device into the log and standard output. Done for all configured framebuffer devices.
# Core-Framebuffer 1-pixel uncached modify
#: Performance test of both reading and vriting into visible framebuffer pixel by pixel. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and and stadard output. Done for all configured framebuffer devices.
# Core-Framebuffer fullscreen buffer read
#: Performance test of reading a fullscreen framebuffer at once. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured devices.
# Core-Framebuffer fullscreen buffer write
#: Performance test of writing into a fullscreen framebuffer at once. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured devices.
# Core-Framebuffer fullscreen buffer modify
#: Performance test of both reading and writing into a fullscreen framebuffer at once. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured devices.
# Core-Backlight verify backlight levels
#: Verify backlight system's backlight level limits against configured limits. Tests the limit values, by using the actual limit and going one step over it.
# Core-Backlight linear backlight level changes
#: Linearly goes through all values between configured minimum and maximum values, by first going from min -> max and then from max -> min. NOTE: This case can timeout if the min and max are very big. The case sleeps for two seconds between each step.
# Core-Backlight logarithmic backlight level changes
#: Goes through all values between configured minimum and maximum values, by going from min -> max. The values are increased by following pattern: (max light / log10 (max light)) * log10 (between min and max). NOTE: This case can timeout if the min and max are very big. The case sleeps for two seconds between each step.

== Coverage ==

blts-fbdev-tests (0.0.8) is testing Linux kernel framebuffer ioctls and backlight subsystem via sysfs. The test driver accesses /dev/fbX directly with open(), close(), ioctl() and m(un)map(). Sysfs is accessed directly via fopen(), fprintf(), fscanf() and fclose().

Hardware coverage is device-dependent, but includes at least the data path diplay device - video memory - system memory.

Current framebuffer coverage matrix:

* [http://gitorious.org/qa-tools/mcts-coverage/blobs/master/Framebuffer-coverage.ods Framebuffer Coverage]

= Running the Tests =

== Hardware setup and test environment ==

The device, be it a notebook or N900 or Ubuntu, needs to have following packages installed:

* libbltscommon1
* blts-fbdev-tests-config (or something that provides this)
*: blts-fbdev-tests-config-example provides this, but does not work as such. '''You will need to edit the configuration file.'''

== Building packages ==

The build environment must have the following packages installed:

;* [[../BLTS Common Library | libbltscommon-devel]]

{{:Quality/TestSuite/Building_BLTS_Packages}}

== Running test cases ==

The tests can be run with

<code>$ blts-fbdev-tests</code>

Command line arguments:

<code>
USAGE: blts-fbdev-tests [-l mylog.txt] [-e test1,test2...] [-en "my test"] [-s] [-?] [-v] [-C variation_config.cnf] [-auto|-v|-vv] [-xml|-axml filename]
-l: Used log file, default blts-fbdev-log.txt
-e: Execute single or multiple selected tests, for example -e 1,4,5.
-en: Execute test by name, for example -en "My test X"
-s: Show list of all tests
-C: Used parameter configuration file
-?: This message
-xml, -axml: Create result XML. -axml appends results to an existing XML file.
-auto: Silent logging for test automation. Only the results are printed to stdout.
-v: Verbose logging (default)
-vv: Even more verbose logging
</code>

Test cases must be run with root priviliges.

== Test result analysis ==

* Where are the results?
* Log files?

== Troubleshooting ==

* What to do if something fails?
* What to check first?

== Configuration file examples ==

To run test case with variable data you need to specify where configuration file is located. You can edit the configuration file yourself.

To run "Core-Backlight linear backlight level changes" case you can use:

<code>$ blts-fbdev-tests -l /var/log/tests/Core-Backlight_linear_backlight_level_changes.log -en "Core-Backlight linear backlight level changes" -C /etc/blts/blts-fbdev-tests.cnf</code>

Example of a configuration file (blts-fbdev-tests.cnf):

<pre>
# Parameter configuration for blts-fbdev

# Valid framebuffer devices for HW.
[parameter]
name framebuffer_device
const "/dev/fb0"
[end_parameter]

# Valid backlight subsystem for HW
[parameter]
name backlight_subsystem
const "/sys/class/backlight/<enter_valid_sysfs_entry_here>"
[end_parameter]

# Minimum light level
[parameter]
name minimum_level
const 0
[end_parameter]

# Maximum light level
[parameter]
name maximum_level
const 255
[end_parameter]

# Minimum light level for logarithmic tests
[parameter]
name logarithmic_min
const 1
[end_parameter]

# Maximum light level for logarithmic tests
[parameter]
name logarithmic_max
const 255
[end_parameter]

# Test case configurations
[test]
name "Core-Framebuffer read frame buffer information with ioctl"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer set blanking levels"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer 1-pixel uncached read"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer 1-pixel uncached write"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer 1-pixel uncached modify"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer fullscreen buffer read"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer fullscreen buffer write"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer fullscreen buffer modify"
params framebuffer_device
[end_test]

[test]
name "Core-Backlight verify backlight levels"
params backlight_subsystem minimum_level maximum_level
[end_test]

[test]
name "Core-Backlight linear backlight level changes"
params backlight_subsystem minimum_level maximum_level
[end_test]

[test]
name "Core-Backlight logarithmic backlight level changes"
params backlight_subsystem logarithmic_min logarithmic_max
[end_test]
</pre>

Replace "/sys/class/backlight/<enter_valid_sysfs_entry_here>" with a valid path to the backlight system your device registers.

= Module Design and Architecture =

== Architecture ==

The test asset (blts-fbdev-tests) is built directly on top of the Linux kernel. Backlight tests use sysfs to test the functionality. The asset has been test to work with at least following Linux kernel versions: 2.6.28, 2.6.31 and 2.6.32.

= Known issues =
* The backlight cases take a lot of time. These cases try to go through all defined backlight levels. Might be better to define amount of steps or something similar into configuration.
* Check for open bugs: [http://bugs.meego.com/buglist.cgi?classification=MeeGo%20Projects&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&component=MeeGo%20Core%20Test%20Suite&product=MeeGo%20QA%20Test%20Suite MeeGo Core Test Suite Bugs]

= Future improvements =
The test driver should attemp to access the edges of the reported display area. Advanced improvements might include things like external camera use to determine whether the output from the test driver matches the actual on-screen results, aka test automation.

= References =
* [http://www.kernel.org Linux Kernel]
* [http://en.wikipedia.org/wiki/Framebuffer Framebuffer on Wikipedia]
* [http://www.linux-fbdev.org/ http://www.linux-fbdev.org]

Quality/TestSuite/Framebuffer Test Specification

2010-12-20T13:18:27Z

Mikan: /* Running test cases */

= Introduction =

== Overview ==

The framebuffer device is a device-independent interface for reading and writing raw data to the video memory. Uses of the device typically include things like text consoles, graphical boot progress indicators and so on. It is also possible to use the framebuffer device as a X11 window system display device.

The framebuffer device is typically used by memory-mapping the device file. The fbdev kernel driver translates any operations to the device-specific display driver. The blts-fbdev-tests asset tests the functionality and performance of this subsystem.

The display backlight driver registers a sysfs based directory upon device activation. This is how the blts-fbdev-tests asset uses the backlight system to change display brightness.

== Getting the Latest Version ==

Sources can be found in gitorius:
* http://gitorious.org/qa-tools/mcts/trees/master/mcts-blts/blts-fbdev

To clone a copy of the repository, see guides in:
* http://gitorious.org/qa-tools/mcts

Latest binary release is planned to be available via MeeGo OBS, see [[Build_Infrastructure|MeeGo Build Infrastructure]] for more information.

== Support & Contacts ==

* IRC: miniinis in #meego-qa-mcts on irc.freenode.org
* Maintainer: [mailto:mika.niinisto@digia.com Mika Niinisto]
* Substitute: [mailto:jussi.saavalainen@digia.com Jussi Saavalainen]
* Bugs should be reported to MeeGo Bugzilla:
** [http://bugs.meego.com/enter_bug.cgi?product=MeeGo%20QA%20Test%20Suite Enter a MeeGo QA Test Suite bug], select component MeeGo Core Test Suite
** [[Quality/How_To_Report_Bugs | How to report bugs]]

== Documentation ==

Check the package README file (essentially contains same info as this page):
* [http://gitorious.org/qa-tools/mcts/blobs/master/mcts-blts/blts-fbdev/README README]

== Licensing ==
* Please see the file called COPYING

== Supported Devices and SW ==

* List of supported (+ not supported devices, if needed for clarity)
** Versions
** Info about what is known to work

Supported
* N900
* nCDK Medfield (starting from version x.z)

Not supported
* Netbook

* Info about supported MeeGo releases (?)

== Test Cases ==

# Core-Framebuffer read frame buffer information with ioctl
#: Reads variant and fixed screen information from frame buffer device(s).
# Core-Framebuffer set blanking levels
#: Tests each of the blanking levels on all configured framebuffer devices.
# Core-Framebuffer 1-pixel uncached read
#: Performance test of reading visible framebuffer pixel by pixel. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured framebuffer devices.
# Core-Framebuffer 1-pixel uncached write
#: Performance test of writing into visible framebuffer pixel by pixel. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer device into the log and standard output. Done for all configured framebuffer devices.
# Core-Framebuffer 1-pixel uncached modify
#: Performance test of both reading and vriting into visible framebuffer pixel by pixel. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and and stadard output. Done for all configured framebuffer devices.
# Core-Framebuffer fullscreen buffer read
#: Performance test of reading a fullscreen framebuffer at once. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured devices.
# Core-Framebuffer fullscreen buffer write
#: Performance test of writing into a fullscreen framebuffer at once. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured devices.
# Core-Framebuffer fullscreen buffer modify
#: Performance test of both reading and writing into a fullscreen framebuffer at once. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured devices.
# Core-Backlight verify backlight levels
#: Verify backlight system's backlight level limits against configured limits. Tests the limit values, by using the actual limit and going one step over it.
# Core-Backlight linear backlight level changes
#: Linearly goes through all values between configured minimum and maximum values, by first going from min -> max and then from max -> min. NOTE: This case can timeout if the min and max are very big. The case sleeps for two seconds between each step.
# Core-Backlight logarithmic backlight level changes
#: Goes through all values between configured minimum and maximum values, by going from min -> max. The values are increased by following pattern: (max light / log10 (max light)) * log10 (between min and max). NOTE: This case can timeout if the min and max are very big. The case sleeps for two seconds between each step.

== Coverage ==

blts-fbdev-tests (0.0.8) is testing Linux kernel framebuffer ioctls and backlight subsystem via sysfs. The test driver accesses /dev/fbX directly with open(), close(), ioctl() and m(un)map(). Sysfs is accessed directly via fopen(), fprintf(), fscanf() and fclose().

Hardware coverage is device-dependent, but includes at least the data path diplay device - video memory - system memory.

Current framebuffer coverage matrix:

* [http://gitorious.org/qa-tools/mcts-coverage/blobs/master/Framebuffer-coverage.ods Framebuffer Coverage]

= Running the Tests =

== Hardware setup and test environment ==

== Building packages ==

The build environment must have the following packages installed:

;* [[../BLTS Common Library | libbltscommon-devel]]

{{:Quality/TestSuite/Building_BLTS_Packages}}

== Running test cases ==

The tests can be run with

<code>$ blts-fbdev-tests</code>

Command line arguments:

<code>
USAGE: blts-fbdev-tests [-l mylog.txt] [-e test1,test2...] [-en "my test"] [-s] [-?] [-v] [-C variation_config.cnf] [-auto|-v|-vv] [-xml|-axml filename]
-l: Used log file, default blts-fbdev-log.txt
-e: Execute single or multiple selected tests, for example -e 1,4,5.
-en: Execute test by name, for example -en "My test X"
-s: Show list of all tests
-C: Used parameter configuration file
-?: This message
-xml, -axml: Create result XML. -axml appends results to an existing XML file.
-auto: Silent logging for test automation. Only the results are printed to stdout.
-v: Verbose logging (default)
-vv: Even more verbose logging
</code>

Test cases must be run with root priviliges.

== Test result analysis ==

* Where are the results?
* Log files?

== Troubleshooting ==

* What to do if something fails?
* What to check first?

== Configuration file examples ==

To run test case with variable data you need to specify where configuration file is located. You can edit the configuration file yourself.

To run "Core-Backlight linear backlight level changes" case you can use:

<code>$ blts-fbdev-tests -l /var/log/tests/Core-Backlight_linear_backlight_level_changes.log -en "Core-Backlight linear backlight level changes" -C /etc/blts/blts-fbdev-tests.cnf</code>

Example of a configuration file (blts-fbdev-tests.cnf):

<pre>
# Parameter configuration for blts-fbdev

# Valid framebuffer devices for HW.
[parameter]
name framebuffer_device
const "/dev/fb0"
[end_parameter]

# Valid backlight subsystem for HW
[parameter]
name backlight_subsystem
const "/sys/class/backlight/<enter_valid_sysfs_entry_here>"
[end_parameter]

# Minimum light level
[parameter]
name minimum_level
const 0
[end_parameter]

# Maximum light level
[parameter]
name maximum_level
const 255
[end_parameter]

# Minimum light level for logarithmic tests
[parameter]
name logarithmic_min
const 1
[end_parameter]

# Maximum light level for logarithmic tests
[parameter]
name logarithmic_max
const 255
[end_parameter]

# Test case configurations
[test]
name "Core-Framebuffer read frame buffer information with ioctl"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer set blanking levels"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer 1-pixel uncached read"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer 1-pixel uncached write"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer 1-pixel uncached modify"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer fullscreen buffer read"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer fullscreen buffer write"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer fullscreen buffer modify"
params framebuffer_device
[end_test]

[test]
name "Core-Backlight verify backlight levels"
params backlight_subsystem minimum_level maximum_level
[end_test]

[test]
name "Core-Backlight linear backlight level changes"
params backlight_subsystem minimum_level maximum_level
[end_test]

[test]
name "Core-Backlight logarithmic backlight level changes"
params backlight_subsystem logarithmic_min logarithmic_max
[end_test]
</pre>

Replace "/sys/class/backlight/<enter_valid_sysfs_entry_here>" with a valid path to the backlight system your device registers.

= Module Design and Architecture =

== Architecture ==

The test asset (blts-fbdev-tests) is built directly on top of the Linux kernel. Backlight tests use sysfs to test the functionality. The asset has been test to work with at least following Linux kernel versions: 2.6.28, 2.6.31 and 2.6.32.

= Known issues =
* The backlight cases take a lot of time. These cases try to go through all defined backlight levels. Might be better to define amount of steps or something similar into configuration.
* Check for open bugs: [http://bugs.meego.com/buglist.cgi?classification=MeeGo%20Projects&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&component=MeeGo%20Core%20Test%20Suite&product=MeeGo%20QA%20Test%20Suite MeeGo Core Test Suite Bugs]

= Future improvements =
The test driver should attemp to access the edges of the reported display area. Advanced improvements might include things like external camera use to determine whether the output from the test driver matches the actual on-screen results, aka test automation.

= References =
* [http://www.kernel.org Linux Kernel]
* [http://en.wikipedia.org/wiki/Framebuffer Framebuffer on Wikipedia]
* [http://www.linux-fbdev.org/ http://www.linux-fbdev.org]

Quality/TestSuite/Framebuffer Test Specification

2010-12-20T13:16:32Z

Mikan: /* Running test cases */

= Introduction =

== Overview ==

The framebuffer device is a device-independent interface for reading and writing raw data to the video memory. Uses of the device typically include things like text consoles, graphical boot progress indicators and so on. It is also possible to use the framebuffer device as a X11 window system display device.

The framebuffer device is typically used by memory-mapping the device file. The fbdev kernel driver translates any operations to the device-specific display driver. The blts-fbdev-tests asset tests the functionality and performance of this subsystem.

The display backlight driver registers a sysfs based directory upon device activation. This is how the blts-fbdev-tests asset uses the backlight system to change display brightness.

== Getting the Latest Version ==

Sources can be found in gitorius:
* http://gitorious.org/qa-tools/mcts/trees/master/mcts-blts/blts-fbdev

To clone a copy of the repository, see guides in:
* http://gitorious.org/qa-tools/mcts

Latest binary release is planned to be available via MeeGo OBS, see [[Build_Infrastructure|MeeGo Build Infrastructure]] for more information.

== Support & Contacts ==

* IRC: miniinis in #meego-qa-mcts on irc.freenode.org
* Maintainer: [mailto:mika.niinisto@digia.com Mika Niinisto]
* Substitute: [mailto:jussi.saavalainen@digia.com Jussi Saavalainen]
* Bugs should be reported to MeeGo Bugzilla:
** [http://bugs.meego.com/enter_bug.cgi?product=MeeGo%20QA%20Test%20Suite Enter a MeeGo QA Test Suite bug], select component MeeGo Core Test Suite
** [[Quality/How_To_Report_Bugs | How to report bugs]]

== Documentation ==

Check the package README file (essentially contains same info as this page):
* [http://gitorious.org/qa-tools/mcts/blobs/master/mcts-blts/blts-fbdev/README README]

== Licensing ==
* Please see the file called COPYING

== Supported Devices and SW ==

* List of supported (+ not supported devices, if needed for clarity)
** Versions
** Info about what is known to work

Supported
* N900
* nCDK Medfield (starting from version x.z)

Not supported
* Netbook

* Info about supported MeeGo releases (?)

== Test Cases ==

# Core-Framebuffer read frame buffer information with ioctl
#: Reads variant and fixed screen information from frame buffer device(s).
# Core-Framebuffer set blanking levels
#: Tests each of the blanking levels on all configured framebuffer devices.
# Core-Framebuffer 1-pixel uncached read
#: Performance test of reading visible framebuffer pixel by pixel. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured framebuffer devices.
# Core-Framebuffer 1-pixel uncached write
#: Performance test of writing into visible framebuffer pixel by pixel. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer device into the log and standard output. Done for all configured framebuffer devices.
# Core-Framebuffer 1-pixel uncached modify
#: Performance test of both reading and vriting into visible framebuffer pixel by pixel. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and and stadard output. Done for all configured framebuffer devices.
# Core-Framebuffer fullscreen buffer read
#: Performance test of reading a fullscreen framebuffer at once. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured devices.
# Core-Framebuffer fullscreen buffer write
#: Performance test of writing into a fullscreen framebuffer at once. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured devices.
# Core-Framebuffer fullscreen buffer modify
#: Performance test of both reading and writing into a fullscreen framebuffer at once. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured devices.
# Core-Backlight verify backlight levels
#: Verify backlight system's backlight level limits against configured limits. Tests the limit values, by using the actual limit and going one step over it.
# Core-Backlight linear backlight level changes
#: Linearly goes through all values between configured minimum and maximum values, by first going from min -> max and then from max -> min. NOTE: This case can timeout if the min and max are very big. The case sleeps for two seconds between each step.
# Core-Backlight logarithmic backlight level changes
#: Goes through all values between configured minimum and maximum values, by going from min -> max. The values are increased by following pattern: (max light / log10 (max light)) * log10 (between min and max). NOTE: This case can timeout if the min and max are very big. The case sleeps for two seconds between each step.

== Coverage ==

blts-fbdev-tests (0.0.8) is testing Linux kernel framebuffer ioctls and backlight subsystem via sysfs. The test driver accesses /dev/fbX directly with open(), close(), ioctl() and m(un)map(). Sysfs is accessed directly via fopen(), fprintf(), fscanf() and fclose().

Hardware coverage is device-dependent, but includes at least the data path diplay device - video memory - system memory.

Current framebuffer coverage matrix:

* [http://gitorious.org/qa-tools/mcts-coverage/blobs/master/Framebuffer-coverage.ods Framebuffer Coverage]

= Running the Tests =

== Hardware setup and test environment ==

== Building packages ==

The build environment must have the following packages installed:

;* [[../BLTS Common Library | libbltscommon-devel]]

{{:Quality/TestSuite/Building_BLTS_Packages}}

== Running test cases ==

The tests can be run with

<code>$ blts-fbdev-tests</code>

Command line arguments

| *Switch* | *Details* |
| -l | Used log file, default blts-fbdev-log.txt |
| -e | Execute single or multiple selected tests, for example -e 1,4,5. |
| -en | Execute test by name, for example -en "My test X" |
| -s | Show list of all tests |
| -C | Used parameter configuration file |
| -? | Help message |
| -nc | Do not output log to terminal |
| -v | Verbose logging |
| -vv | Very Verbose logging |

Test cases must be run with root priviliges.

== Test result analysis ==

* Where are the results?
* Log files?

== Troubleshooting ==

* What to do if something fails?
* What to check first?

== Configuration file examples ==

To run test case with variable data you need to specify where configuration file is located. You can edit the configuration file yourself.

To run "Core-Backlight linear backlight level changes" case you can use:

<code>$ blts-fbdev-tests -l /var/log/tests/Core-Backlight_linear_backlight_level_changes.log -en "Core-Backlight linear backlight level changes" -C /etc/blts/blts-fbdev-tests.cnf</code>

Example of a configuration file (blts-fbdev-tests.cnf):

<pre>
# Parameter configuration for blts-fbdev

# Valid framebuffer devices for HW.
[parameter]
name framebuffer_device
const "/dev/fb0"
[end_parameter]

# Valid backlight subsystem for HW
[parameter]
name backlight_subsystem
const "/sys/class/backlight/<enter_valid_sysfs_entry_here>"
[end_parameter]

# Minimum light level
[parameter]
name minimum_level
const 0
[end_parameter]

# Maximum light level
[parameter]
name maximum_level
const 255
[end_parameter]

# Minimum light level for logarithmic tests
[parameter]
name logarithmic_min
const 1
[end_parameter]

# Maximum light level for logarithmic tests
[parameter]
name logarithmic_max
const 255
[end_parameter]

# Test case configurations
[test]
name "Core-Framebuffer read frame buffer information with ioctl"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer set blanking levels"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer 1-pixel uncached read"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer 1-pixel uncached write"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer 1-pixel uncached modify"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer fullscreen buffer read"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer fullscreen buffer write"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer fullscreen buffer modify"
params framebuffer_device
[end_test]

[test]
name "Core-Backlight verify backlight levels"
params backlight_subsystem minimum_level maximum_level
[end_test]

[test]
name "Core-Backlight linear backlight level changes"
params backlight_subsystem minimum_level maximum_level
[end_test]

[test]
name "Core-Backlight logarithmic backlight level changes"
params backlight_subsystem logarithmic_min logarithmic_max
[end_test]
</pre>

Replace "/sys/class/backlight/<enter_valid_sysfs_entry_here>" with a valid path to the backlight system your device registers.

= Module Design and Architecture =

== Architecture ==

The test asset (blts-fbdev-tests) is built directly on top of the Linux kernel. Backlight tests use sysfs to test the functionality. The asset has been test to work with at least following Linux kernel versions: 2.6.28, 2.6.31 and 2.6.32.

= Known issues =
* The backlight cases take a lot of time. These cases try to go through all defined backlight levels. Might be better to define amount of steps or something similar into configuration.
* Check for open bugs: [http://bugs.meego.com/buglist.cgi?classification=MeeGo%20Projects&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&component=MeeGo%20Core%20Test%20Suite&product=MeeGo%20QA%20Test%20Suite MeeGo Core Test Suite Bugs]

= Future improvements =
The test driver should attemp to access the edges of the reported display area. Advanced improvements might include things like external camera use to determine whether the output from the test driver matches the actual on-screen results, aka test automation.

= References =
* [http://www.kernel.org Linux Kernel]
* [http://en.wikipedia.org/wiki/Framebuffer Framebuffer on Wikipedia]
* [http://www.linux-fbdev.org/ http://www.linux-fbdev.org]

Quality/TestSuite/Framebuffer Test Specification

2010-12-20T13:15:55Z

Mikan: /* Hardware setup and test environment */

= Introduction =

== Overview ==

The framebuffer device is a device-independent interface for reading and writing raw data to the video memory. Uses of the device typically include things like text consoles, graphical boot progress indicators and so on. It is also possible to use the framebuffer device as a X11 window system display device.

The framebuffer device is typically used by memory-mapping the device file. The fbdev kernel driver translates any operations to the device-specific display driver. The blts-fbdev-tests asset tests the functionality and performance of this subsystem.

The display backlight driver registers a sysfs based directory upon device activation. This is how the blts-fbdev-tests asset uses the backlight system to change display brightness.

== Getting the Latest Version ==

Sources can be found in gitorius:
* http://gitorious.org/qa-tools/mcts/trees/master/mcts-blts/blts-fbdev

To clone a copy of the repository, see guides in:
* http://gitorious.org/qa-tools/mcts

Latest binary release is planned to be available via MeeGo OBS, see [[Build_Infrastructure|MeeGo Build Infrastructure]] for more information.

== Support & Contacts ==

* IRC: miniinis in #meego-qa-mcts on irc.freenode.org
* Maintainer: [mailto:mika.niinisto@digia.com Mika Niinisto]
* Substitute: [mailto:jussi.saavalainen@digia.com Jussi Saavalainen]
* Bugs should be reported to MeeGo Bugzilla:
** [http://bugs.meego.com/enter_bug.cgi?product=MeeGo%20QA%20Test%20Suite Enter a MeeGo QA Test Suite bug], select component MeeGo Core Test Suite
** [[Quality/How_To_Report_Bugs | How to report bugs]]

== Documentation ==

Check the package README file (essentially contains same info as this page):
* [http://gitorious.org/qa-tools/mcts/blobs/master/mcts-blts/blts-fbdev/README README]

== Licensing ==
* Please see the file called COPYING

== Supported Devices and SW ==

* List of supported (+ not supported devices, if needed for clarity)
** Versions
** Info about what is known to work

Supported
* N900
* nCDK Medfield (starting from version x.z)

Not supported
* Netbook

* Info about supported MeeGo releases (?)

== Test Cases ==

# Core-Framebuffer read frame buffer information with ioctl
#: Reads variant and fixed screen information from frame buffer device(s).
# Core-Framebuffer set blanking levels
#: Tests each of the blanking levels on all configured framebuffer devices.
# Core-Framebuffer 1-pixel uncached read
#: Performance test of reading visible framebuffer pixel by pixel. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured framebuffer devices.
# Core-Framebuffer 1-pixel uncached write
#: Performance test of writing into visible framebuffer pixel by pixel. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer device into the log and standard output. Done for all configured framebuffer devices.
# Core-Framebuffer 1-pixel uncached modify
#: Performance test of both reading and vriting into visible framebuffer pixel by pixel. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and and stadard output. Done for all configured framebuffer devices.
# Core-Framebuffer fullscreen buffer read
#: Performance test of reading a fullscreen framebuffer at once. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured devices.
# Core-Framebuffer fullscreen buffer write
#: Performance test of writing into a fullscreen framebuffer at once. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured devices.
# Core-Framebuffer fullscreen buffer modify
#: Performance test of both reading and writing into a fullscreen framebuffer at once. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured devices.
# Core-Backlight verify backlight levels
#: Verify backlight system's backlight level limits against configured limits. Tests the limit values, by using the actual limit and going one step over it.
# Core-Backlight linear backlight level changes
#: Linearly goes through all values between configured minimum and maximum values, by first going from min -> max and then from max -> min. NOTE: This case can timeout if the min and max are very big. The case sleeps for two seconds between each step.
# Core-Backlight logarithmic backlight level changes
#: Goes through all values between configured minimum and maximum values, by going from min -> max. The values are increased by following pattern: (max light / log10 (max light)) * log10 (between min and max). NOTE: This case can timeout if the min and max are very big. The case sleeps for two seconds between each step.

== Coverage ==

blts-fbdev-tests (0.0.8) is testing Linux kernel framebuffer ioctls and backlight subsystem via sysfs. The test driver accesses /dev/fbX directly with open(), close(), ioctl() and m(un)map(). Sysfs is accessed directly via fopen(), fprintf(), fscanf() and fclose().

Hardware coverage is device-dependent, but includes at least the data path diplay device - video memory - system memory.

Current framebuffer coverage matrix:

* [http://gitorious.org/qa-tools/mcts-coverage/blobs/master/Framebuffer-coverage.ods Framebuffer Coverage]

= Running the Tests =

== Hardware setup and test environment ==

== Building packages ==

The build environment must have the following packages installed:

;* [[../BLTS Common Library | libbltscommon-devel]]

{{:Quality/TestSuite/Building_BLTS_Packages}}

== Running test cases ==

* Step-by-step instructions how to execute tests with an example
* Root or user privileges?
* What to do if something goes wrong?
** How to run in debug mode?
** What to look in log files?

== Test result analysis ==

* Where are the results?
* Log files?

== Troubleshooting ==

* What to do if something fails?
* What to check first?

== Configuration file examples ==

To run test case with variable data you need to specify where configuration file is located. You can edit the configuration file yourself.

To run "Core-Backlight linear backlight level changes" case you can use:

<code>$ blts-fbdev-tests -l /var/log/tests/Core-Backlight_linear_backlight_level_changes.log -en "Core-Backlight linear backlight level changes" -C /etc/blts/blts-fbdev-tests.cnf</code>

Example of a configuration file (blts-fbdev-tests.cnf):

<pre>
# Parameter configuration for blts-fbdev

# Valid framebuffer devices for HW.
[parameter]
name framebuffer_device
const "/dev/fb0"
[end_parameter]

# Valid backlight subsystem for HW
[parameter]
name backlight_subsystem
const "/sys/class/backlight/<enter_valid_sysfs_entry_here>"
[end_parameter]

# Minimum light level
[parameter]
name minimum_level
const 0
[end_parameter]

# Maximum light level
[parameter]
name maximum_level
const 255
[end_parameter]

# Minimum light level for logarithmic tests
[parameter]
name logarithmic_min
const 1
[end_parameter]

# Maximum light level for logarithmic tests
[parameter]
name logarithmic_max
const 255
[end_parameter]

# Test case configurations
[test]
name "Core-Framebuffer read frame buffer information with ioctl"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer set blanking levels"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer 1-pixel uncached read"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer 1-pixel uncached write"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer 1-pixel uncached modify"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer fullscreen buffer read"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer fullscreen buffer write"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer fullscreen buffer modify"
params framebuffer_device
[end_test]

[test]
name "Core-Backlight verify backlight levels"
params backlight_subsystem minimum_level maximum_level
[end_test]

[test]
name "Core-Backlight linear backlight level changes"
params backlight_subsystem minimum_level maximum_level
[end_test]

[test]
name "Core-Backlight logarithmic backlight level changes"
params backlight_subsystem logarithmic_min logarithmic_max
[end_test]
</pre>

Replace "/sys/class/backlight/<enter_valid_sysfs_entry_here>" with a valid path to the backlight system your device registers.

= Module Design and Architecture =

== Architecture ==

The test asset (blts-fbdev-tests) is built directly on top of the Linux kernel. Backlight tests use sysfs to test the functionality. The asset has been test to work with at least following Linux kernel versions: 2.6.28, 2.6.31 and 2.6.32.

= Known issues =
* The backlight cases take a lot of time. These cases try to go through all defined backlight levels. Might be better to define amount of steps or something similar into configuration.
* Check for open bugs: [http://bugs.meego.com/buglist.cgi?classification=MeeGo%20Projects&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&component=MeeGo%20Core%20Test%20Suite&product=MeeGo%20QA%20Test%20Suite MeeGo Core Test Suite Bugs]

= Future improvements =
The test driver should attemp to access the edges of the reported display area. Advanced improvements might include things like external camera use to determine whether the output from the test driver matches the actual on-screen results, aka test automation.

= References =
* [http://www.kernel.org Linux Kernel]
* [http://en.wikipedia.org/wiki/Framebuffer Framebuffer on Wikipedia]
* [http://www.linux-fbdev.org/ http://www.linux-fbdev.org]

Quality/TestSuite/Framebuffer Test Specification

2010-12-20T13:15:40Z

Mikan: /* Hardware setup and test environment */

= Introduction =

== Overview ==

The framebuffer device is a device-independent interface for reading and writing raw data to the video memory. Uses of the device typically include things like text consoles, graphical boot progress indicators and so on. It is also possible to use the framebuffer device as a X11 window system display device.

The framebuffer device is typically used by memory-mapping the device file. The fbdev kernel driver translates any operations to the device-specific display driver. The blts-fbdev-tests asset tests the functionality and performance of this subsystem.

The display backlight driver registers a sysfs based directory upon device activation. This is how the blts-fbdev-tests asset uses the backlight system to change display brightness.

== Getting the Latest Version ==

Sources can be found in gitorius:
* http://gitorious.org/qa-tools/mcts/trees/master/mcts-blts/blts-fbdev

To clone a copy of the repository, see guides in:
* http://gitorious.org/qa-tools/mcts

Latest binary release is planned to be available via MeeGo OBS, see [[Build_Infrastructure|MeeGo Build Infrastructure]] for more information.

== Support & Contacts ==

* IRC: miniinis in #meego-qa-mcts on irc.freenode.org
* Maintainer: [mailto:mika.niinisto@digia.com Mika Niinisto]
* Substitute: [mailto:jussi.saavalainen@digia.com Jussi Saavalainen]
* Bugs should be reported to MeeGo Bugzilla:
** [http://bugs.meego.com/enter_bug.cgi?product=MeeGo%20QA%20Test%20Suite Enter a MeeGo QA Test Suite bug], select component MeeGo Core Test Suite
** [[Quality/How_To_Report_Bugs | How to report bugs]]

== Documentation ==

Check the package README file (essentially contains same info as this page):
* [http://gitorious.org/qa-tools/mcts/blobs/master/mcts-blts/blts-fbdev/README README]

== Licensing ==
* Please see the file called COPYING

== Supported Devices and SW ==

* List of supported (+ not supported devices, if needed for clarity)
** Versions
** Info about what is known to work

Supported
* N900
* nCDK Medfield (starting from version x.z)

Not supported
* Netbook

* Info about supported MeeGo releases (?)

== Test Cases ==

# Core-Framebuffer read frame buffer information with ioctl
#: Reads variant and fixed screen information from frame buffer device(s).
# Core-Framebuffer set blanking levels
#: Tests each of the blanking levels on all configured framebuffer devices.
# Core-Framebuffer 1-pixel uncached read
#: Performance test of reading visible framebuffer pixel by pixel. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured framebuffer devices.
# Core-Framebuffer 1-pixel uncached write
#: Performance test of writing into visible framebuffer pixel by pixel. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer device into the log and standard output. Done for all configured framebuffer devices.
# Core-Framebuffer 1-pixel uncached modify
#: Performance test of both reading and vriting into visible framebuffer pixel by pixel. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and and stadard output. Done for all configured framebuffer devices.
# Core-Framebuffer fullscreen buffer read
#: Performance test of reading a fullscreen framebuffer at once. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured devices.
# Core-Framebuffer fullscreen buffer write
#: Performance test of writing into a fullscreen framebuffer at once. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured devices.
# Core-Framebuffer fullscreen buffer modify
#: Performance test of both reading and writing into a fullscreen framebuffer at once. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured devices.
# Core-Backlight verify backlight levels
#: Verify backlight system's backlight level limits against configured limits. Tests the limit values, by using the actual limit and going one step over it.
# Core-Backlight linear backlight level changes
#: Linearly goes through all values between configured minimum and maximum values, by first going from min -> max and then from max -> min. NOTE: This case can timeout if the min and max are very big. The case sleeps for two seconds between each step.
# Core-Backlight logarithmic backlight level changes
#: Goes through all values between configured minimum and maximum values, by going from min -> max. The values are increased by following pattern: (max light / log10 (max light)) * log10 (between min and max). NOTE: This case can timeout if the min and max are very big. The case sleeps for two seconds between each step.

== Coverage ==

blts-fbdev-tests (0.0.8) is testing Linux kernel framebuffer ioctls and backlight subsystem via sysfs. The test driver accesses /dev/fbX directly with open(), close(), ioctl() and m(un)map(). Sysfs is accessed directly via fopen(), fprintf(), fscanf() and fclose().

Hardware coverage is device-dependent, but includes at least the data path diplay device - video memory - system memory.

Current framebuffer coverage matrix:

* [http://gitorious.org/qa-tools/mcts-coverage/blobs/master/Framebuffer-coverage.ods Framebuffer Coverage]

= Running the Tests =

== Hardware setup and test environment ==

The tests can be run with

<code>$ blts-fbdev-tests</code>

Command line arguments

| *Switch* | *Details* |
| -l | Used log file, default blts-fbdev-log.txt |
| -e | Execute single or multiple selected tests, for example -e 1,4,5. |
| -en | Execute test by name, for example -en "My test X" |
| -s | Show list of all tests |
| -C | Used parameter configuration file |
| -? | Help message |
| -nc | Do not output log to terminal |
| -v | Verbose logging |

Test cases must be run with root priviliges.

== Building packages ==

The build environment must have the following packages installed:

;* [[../BLTS Common Library | libbltscommon-devel]]

{{:Quality/TestSuite/Building_BLTS_Packages}}

== Running test cases ==

* Step-by-step instructions how to execute tests with an example
* Root or user privileges?
* What to do if something goes wrong?
** How to run in debug mode?
** What to look in log files?

== Test result analysis ==

* Where are the results?
* Log files?

== Troubleshooting ==

* What to do if something fails?
* What to check first?

== Configuration file examples ==

To run test case with variable data you need to specify where configuration file is located. You can edit the configuration file yourself.

To run "Core-Backlight linear backlight level changes" case you can use:

<code>$ blts-fbdev-tests -l /var/log/tests/Core-Backlight_linear_backlight_level_changes.log -en "Core-Backlight linear backlight level changes" -C /etc/blts/blts-fbdev-tests.cnf</code>

Example of a configuration file (blts-fbdev-tests.cnf):

<pre>
# Parameter configuration for blts-fbdev

# Valid framebuffer devices for HW.
[parameter]
name framebuffer_device
const "/dev/fb0"
[end_parameter]

# Valid backlight subsystem for HW
[parameter]
name backlight_subsystem
const "/sys/class/backlight/<enter_valid_sysfs_entry_here>"
[end_parameter]

# Minimum light level
[parameter]
name minimum_level
const 0
[end_parameter]

# Maximum light level
[parameter]
name maximum_level
const 255
[end_parameter]

# Minimum light level for logarithmic tests
[parameter]
name logarithmic_min
const 1
[end_parameter]

# Maximum light level for logarithmic tests
[parameter]
name logarithmic_max
const 255
[end_parameter]

# Test case configurations
[test]
name "Core-Framebuffer read frame buffer information with ioctl"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer set blanking levels"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer 1-pixel uncached read"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer 1-pixel uncached write"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer 1-pixel uncached modify"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer fullscreen buffer read"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer fullscreen buffer write"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer fullscreen buffer modify"
params framebuffer_device
[end_test]

[test]
name "Core-Backlight verify backlight levels"
params backlight_subsystem minimum_level maximum_level
[end_test]

[test]
name "Core-Backlight linear backlight level changes"
params backlight_subsystem minimum_level maximum_level
[end_test]

[test]
name "Core-Backlight logarithmic backlight level changes"
params backlight_subsystem logarithmic_min logarithmic_max
[end_test]
</pre>

Replace "/sys/class/backlight/<enter_valid_sysfs_entry_here>" with a valid path to the backlight system your device registers.

= Module Design and Architecture =

== Architecture ==

The test asset (blts-fbdev-tests) is built directly on top of the Linux kernel. Backlight tests use sysfs to test the functionality. The asset has been test to work with at least following Linux kernel versions: 2.6.28, 2.6.31 and 2.6.32.

= Known issues =
* The backlight cases take a lot of time. These cases try to go through all defined backlight levels. Might be better to define amount of steps or something similar into configuration.
* Check for open bugs: [http://bugs.meego.com/buglist.cgi?classification=MeeGo%20Projects&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&component=MeeGo%20Core%20Test%20Suite&product=MeeGo%20QA%20Test%20Suite MeeGo Core Test Suite Bugs]

= Future improvements =
The test driver should attemp to access the edges of the reported display area. Advanced improvements might include things like external camera use to determine whether the output from the test driver matches the actual on-screen results, aka test automation.

= References =
* [http://www.kernel.org Linux Kernel]
* [http://en.wikipedia.org/wiki/Framebuffer Framebuffer on Wikipedia]
* [http://www.linux-fbdev.org/ http://www.linux-fbdev.org]

Quality/TestSuite/Framebuffer Test Specification

2010-12-20T12:55:16Z

Mikan: /* Configuration file examples */

= Introduction =

== Overview ==

The framebuffer device is a device-independent interface for reading and writing raw data to the video memory. Uses of the device typically include things like text consoles, graphical boot progress indicators and so on. It is also possible to use the framebuffer device as a X11 window system display device.

The framebuffer device is typically used by memory-mapping the device file. The fbdev kernel driver translates any operations to the device-specific display driver. The blts-fbdev-tests asset tests the functionality and performance of this subsystem.

The display backlight driver registers a sysfs based directory upon device activation. This is how the blts-fbdev-tests asset uses the backlight system to change display brightness.

== Getting the Latest Version ==

Sources can be found in gitorius:
* http://gitorious.org/qa-tools/mcts/trees/master/mcts-blts/blts-fbdev

To clone a copy of the repository, see guides in:
* http://gitorious.org/qa-tools/mcts

Latest binary release is planned to be available via MeeGo OBS, see [[Build_Infrastructure|MeeGo Build Infrastructure]] for more information.

== Support & Contacts ==

* IRC: miniinis in #meego-qa-mcts on irc.freenode.org
* Maintainer: [mailto:mika.niinisto@digia.com Mika Niinisto]
* Substitute: [mailto:jussi.saavalainen@digia.com Jussi Saavalainen]
* Bugs should be reported to MeeGo Bugzilla:
** [http://bugs.meego.com/enter_bug.cgi?product=MeeGo%20QA%20Test%20Suite Enter a MeeGo QA Test Suite bug], select component MeeGo Core Test Suite
** [[Quality/How_To_Report_Bugs | How to report bugs]]

== Documentation ==

Check the package README file (essentially contains same info as this page):
* [http://gitorious.org/qa-tools/mcts/blobs/master/mcts-blts/blts-fbdev/README README]

== Licensing ==
* Please see the file called COPYING

== Supported Devices and SW ==

* List of supported (+ not supported devices, if needed for clarity)
** Versions
** Info about what is known to work

Supported
* N900
* nCDK Medfield (starting from version x.z)

Not supported
* Netbook

* Info about supported MeeGo releases (?)

== Test Cases ==

# Core-Framebuffer read frame buffer information with ioctl
#: Reads variant and fixed screen information from frame buffer device(s).
# Core-Framebuffer set blanking levels
#: Tests each of the blanking levels on all configured framebuffer devices.
# Core-Framebuffer 1-pixel uncached read
#: Performance test of reading visible framebuffer pixel by pixel. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured framebuffer devices.
# Core-Framebuffer 1-pixel uncached write
#: Performance test of writing into visible framebuffer pixel by pixel. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer device into the log and standard output. Done for all configured framebuffer devices.
# Core-Framebuffer 1-pixel uncached modify
#: Performance test of both reading and vriting into visible framebuffer pixel by pixel. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and and stadard output. Done for all configured framebuffer devices.
# Core-Framebuffer fullscreen buffer read
#: Performance test of reading a fullscreen framebuffer at once. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured devices.
# Core-Framebuffer fullscreen buffer write
#: Performance test of writing into a fullscreen framebuffer at once. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured devices.
# Core-Framebuffer fullscreen buffer modify
#: Performance test of both reading and writing into a fullscreen framebuffer at once. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured devices.
# Core-Backlight verify backlight levels
#: Verify backlight system's backlight level limits against configured limits. Tests the limit values, by using the actual limit and going one step over it.
# Core-Backlight linear backlight level changes
#: Linearly goes through all values between configured minimum and maximum values, by first going from min -> max and then from max -> min. NOTE: This case can timeout if the min and max are very big. The case sleeps for two seconds between each step.
# Core-Backlight logarithmic backlight level changes
#: Goes through all values between configured minimum and maximum values, by going from min -> max. The values are increased by following pattern: (max light / log10 (max light)) * log10 (between min and max). NOTE: This case can timeout if the min and max are very big. The case sleeps for two seconds between each step.

== Coverage ==

blts-fbdev-tests (0.0.8) is testing Linux kernel framebuffer ioctls and backlight subsystem via sysfs. The test driver accesses /dev/fbX directly with open(), close(), ioctl() and m(un)map(). Sysfs is accessed directly via fopen(), fprintf(), fscanf() and fclose().

Hardware coverage is device-dependent, but includes at least the data path diplay device - video memory - system memory.

Current framebuffer coverage matrix:

* [http://gitorious.org/qa-tools/mcts-coverage/blobs/master/Framebuffer-coverage.ods Framebuffer Coverage]

= Running the Tests =

== Hardware setup and test environment ==

* What SW is needed? What packages need to be installed? What versions?
* What HW is needed? What versions?
* How to get accurate measurement results?
* Step-by-step guide for checking that prerequisites are met
** HW version
** Installed packages
** Etc.

== Building packages ==

The build environment must have the following packages installed:

;* [[../BLTS Common Library | libbltscommon-devel]]

{{:Quality/TestSuite/Building_BLTS_Packages}}

== Running test cases ==

* Step-by-step instructions how to execute tests with an example
* Root or user privileges?
* What to do if something goes wrong?
** How to run in debug mode?
** What to look in log files?

== Test result analysis ==

* Where are the results?
* Log files?

== Troubleshooting ==

* What to do if something fails?
* What to check first?

== Configuration file examples ==

To run test case with variable data you need to specify where configuration file is located. You can edit the configuration file yourself.

To run "Core-Backlight linear backlight level changes" case you can use:

<code>$ blts-fbdev-tests -l /var/log/tests/Core-Backlight_linear_backlight_level_changes.log -en "Core-Backlight linear backlight level changes" -C /etc/blts/blts-fbdev-tests.cnf</code>

Example of a configuration file (blts-fbdev-tests.cnf):

<pre>
# Parameter configuration for blts-fbdev

# Valid framebuffer devices for HW.
[parameter]
name framebuffer_device
const "/dev/fb0"
[end_parameter]

# Valid backlight subsystem for HW
[parameter]
name backlight_subsystem
const "/sys/class/backlight/<enter_valid_sysfs_entry_here>"
[end_parameter]

# Minimum light level
[parameter]
name minimum_level
const 0
[end_parameter]

# Maximum light level
[parameter]
name maximum_level
const 255
[end_parameter]

# Minimum light level for logarithmic tests
[parameter]
name logarithmic_min
const 1
[end_parameter]

# Maximum light level for logarithmic tests
[parameter]
name logarithmic_max
const 255
[end_parameter]

# Test case configurations
[test]
name "Core-Framebuffer read frame buffer information with ioctl"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer set blanking levels"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer 1-pixel uncached read"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer 1-pixel uncached write"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer 1-pixel uncached modify"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer fullscreen buffer read"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer fullscreen buffer write"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer fullscreen buffer modify"
params framebuffer_device
[end_test]

[test]
name "Core-Backlight verify backlight levels"
params backlight_subsystem minimum_level maximum_level
[end_test]

[test]
name "Core-Backlight linear backlight level changes"
params backlight_subsystem minimum_level maximum_level
[end_test]

[test]
name "Core-Backlight logarithmic backlight level changes"
params backlight_subsystem logarithmic_min logarithmic_max
[end_test]
</pre>

Replace "/sys/class/backlight/<enter_valid_sysfs_entry_here>" with a valid path to the backlight system your device registers.

= Module Design and Architecture =

== Architecture ==

The test asset (blts-fbdev-tests) is built directly on top of the Linux kernel. Backlight tests use sysfs to test the functionality. The asset has been test to work with at least following Linux kernel versions: 2.6.28, 2.6.31 and 2.6.32.

= Known issues =
* The backlight cases take a lot of time. These cases try to go through all defined backlight levels. Might be better to define amount of steps or something similar into configuration.
* Check for open bugs: [http://bugs.meego.com/buglist.cgi?classification=MeeGo%20Projects&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&component=MeeGo%20Core%20Test%20Suite&product=MeeGo%20QA%20Test%20Suite MeeGo Core Test Suite Bugs]

= Future improvements =
The test driver should attemp to access the edges of the reported display area. Advanced improvements might include things like external camera use to determine whether the output from the test driver matches the actual on-screen results, aka test automation.

= References =
* [http://www.kernel.org Linux Kernel]
* [http://en.wikipedia.org/wiki/Framebuffer Framebuffer on Wikipedia]
* [http://www.linux-fbdev.org/ http://www.linux-fbdev.org]

Quality/TestSuite/Framebuffer Test Specification

2010-12-20T12:46:32Z

Mikan: /* Configuration file examples */

= Introduction =

== Overview ==

The framebuffer device is a device-independent interface for reading and writing raw data to the video memory. Uses of the device typically include things like text consoles, graphical boot progress indicators and so on. It is also possible to use the framebuffer device as a X11 window system display device.

The framebuffer device is typically used by memory-mapping the device file. The fbdev kernel driver translates any operations to the device-specific display driver. The blts-fbdev-tests asset tests the functionality and performance of this subsystem.

The display backlight driver registers a sysfs based directory upon device activation. This is how the blts-fbdev-tests asset uses the backlight system to change display brightness.

== Getting the Latest Version ==

Sources can be found in gitorius:
* http://gitorious.org/qa-tools/mcts/trees/master/mcts-blts/blts-fbdev

To clone a copy of the repository, see guides in:
* http://gitorious.org/qa-tools/mcts

Latest binary release is planned to be available via MeeGo OBS, see [[Build_Infrastructure|MeeGo Build Infrastructure]] for more information.

== Support & Contacts ==

* IRC: miniinis in #meego-qa-mcts on irc.freenode.org
* Maintainer: [mailto:mika.niinisto@digia.com Mika Niinisto]
* Substitute: [mailto:jussi.saavalainen@digia.com Jussi Saavalainen]
* Bugs should be reported to MeeGo Bugzilla:
** [http://bugs.meego.com/enter_bug.cgi?product=MeeGo%20QA%20Test%20Suite Enter a MeeGo QA Test Suite bug], select component MeeGo Core Test Suite
** [[Quality/How_To_Report_Bugs | How to report bugs]]

== Documentation ==

Check the package README file (essentially contains same info as this page):
* [http://gitorious.org/qa-tools/mcts/blobs/master/mcts-blts/blts-fbdev/README README]

== Licensing ==
* Please see the file called COPYING

== Supported Devices and SW ==

* List of supported (+ not supported devices, if needed for clarity)
** Versions
** Info about what is known to work

Supported
* N900
* nCDK Medfield (starting from version x.z)

Not supported
* Netbook

* Info about supported MeeGo releases (?)

== Test Cases ==

# Core-Framebuffer read frame buffer information with ioctl
#: Reads variant and fixed screen information from frame buffer device(s).
# Core-Framebuffer set blanking levels
#: Tests each of the blanking levels on all configured framebuffer devices.
# Core-Framebuffer 1-pixel uncached read
#: Performance test of reading visible framebuffer pixel by pixel. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured framebuffer devices.
# Core-Framebuffer 1-pixel uncached write
#: Performance test of writing into visible framebuffer pixel by pixel. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer device into the log and standard output. Done for all configured framebuffer devices.
# Core-Framebuffer 1-pixel uncached modify
#: Performance test of both reading and vriting into visible framebuffer pixel by pixel. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and and stadard output. Done for all configured framebuffer devices.
# Core-Framebuffer fullscreen buffer read
#: Performance test of reading a fullscreen framebuffer at once. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured devices.
# Core-Framebuffer fullscreen buffer write
#: Performance test of writing into a fullscreen framebuffer at once. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured devices.
# Core-Framebuffer fullscreen buffer modify
#: Performance test of both reading and writing into a fullscreen framebuffer at once. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured devices.
# Core-Backlight verify backlight levels
#: Verify backlight system's backlight level limits against configured limits. Tests the limit values, by using the actual limit and going one step over it.
# Core-Backlight linear backlight level changes
#: Linearly goes through all values between configured minimum and maximum values, by first going from min -> max and then from max -> min. NOTE: This case can timeout if the min and max are very big. The case sleeps for two seconds between each step.
# Core-Backlight logarithmic backlight level changes
#: Goes through all values between configured minimum and maximum values, by going from min -> max. The values are increased by following pattern: (max light / log10 (max light)) * log10 (between min and max). NOTE: This case can timeout if the min and max are very big. The case sleeps for two seconds between each step.

== Coverage ==

blts-fbdev-tests (0.0.8) is testing Linux kernel framebuffer ioctls and backlight subsystem via sysfs. The test driver accesses /dev/fbX directly with open(), close(), ioctl() and m(un)map(). Sysfs is accessed directly via fopen(), fprintf(), fscanf() and fclose().

Hardware coverage is device-dependent, but includes at least the data path diplay device - video memory - system memory.

Current framebuffer coverage matrix:

* [http://gitorious.org/qa-tools/mcts-coverage/blobs/master/Framebuffer-coverage.ods Framebuffer Coverage]

= Running the Tests =

== Hardware setup and test environment ==

* What SW is needed? What packages need to be installed? What versions?
* What HW is needed? What versions?
* How to get accurate measurement results?
* Step-by-step guide for checking that prerequisites are met
** HW version
** Installed packages
** Etc.

== Building packages ==

The build environment must have the following packages installed:

;* [[../BLTS Common Library | libbltscommon-devel]]

{{:Quality/TestSuite/Building_BLTS_Packages}}

== Running test cases ==

* Step-by-step instructions how to execute tests with an example
* Root or user privileges?
* What to do if something goes wrong?
** How to run in debug mode?
** What to look in log files?

== Test result analysis ==

* Where are the results?
* Log files?

== Troubleshooting ==

* What to do if something fails?
* What to check first?

== Configuration file examples ==

<pre>
# Parameter configuration for blts-fbdev

# Valid framebuffer devices for HW.
[parameter]
name framebuffer_device
const "/dev/fb0"
[end_parameter]

# Valid backlight subsystem for HW
[parameter]
name backlight_subsystem
const "/sys/class/backlight/<enter_valid_sysfs_entry_here>"
[end_parameter]

# Minimum light level
[parameter]
name minimum_level
const 0
[end_parameter]

# Maximum light level
[parameter]
name maximum_level
const 255
[end_parameter]

# Minimum light level for logarithmic tests
[parameter]
name logarithmic_min
const 1
[end_parameter]

# Maximum light level for logarithmic tests
[parameter]
name logarithmic_max
const 255
[end_parameter]

# Test case configurations
[test]
name "Core-Framebuffer read frame buffer information with ioctl"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer set blanking levels"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer 1-pixel uncached read"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer 1-pixel uncached write"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer 1-pixel uncached modify"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer fullscreen buffer read"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer fullscreen buffer write"
params framebuffer_device
[end_test]

[test]
name "Core-Framebuffer fullscreen buffer modify"
params framebuffer_device
[end_test]

[test]
name "Core-Backlight verify backlight levels"
params backlight_subsystem minimum_level maximum_level
[end_test]

[test]
name "Core-Backlight linear backlight level changes"
params backlight_subsystem minimum_level maximum_level
[end_test]

[test]
name "Core-Backlight logarithmic backlight level changes"
params backlight_subsystem logarithmic_min logarithmic_max
[end_test]
</pre>

= Module Design and Architecture =

== Architecture ==

The test asset (blts-fbdev-tests) is built directly on top of the Linux kernel. Backlight tests use sysfs to test the functionality. The asset has been test to work with at least following Linux kernel versions: 2.6.28, 2.6.31 and 2.6.32.

= Known issues =
* The backlight cases take a lot of time. These cases try to go through all defined backlight levels. Might be better to define amount of steps or something similar into configuration.
* Check for open bugs: [http://bugs.meego.com/buglist.cgi?classification=MeeGo%20Projects&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&component=MeeGo%20Core%20Test%20Suite&product=MeeGo%20QA%20Test%20Suite MeeGo Core Test Suite Bugs]

= Future improvements =
The test driver should attemp to access the edges of the reported display area. Advanced improvements might include things like external camera use to determine whether the output from the test driver matches the actual on-screen results, aka test automation.

= References =
* [http://www.kernel.org Linux Kernel]
* [http://en.wikipedia.org/wiki/Framebuffer Framebuffer on Wikipedia]
* [http://www.linux-fbdev.org/ http://www.linux-fbdev.org]

Quality/TestSuite/Framebuffer Test Specification

2010-12-20T08:44:05Z

Mikan: /* Future improvements */

Quality/TestSuite/Framebuffer Test Specification

2010-12-17T16:26:01Z

Mikan: /* Coverage */

Quality/TestSuite/Framebuffer Test Specification

2010-12-17T16:24:04Z

Mikan: /* Known issues */

Quality/TestSuite/Framebuffer Test Specification

2010-12-17T16:19:52Z

Mikan: /* Documentation */

Quality/TestSuite/Framebuffer Test Specification

2010-12-17T16:19:20Z

Mikan: /* Documentation */

Quality/TestSuite/Framebuffer Test Specification

2010-12-17T16:10:17Z

Mikan: /* Support & Contacts */

Quality/TestSuite/Framebuffer Test Specification

2010-12-17T16:05:03Z

Mikan: /* Test Cases */

Quality/TestSuite/Framebuffer Test Specification

2010-12-17T15:56:53Z

Mikan: /* Test Cases */

Quality/TestSuite/Framebuffer Test Specification

2010-12-17T15:48:21Z

Mikan: /* Support & Contacts */

Quality/TestSuite/Framebuffer Test Specification

2010-12-17T15:37:14Z

Mikan: /* Overview */

Quality/TestSuite/Framebuffer Test Specification

2010-12-17T14:49:49Z

Mikan: /* Getting the Latest Version */

Quality/TestSuite/Framebuffer Test Specification

2010-12-17T14:46:41Z

Mikan: /* Getting the Latest Version */

Quality/TestSuite/Framebuffer Test Specification

2010-12-17T14:34:38Z

Mikan: /* Architecture */

Quality/TestSuite/Framebuffer Test Specification

2010-12-17T14:29:31Z

Mikan: /* References */

Quality/TestSuite/Framebuffer Test Specification

2010-12-17T14:29:06Z

Mikan: /* References */

Quality/TestSuite/Framebuffer Test Specification

2010-12-17T14:06:44Z

Mikan: /* Overview */

Quality/TestSuite/Framebuffer Test Specification

2010-12-17T13:17:47Z

Mikan: /* Building packages */

= Introduction =

== Overview ==

* What is it? Background?
* What API is used? What version?
* What it test? What it doesn't test?
* Test types?
* Current status? Release? Under developement?

== Getting the Latest Version ==

* Link to gitorious
* Step-by-step guide how to obtain the sources for ...
** Latest release version (official)
** Latest development version

* Link to meego repo to rpm package

== Support & Contacts ==

* Where to get help? IRC, e-mail ...
* Maintainer name + e-mail + substitute name + e-mail
* If there are any specific instructions for reporting bugs for this specific test module, list them here (logs etc)
* Where to report bugs (what component etc)
** http://wiki.meego.com/Quality/How_To_Report_Bugs

== Documentation ==

<pre>
* Links to more documentation?
</pre>

== Licensing ==
* Please see the file called COPYING

== Supported Devices and SW ==

* List of supported (+ not supported devices, if needed for clarity)
** Versions
** Info about what is known to work

Supported
* N900
* nCDK Medfield (starting from version x.z)

Not supported
* Netbook

* Info about supported MeeGo releases (?)

== Test Cases ==

* List of / link to list of test cases (test case title + description etc)
** If the list is long put them on a separate page

== Coverage ==

blts-fbdev-tests (0.0.8) is testing Linux kernel framebuffer ioctls and backlight subsystem via sysfs.

Current framebuffer coverage matrix:

* [http://gitorious.org/qa-tools/mcts-coverage/blobs/master/Framebuffer-coverage.ods Framebuffer Coverage]

= Running the Tests =

== Hardware setup and test environment ==

* What SW is needed? What packages need to be installed? What versions?
* What HW is needed? What versions?
* How to get accurate measurement results?
* Step-by-step guide for checking that prerequisites are met
** HW version
** Installed packages
** Etc.

== Building packages ==

The build environment must have the following packages installed:

;* [[../BLTS Common Library | libbltscommon-devel]]

{{:Quality/TestSuite/Building_BLTS_Packages}}

== Running test cases ==

* Step-by-step instructions how to execute tests with an example
* Root or user privileges?
* What to do if something goes wrong?
** How to run in debug mode?
** What to look in log files?

== Test result analysis ==

* Where are the results?
* Log files?

== Troubleshooting ==

* What to do if something fails?
* What to check first?

== Configuration file examples ==
* Configuration file explained
* Example of configuration file

= Module Design and Architecture =

== Architecture ==

* What APIs are used? What API versions? E.g. Qt Mobility Messaging 1.0.1, link to API doc
* Architecture Diagrams
* Etc.

= Known issues =
* Link to open bugs on meego bugzilla
* Other known issues listed

= Future improvements =
* List of planned future improvements
* Later, link to backlog items to be done

= References =
* Links to API documentation
* Links to referred docs
* Etc.

Quality/TestSuite/Framebuffer Test Specification

2010-12-17T13:13:11Z

Mikan: /* Building packages */

= Introduction =

== Overview ==

* What is it? Background?
* What API is used? What version?
* What it test? What it doesn't test?
* Test types?
* Current status? Release? Under developement?

== Getting the Latest Version ==

* Link to gitorious
* Step-by-step guide how to obtain the sources for ...
** Latest release version (official)
** Latest development version

* Link to meego repo to rpm package

== Support & Contacts ==

* Where to get help? IRC, e-mail ...
* Maintainer name + e-mail + substitute name + e-mail
* If there are any specific instructions for reporting bugs for this specific test module, list them here (logs etc)
* Where to report bugs (what component etc)
** http://wiki.meego.com/Quality/How_To_Report_Bugs

== Documentation ==

<pre>
* Links to more documentation?
</pre>

== Licensing ==
* Please see the file called COPYING

== Supported Devices and SW ==

* List of supported (+ not supported devices, if needed for clarity)
** Versions
** Info about what is known to work

Supported
* N900
* nCDK Medfield (starting from version x.z)

Not supported
* Netbook

* Info about supported MeeGo releases (?)

== Test Cases ==

* List of / link to list of test cases (test case title + description etc)
** If the list is long put them on a separate page

== Coverage ==

blts-fbdev-tests (0.0.8) is testing Linux kernel framebuffer ioctls and backlight subsystem via sysfs.

Current framebuffer coverage matrix:

* [http://gitorious.org/qa-tools/mcts-coverage/blobs/master/Framebuffer-coverage.ods Framebuffer Coverage]

= Running the Tests =

== Hardware setup and test environment ==

* What SW is needed? What packages need to be installed? What versions?
* What HW is needed? What versions?
* How to get accurate measurement results?
* Step-by-step guide for checking that prerequisites are met
** HW version
** Installed packages
** Etc.

== Building packages ==
{{:Quality/TestSuite/Building_BLTS_Packages}}

== Running test cases ==

* Step-by-step instructions how to execute tests with an example
* Root or user privileges?
* What to do if something goes wrong?
** How to run in debug mode?
** What to look in log files?

== Test result analysis ==

* Where are the results?
* Log files?

== Troubleshooting ==

* What to do if something fails?
* What to check first?

== Configuration file examples ==
* Configuration file explained
* Example of configuration file

= Module Design and Architecture =

== Architecture ==

* What APIs are used? What API versions? E.g. Qt Mobility Messaging 1.0.1, link to API doc
* Architecture Diagrams
* Etc.

= Known issues =
* Link to open bugs on meego bugzilla
* Other known issues listed

= Future improvements =
* List of planned future improvements
* Later, link to backlog items to be done

= References =
* Links to API documentation
* Links to referred docs
* Etc.

Quality/TestSuite/Framebuffer Test Specification

2010-12-17T08:55:47Z

Mikan: /* Coverage */

= Introduction =

== Overview ==

* What is it? Background?
* What API is used? What version?
* What it test? What it doesn't test?
* Test types?
* Current status? Release? Under developement?

== Getting the Latest Version ==

* Link to gitorious
* Step-by-step guide how to obtain the sources for ...
** Latest release version (official)
** Latest development version

* Link to meego repo to rpm package

== Support & Contacts ==

* Where to get help? IRC, e-mail ...
* Maintainer name + e-mail + substitute name + e-mail
* If there are any specific instructions for reporting bugs for this specific test module, list them here (logs etc)
* Where to report bugs (what component etc)
** http://wiki.meego.com/Quality/How_To_Report_Bugs

== Documentation ==

<pre>
* Links to more documentation?
</pre>

== Licensing ==
* Please see the file called COPYING

== Supported Devices and SW ==

* List of supported (+ not supported devices, if needed for clarity)
** Versions
** Info about what is known to work

Supported
* N900
* nCDK Medfield (starting from version x.z)

Not supported
* Netbook

* Info about supported MeeGo releases (?)

== Test Cases ==

* List of / link to list of test cases (test case title + description etc)
** If the list is long put them on a separate page

== Coverage ==

blts-fbdev-tests (0.0.8) is testing Linux kernel framebuffer ioctls and backlight subsystem via sysfs.

Current framebuffer coverage matrix:

* [http://gitorious.org/qa-tools/mcts-coverage/blobs/master/Framebuffer-coverage.ods Framebuffer Coverage]

= Running the Tests =

== Hardware setup and test environment ==

* What SW is needed? What packages need to be installed? What versions?
* What HW is needed? What versions?
* How to get accurate measurement results?
* Step-by-step guide for checking that prerequisites are met
** HW version
** Installed packages
** Etc.

== Building packages ==
* How to build package from source code
** using build script
** Manually (if needed)
* How to install package from repo? rpm -i ...

== Running test cases ==

* Step-by-step instructions how to execute tests with an example
* Root or user privileges?
* What to do if something goes wrong?
** How to run in debug mode?
** What to look in log files?

== Test result analysis ==

* Where are the results?
* Log files?

== Troubleshooting ==

* What to do if something fails?
* What to check first?

== Configuration file examples ==
* Configuration file explained
* Example of configuration file

= Module Design and Architecture =

== Architecture ==

* What APIs are used? What API versions? E.g. Qt Mobility Messaging 1.0.1, link to API doc
* Architecture Diagrams
* Etc.

= Known issues =
* Link to open bugs on meego bugzilla
* Other known issues listed

= Future improvements =
* List of planned future improvements
* Later, link to backlog items to be done

= References =
* Links to API documentation
* Links to referred docs
* Etc.

Quality/TestSuite/Framebuffer Test Specification

2010-12-17T08:54:31Z

Mikan: /* Coverage */

= Introduction =

== Overview ==

* What is it? Background?
* What API is used? What version?
* What it test? What it doesn't test?
* Test types?
* Current status? Release? Under developement?

== Getting the Latest Version ==

* Link to gitorious
* Step-by-step guide how to obtain the sources for ...
** Latest release version (official)
** Latest development version

* Link to meego repo to rpm package

== Support & Contacts ==

* Where to get help? IRC, e-mail ...
* Maintainer name + e-mail + substitute name + e-mail
* If there are any specific instructions for reporting bugs for this specific test module, list them here (logs etc)
* Where to report bugs (what component etc)
** http://wiki.meego.com/Quality/How_To_Report_Bugs

== Documentation ==

<pre>
* Links to more documentation?
</pre>

== Licensing ==
* Please see the file called COPYING

== Supported Devices and SW ==

* List of supported (+ not supported devices, if needed for clarity)
** Versions
** Info about what is known to work

Supported
* N900
* nCDK Medfield (starting from version x.z)

Not supported
* Netbook

* Info about supported MeeGo releases (?)

== Test Cases ==

* List of / link to list of test cases (test case title + description etc)
** If the list is long put them on a separate page

== Coverage ==

blts-fbdev-tests (0.0.8) is testing Linux kernel framebuffer ioctls and backlight subsystem via sysfs.

[http://gitorious.org/qa-tools/mcts-coverage/blobs/master/Framebuffer-coverage.ods Framebuffer Coverage]

= Running the Tests =

== Hardware setup and test environment ==

* What SW is needed? What packages need to be installed? What versions?
* What HW is needed? What versions?
* How to get accurate measurement results?
* Step-by-step guide for checking that prerequisites are met
** HW version
** Installed packages
** Etc.

== Building packages ==
* How to build package from source code
** using build script
** Manually (if needed)
* How to install package from repo? rpm -i ...

== Running test cases ==

* Step-by-step instructions how to execute tests with an example
* Root or user privileges?
* What to do if something goes wrong?
** How to run in debug mode?
** What to look in log files?

== Test result analysis ==

* Where are the results?
* Log files?

== Troubleshooting ==

* What to do if something fails?
* What to check first?

== Configuration file examples ==
* Configuration file explained
* Example of configuration file

= Module Design and Architecture =

== Architecture ==

* What APIs are used? What API versions? E.g. Qt Mobility Messaging 1.0.1, link to API doc
* Architecture Diagrams
* Etc.

= Known issues =
* Link to open bugs on meego bugzilla
* Other known issues listed

= Future improvements =
* List of planned future improvements
* Later, link to backlog items to be done

= References =
* Links to API documentation
* Links to referred docs
* Etc.

Quality/TestSuite/Framebuffer Test Specification

2010-12-17T08:52:10Z

Mikan: /* Coverage */

= Introduction =

== Overview ==

* What is it? Background?
* What API is used? What version?
* What it test? What it doesn't test?
* Test types?
* Current status? Release? Under developement?

== Getting the Latest Version ==

* Link to gitorious
* Step-by-step guide how to obtain the sources for ...
** Latest release version (official)
** Latest development version

* Link to meego repo to rpm package

== Support & Contacts ==

* Where to get help? IRC, e-mail ...
* Maintainer name + e-mail + substitute name + e-mail
* If there are any specific instructions for reporting bugs for this specific test module, list them here (logs etc)
* Where to report bugs (what component etc)
** http://wiki.meego.com/Quality/How_To_Report_Bugs

== Documentation ==

<pre>
* Links to more documentation?
</pre>

== Licensing ==
* Please see the file called COPYING

== Supported Devices and SW ==

* List of supported (+ not supported devices, if needed for clarity)
** Versions
** Info about what is known to work

Supported
* N900
* nCDK Medfield (starting from version x.z)

Not supported
* Netbook

* Info about supported MeeGo releases (?)

== Test Cases ==

* List of / link to list of test cases (test case title + description etc)
** If the list is long put them on a separate page

== Coverage ==

[http://gitorious.org/qa-tools/mcts-coverage/blobs/master/Framebuffer-coverage.ods Framebuffer Coverage]

= Running the Tests =

== Hardware setup and test environment ==

* What SW is needed? What packages need to be installed? What versions?
* What HW is needed? What versions?
* How to get accurate measurement results?
* Step-by-step guide for checking that prerequisites are met
** HW version
** Installed packages
** Etc.

== Building packages ==
* How to build package from source code
** using build script
** Manually (if needed)
* How to install package from repo? rpm -i ...

== Running test cases ==

* Step-by-step instructions how to execute tests with an example
* Root or user privileges?
* What to do if something goes wrong?
** How to run in debug mode?
** What to look in log files?

== Test result analysis ==

* Where are the results?
* Log files?

== Troubleshooting ==

* What to do if something fails?
* What to check first?

== Configuration file examples ==
* Configuration file explained
* Example of configuration file

= Module Design and Architecture =

== Architecture ==

* What APIs are used? What API versions? E.g. Qt Mobility Messaging 1.0.1, link to API doc
* Architecture Diagrams
* Etc.

= Known issues =
* Link to open bugs on meego bugzilla
* Other known issues listed

= Future improvements =
* List of planned future improvements
* Later, link to backlog items to be done

= References =
* Links to API documentation
* Links to referred docs
* Etc.

Quality/TestSuite/Framebuffer Test Specification

2010-12-16T16:37:01Z

Mikan:

= Introduction =

== Overview ==

* What is it? Background?
* What API is used? What version?
* What it test? What it doesn't test?
* Test types?
* Current status? Release? Under developement?

== Getting the Latest Version ==

* Link to gitorious
* Step-by-step guide how to obtain the sources for ...
** Latest release version (official)
** Latest development version

* Link to meego repo to rpm package

== Support & Contacts ==

* Where to get help? IRC, e-mail ...
* Maintainer name + e-mail + substitute name + e-mail
* If there are any specific instructions for reporting bugs for this specific test module, list them here (logs etc)
* Where to report bugs (what component etc)
** http://wiki.meego.com/Quality/How_To_Report_Bugs

== Documentation ==

<pre>
* Links to more documentation?
</pre>

== Licensing ==
* Please see the file called COPYING

== Supported Devices and SW ==

* List of supported (+ not supported devices, if needed for clarity)
** Versions
** Info about what is known to work

Supported
* N900
* nCDK Medfield (starting from version x.z)

Not supported
* Netbook

* Info about supported MeeGo releases (?)

== Test Cases ==

* List of / link to list of test cases (test case title + description etc)
** If the list is long put them on a separate page

== Coverage ==

* Coverage target
* Textual coverage description
* Link to coverage sheet
* Coverage table (e.g. test types)
* Limitations, what is not covered

= Running the Tests =

== Hardware setup and test environment ==

* What SW is needed? What packages need to be installed? What versions?
* What HW is needed? What versions?
* How to get accurate measurement results?
* Step-by-step guide for checking that prerequisites are met
** HW version
** Installed packages
** Etc.

== Building packages ==
* How to build package from source code
** using build script
** Manually (if needed)
* How to install package from repo? rpm -i ...

== Running test cases ==

* Step-by-step instructions how to execute tests with an example
* Root or user privileges?
* What to do if something goes wrong?
** How to run in debug mode?
** What to look in log files?

== Test result analysis ==

* Where are the results?
* Log files?

== Troubleshooting ==

* What to do if something fails?
* What to check first?

== Configuration file examples ==
* Configuration file explained
* Example of configuration file

= Module Design and Architecture =

== Architecture ==

* What APIs are used? What API versions? E.g. Qt Mobility Messaging 1.0.1, link to API doc
* Architecture Diagrams
* Etc.

= Known issues =
* Link to open bugs on meego bugzilla
* Other known issues listed

= Future improvements =
* List of planned future improvements
* Later, link to backlog items to be done

= References =
* Links to API documentation
* Links to referred docs
* Etc.

Quality/TestSuite/MCTS

2010-12-16T16:35:45Z

Mikan: /* Test Suite Status For OS Base */

== MeeGo Core Test Suite (MCTS)==
=== Overview ===

* MCTS Development Guideline [[/MCTS_Development_Guideline | MCTS Development Guideline]] 
* Discussion about [[/MCTS_API_analysis | API analysis]] for MCTS functional test design
* Interested in contributing to MCTS ? Look at [[/MCTS_Start_Contributing | How to start contributing]]

=== Test Suite Code & API Coverage Analysis Repositories ===
You can get the code here: http://gitorious.org/qa-tools/mcts 
You can get the coverage analysis documents here: http://gitorious.org/qa-tools/mcts-coverage

=== MCTS Releases ===
MCTS is released typically in a biweekly cycle. The release process
is described in [[/MCTS_Release_Process | MCTS Release Process.]]

You can find information about the completed and planned MCTS releases from [[/MCTS_Releases | MCTS Releases.]]

=== Test Suite Status For Middleware (New) ===

{| cellspacing="0" border="1"
|-
!| '''Domain'''
!| '''Component'''
!| [http://wiki.meego.com/Quality/Plans/MeeGo_Core_Test_Plan Test Coverage]
!| '''% Ready'''
!| '''Auto %'''
!| [http://gitorious.org/qa-tools/mcts MCTS package]
!| '''Maintainer'''
!| '''Target Due'''
|-
| rowspan = "6" | Security

| Accounts || || || || WIP || ||

|-
| Single Sign-On || || || || WIP || ||

|-
| Integrity Protection Framework || || || || WIP || ||

|-
| Certificate Manager || || || || WIP || ||

|-
| SW Distribution Security || || || || WIP || ||

|-
| Access Control Framework || || || || WIP || ||

|-
| rowspan = "4" | System

| System Control || || || || WIP || ||

|-
| Resource Policy || Average || || || WIP || ||

|-
| Context Framework || Through || || || WIP || ||

|-
| Sensor Framework || Average || || || mcts-blts-sensor-frontend mcts-blts-sensor-plugins || ||

|-
| Location
| [[../GeoClue Test Plan | Location Framework]] || light ||100% ||100% || mcts-geoclue-tests || [mailto:shaofeng.tang@intel.com Shaofeng Tang] ||

|-
| rowspan = "5" | PIM

| Calendar Engine || Average || || || WIP || ||

|-
| Contacts Engine || Average || || || WIP || ||

|-
| Email Engine || Average || || || WIP || ||

|-
| Backup Framework || Average || || || WIP || ||

|-
| Synchronization Framework || Average || || || WIP || ||

|-
| rowspan = "3" | Multimedia

| Gstreamer || light || || || mcts-mwts-gstreamer mcts-mwts-gcamera || ||

|-
| PulseAudio || light ||100% ||100% || mcts-pulseaudio-tests mcts-blts-alsa-core || [mailto:hao.h.chen@intel.com Hao Chen] || Dec. 17 for test plan

|-
| UPnP || light ||100% ||0% || mcts-gupnp-tests || [mailto:daniel.tao@intel.com Daniel Tao] ||

|-
| rowspan = "4"| Communications
| Telephony & IM || light || || || mcts-mwts-telepathy || ||

|-
| [[/OFono Test Plan |Cellular Framework]] || Through ||100% ||36% || mcts-ofono-tests mcts-blts-ofono || [mailto:elva.fu@intel.com Elva Fu]||

|-
| [[/ConnMan Test Plan | ConnMan]] || Through ||100% ||43% || mcts-connman-tests || [mailto:jeff.zheng@intel.com Jeff Zheng] ||

|-
| [[/MeeGo Bluez Test Plan |Bluetooth]] || Average ||100% ||16% || mcts-bluez-tests mcts-blts-bluetooth || [mailto:jingke.zhang@intel.com Jingke] ||

|-
| rowspan = "3" | Qt
| Qt || || || || mcts-mwts-network mcts-mwts-telepathy || ||

|-
| Qt WebKit || || || || N/A || ||

|-
| Qt Web Runtime || || || || N/A || ||

|-
| rowspan = "9" | Qt Mobility
| QtM contacts || || || || WIP || ||

|-
| QtM Location || || || || mcts-mwts-location || ||

|-
| QtM Messaging || || || || mcts-mwts-messaging || ||

|-
| QtM Publish & Subscribe || || || || WIP || ||

|-
| QtM Sensors || || || || mcts-mwts-sensors || ||

|-
| QtM Service Framework || || || || WIP || ||

|-
| QtM Versit || || || || WIP || ||

|-
| QtM Multimedia || || || || mcts-mwts-multimedia || ||

|-
| QtM System Info || || || || WIP || ||

|-
| rowspan = "3" | [[../MeeGo_Graphics_Test_Plan | Graphics]]
| OpenGL ES || Average ||100% ||13% || mcts-qtgfx-tests mcts-blts-openles2-perf || [mailto:kui.zheng@intel.com Kui Zheng] ||

|-
| Font Management || || || || N/A || ||

|-
| X11 || Light ||100% ||100% || mcts-x-tests mcts-rendercheck-tests mcts-blts-fbdev || [mailto:kui.zheng@intel.com Kui Zheng] ||

|-
| Data Management || Content Framework || Through || || || mcts-tracker-tests || ||

|-
| SW Management
| Package Manager || light || || || mcts-packagekit-tests || [mailto:huajun.li@intel.com Huajun Li] || Dec. 17 for test plan

|-
| Kernel

| Linux Kernel || || || || mcts-blts-usb mcts-blts-input-devices mcts-mwts-filesystem || ||

|}

=== Released Middleware Test Asset Descriptions ===
[[../MWTS Asset Descriptions | Released Middleware Test Asset Descriptions]]

=== Test Suite Status For OS Base===
{|cellspacing="0" border="1"
!|Category
!|Component
!|Test Coverage
!|Planned #
!|Ready #
!|Auto %
!|Major Contacts
!|Due

|-
| rowspan = "17" | OS Base|| [[../Audio Driver Test Specification | Audio Driver]] || '''Light''' ||31||31||0% || [mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen]||tbd

|-
| [[../Bluetooth Driver Test Specification | Bluetooth Driver]] || '''Light''' || 23 || 23 || 0% ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen]||tbd

|-
| [[../Camera Driver Test Specification | Camera Driver]] || '''Light''' || 12 || 12 || 0% ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen]||tbd

|-
| [[../Functional Key Driver Test Plan | Functional Key Driver]] || '''Open''' || tbd || || || || tbd

|-
| [[../Framebuffer Test Specification | Framebuffer Driver]] || '''Light''' || 22 || 11 || 0% || [mailto:mika.niinisto@digia.com Mika Niinistö] ||tbd

|-
| [[../GPS Driver Test Plan | GPS Driver]] || '''Light''' || || || ||Jussi Saavalainen||tbd

|-
| [[../Input Devices Driver Test Specification | Input Devices Driver]] || '''Light''' || 3 || 3 || 0% || ||tbd

|-
| [[../oFono Modem API Test Specification | Modem Devices Driver]] || '''Light''' || N/A || N/A || N/A || ||tbd

|-
| [[../SD-MMC Driver Test Plan | SD/MMC Driver]] || '''Light''' || 33 || 33 || 0% ||Jussi Saavalainen ||Sep.3.2010

|-
| [[../Sensor Test Front-end | Sensor Driver]] || '''N/A''' || N/A || N/A || N/A || Pasi Matilainen ||tbd

|-
| [[../Touch Screen Driver Test Plan | Touch Screen Driver]] || '''Light''' || || || || Juhani Taipale||tbd

|-
| [[../Touchpad Driver Test Plan | Touchpad Driver]] || '''Open''' || tbd || || || ||tbd

|-
| [[../USB Driver Test Specification | USB Driver]] || '''Light''' || 35 || 35 || 0% ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen] ||tbd

|-
| [[../Video Playback Driver Test Specification | Video Playback Driver]] || '''Average''' || 6 || 6 || 0% ||[mailto:kimmo.myllyvirta@digia.com Kimmo Myllyvirta] ||tbd

|-
| [[../Watchdog Driver Test Specification | Watchdog Driver]] || '''Average''' || 3 || 3 || 0% || [mailto:kimmo.myllyvirta@digia.com Kimmo Myllyvirta] ||tbd

|-
| [[../WIFI Driver Test Specification | WIFI Driver]] || '''Light''' || 10 || 10 || 0% ||Jussi Saavalainen ||tbd

|-
| [[../X11 Test Specification | X11]] || '''Light''' || 11 || 11 || 0% || [mailto:kimmo.myllyvirta@digia.com Kimmo Myllyvirta] ||tbd
|}

Quality/TestSuite/Framebuffer Test Specification

2010-12-16T16:34:51Z

Mikan: Copied template to create the page

= Introduction =

== Overview ==

* What is it? Background?
* What API is used? What version?
* What it test? What it doesn't test?
* Test types?
* Current status? Release? Under developement?

== Getting the Latest Version ==

* Link to gitorious
* Step-by-step guide how to obtain the sources for ...
** Latest release version (official)
** Latest development version

* Link to meego repo to rpm package

== Support & Contacts ==

* Where to get help? IRC, e-mail ...
* Maintainer name + e-mail + substitute name + e-mail
* If there are any specific instructions for reporting bugs for this specific test module, list them here (logs etc)
* Where to report bugs (what component etc)
** http://wiki.meego.com/Quality/How_To_Report_Bugs

== Documentation ==

<pre>
* Links to more documentation?
</pre>

== Licensing ==
* Please see the file called COPYING

== Supported Devices and SW ==

* List of supported (+ not supported devices, if needed for clarity)
** Versions
** Info about what is known to work

Supported
* N900
* nCDK Medfield (starting from version x.z)

Not supported
* Netbook

* Info about supported MeeGo releases (?)

== Test Cases ==

* List of / link to list of test cases (test case title + description etc)
** If the list is long put them on a separate page

== Coverage ==

* Coverage target
* Textual coverage description
* Link to coverage sheet
* Coverage table (e.g. test types)
* Limitations, what is not covered

= Running the Tests =

== Hardware setup and test environment ==

* What SW is needed? What packages need to be installed? What versions?
* What HW is needed? What versions?
* How to get accurate measurement results?
* Step-by-step guide for checking that prerequisites are met
** HW version
** Installed packages
** Etc.

== Building packages ==
* How to build package from source code
** using build script
** Manually (if needed)
* How to install package from repo? rpm -i ...

== Running test cases ==

* Step-by-step instructions how to execute tests with an example
* Root or user privileges?
* What to do if something goes wrong?
** How to run in debug mode?
** What to look in log files?

== Test result analysis ==

* Where are the results?
* Log files?

== Troubleshooting ==

* What to do if something fails?
* What to check first?

== Configuration file examples ==
* Configuration file explained
* Example of configuration file

= Module Design and Architecture =

== Architecture ==

* What APIs are used? What API versions? E.g. Qt Mobility Messaging 1.0.1, link to API doc
* Architecture Diagrams
* Etc.

== MIN Scripter Interface ==
* Table of MIN scripter interfaces with parameters and descriptions

= Known issues =
* Link to open bugs on meego bugzilla
* Other known issues listed

= Future improvements =
* List of planned future improvements
* Later, link to backlog items to be done

= References =
* Links to API documentation
* Links to referred docs
* Etc.

Quality/TestSuite/MCTS

2010-12-16T12:22:27Z

Mikan: /* Test Suite Status For OS Base */

== MeeGo Core Test Suite (MCTS)==
=== Overview ===

* MCTS Development Guideline [[/MCTS_Development_Guideline | MCTS Development Guideline]] 
* Discussion about [[/MCTS_API_analysis | API analysis]] for MCTS functional test design
* Interested in contributing to MCTS ? Look at [[/MCTS_Start_Contributing | How to start contributing]]

=== Test Suite Code & API Coverage Analysis Repositories ===
You can get the code here: http://gitorious.org/qa-tools/mcts 
You can get the coverage analysis documents here: http://gitorious.org/qa-tools/mcts-coverage

=== MCTS Releases ===
MCTS is released typically in a biweekly cycle. The release process
is described in [[/MCTS_Release_Process | MCTS Release Process.]]

You can find information about the completed and planned MCTS releases from [[/MCTS_Releases | MCTS Releases.]]

=== Test Suite Status For Middleware (New) ===

{| cellspacing="0" border="1"
|-
!| '''Domain'''
!| '''Component'''
!| [http://wiki.meego.com/Quality/Plans/MeeGo_Core_Test_Plan Test Coverage]
!| '''% Ready'''
!| '''Auto %'''
!| [http://gitorious.org/qa-tools/mcts MCTS package]
!| '''Maintainer'''
!| '''Target Due'''
|-
| rowspan = "6" | Security

| Accounts || || || || WIP || ||

|-
| Single Sign-On || || || || WIP || ||

|-
| Integrity Protection Framework || || || || WIP || ||

|-
| Certificate Manager || || || || WIP || ||

|-
| SW Distribution Security || || || || WIP || ||

|-
| Access Control Framework || || || || WIP || ||

|-
| rowspan = "4" | System

| System Control || || || || WIP || ||

|-
| Resource Policy || Average || || || WIP || ||

|-
| Context Framework || Through || || || WIP || ||

|-
| Sensor Framework || Average || || || mcts-blts-sensor-frontend mcts-blts-sensor-plugins || ||

|-
| Location
| [[../GeoClue Test Plan | Location Framework]] || light ||100% ||100% || mcts-geoclue-tests || [mailto:shaofeng.tang@intel.com Shaofeng Tang] ||

|-
| rowspan = "5" | PIM

| Calendar Engine || Average || || || WIP || ||

|-
| Contacts Engine || Average || || || WIP || ||

|-
| Email Engine || Average || || || WIP || ||

|-
| Backup Framework || Average || || || WIP || ||

|-
| Synchronization Framework || Average || || || WIP || ||

|-
| rowspan = "3" | Multimedia

| Gstreamer || light || || || mcts-mwts-gstreamer mcts-mwts-gcamera || ||

|-
| PulseAudio || light ||100% ||100% || mcts-pulseaudio-tests mcts-blts-alsa-core || [mailto:hao.h.chen@intel.com Hao Chen] || Dec. 17 for test plan

|-
| UPnP || light ||100% ||0% || mcts-gupnp-tests || [mailto:daniel.tao@intel.com Daniel Tao] ||

|-
| rowspan = "4"| Communications
| Telephony & IM || light || || || mcts-mwts-telepathy || ||

|-
| [[/OFono Test Plan |Cellular Framework]] || Through ||100% ||36% || mcts-ofono-tests mcts-blts-ofono || [mailto:elva.fu@intel.com Elva Fu]||

|-
| [[/ConnMan Test Plan | ConnMan]] || Through ||100% ||43% || mcts-connman-tests || [mailto:jeff.zheng@intel.com Jeff Zheng] ||

|-
| [[/MeeGo Bluez Test Plan |Bluetooth]] || Average ||100% ||16% || mcts-bluez-tests mcts-blts-bluetooth || [mailto:jingke.zhang@intel.com Jingke] ||

|-
| rowspan = "3" | Qt
| Qt || || || || mcts-mwts-network mcts-mwts-telepathy || ||

|-
| Qt WebKit || || || || N/A || ||

|-
| Qt Web Runtime || || || || N/A || ||

|-
| rowspan = "9" | Qt Mobility
| QtM contacts || || || || WIP || ||

|-
| QtM Location || || || || mcts-mwts-location || ||

|-
| QtM Messaging || || || || mcts-mwts-messaging || ||

|-
| QtM Publish & Subscribe || || || || WIP || ||

|-
| QtM Sensors || || || || mcts-mwts-sensors || ||

|-
| QtM Service Framework || || || || WIP || ||

|-
| QtM Versit || || || || WIP || ||

|-
| QtM Multimedia || || || || mcts-mwts-multimedia || ||

|-
| QtM System Info || || || || WIP || ||

|-
| rowspan = "3" | [[../MeeGo_Graphics_Test_Plan | Graphics]]
| OpenGL ES || Average ||100% ||13% || mcts-qtgfx-tests mcts-blts-openles2-perf || [mailto:kui.zheng@intel.com Kui Zheng] ||

|-
| Font Management || || || || N/A || ||

|-
| X11 || Light ||100% ||100% || mcts-x-tests mcts-rendercheck-tests mcts-blts-fbdev || [mailto:kui.zheng@intel.com Kui Zheng] ||

|-
| Data Management || Content Framework || Through || || || mcts-tracker-tests || ||

|-
| SW Management
| Package Manager || light || || || mcts-packagekit-tests || [mailto:huajun.li@intel.com Huajun Li] || Dec. 17 for test plan

|-
| Kernel

| Linux Kernel || || || || mcts-blts-usb mcts-blts-input-devices mcts-mwts-filesystem || ||

|}

=== Released Middleware Test Asset Descriptions ===
[[../MWTS Asset Descriptions | Released Middleware Test Asset Descriptions]]

=== Test Suite Status For OS Base===
{|cellspacing="0" border="1"
!|Category
!|Component
!|Test Coverage
!|Planned #
!|Ready #
!|Auto %
!|Major Contacts
!|Due

|-
| rowspan = "16" | OS Base|| [[../Audio Driver Test Specification | Audio Driver]] || '''Light''' ||31||31||0% || [mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen]||tbd

|-
| [[../Bluetooth Driver Test Specification | Bluetooth Driver]] || '''Light''' || 23 || 23 || 0% ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen]||tbd

|-
| [[../Camera Driver Test Specification | Camera Driver]] || '''Light''' || 12 || 12 || 0% ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen]||tbd

|-
| [[../Functional Key Driver Test Plan | Functional Key Driver]] || '''Open''' || tbd || || || || tbd

|-
| [[../GPS Driver Test Plan | GPS Driver]] || '''Light''' || || || ||Jussi Saavalainen||tbd

|-
| [[../Input Devices Driver Test Specification | Input Devices Driver]] || '''Light''' || 3 || 3 || 0% || ||tbd

|-
| [[../SD-MMC Driver Test Plan | SD/MMC Driver]] || '''Light''' || 33 || 33 || 0% ||Jussi Saavalainen ||Sep.3.2010

|-
| [[../Sensor Driver Test Plan | Sensor Driver]] || '''Light''' || 8 || 8 || 0% ||Jussi Saavalainen ||tbd

|-
| [[../Touch Screen Driver Test Plan | Touch Screen Driver]] || '''Light''' || || || || Juhani Taipale||tbd

|-
| [[../Touchpad Driver Test Plan | Touchpad Driver]] || '''Open''' || tbd || || || ||tbd

|-
| [[../USB Driver Test Specification | USB Driver]] || '''Light''' || 35 || 35 || 0% ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen] ||tbd

|-
| [[../Video Playback Driver Test Specification | Video Playback Driver]] || '''Average''' || 6 || 6 || 0% ||[mailto:kimmo.myllyvirta@digia.com Kimmo Myllyvirta] ||tbd

|-
| [[../Watchdog Driver Test Specification | Watchdog Driver]] || '''Average''' || 3 || 3 || 0% || [mailto:kimmo.myllyvirta@digia.com Kimmo Myllyvirta] ||tbd

|-
| [[../WIFI Driver Test Specification | WIFI Driver]] || '''Light''' || 10 || 10 || 0% ||Jussi Saavalainen ||tbd

|-
| [[../X11 Test Specification | X11]] || '''Light''' || 11 || 11 || 0% || [mailto:kimmo.myllyvirta@digia.com Kimmo Myllyvirta] ||tbd

|-
| [[../Framebuffer Test Specification | Framebuffer Driver]] || '''Light''' || 22 || 11 || 0% || [mailto:mika.niinisto@digia.com Mika Niinistö] ||tbd
|}

Quality/TestSuite/MCTS

2010-12-16T12:19:58Z

Mikan: /* Test Suite Status For OS Base */

== MeeGo Core Test Suite (MCTS)==
=== Overview ===

* MCTS Development Guideline [[/MCTS_Development_Guideline | MCTS Development Guideline]] 
* Discussion about [[/MCTS_API_analysis | API analysis]] for MCTS functional test design
* Interested in contributing to MCTS ? Look at [[/MCTS_Start_Contributing | How to start contributing]]

=== Test Suite Code & API Coverage Analysis Repositories ===
You can get the code here: http://gitorious.org/qa-tools/mcts 
You can get the coverage analysis documents here: http://gitorious.org/qa-tools/mcts-coverage

=== MCTS Releases ===
MCTS is released typically in a biweekly cycle. The release process
is described in [[/MCTS_Release_Process | MCTS Release Process.]]

You can find information about the completed and planned MCTS releases from [[/MCTS_Releases | MCTS Releases.]]

=== Test Suite Status For Middleware (New) ===

{| cellspacing="0" border="1"
|-
!| '''Domain'''
!| '''Component'''
!| [http://wiki.meego.com/Quality/Plans/MeeGo_Core_Test_Plan Test Coverage]
!| '''% Ready'''
!| '''Auto %'''
!| [http://gitorious.org/qa-tools/mcts MCTS package]
!| '''Maintainer'''
!| '''Target Due'''
|-
| rowspan = "6" | Security

| Accounts || || || || WIP || ||

|-
| Single Sign-On || || || || WIP || ||

|-
| Integrity Protection Framework || || || || WIP || ||

|-
| Certificate Manager || || || || WIP || ||

|-
| SW Distribution Security || || || || WIP || ||

|-
| Access Control Framework || || || || WIP || ||

|-
| rowspan = "4" | System

| System Control || || || || WIP || ||

|-
| Resource Policy || Average || || || WIP || ||

|-
| Context Framework || Through || || || WIP || ||

|-
| Sensor Framework || Average || || || mcts-blts-sensor-frontend mcts-blts-sensor-plugins || ||

|-
| Location
| [[../GeoClue Test Plan | Location Framework]] || light ||100% ||100% || mcts-geoclue-tests || [mailto:shaofeng.tang@intel.com Shaofeng Tang] ||

|-
| rowspan = "5" | PIM

| Calendar Engine || Average || || || WIP || ||

|-
| Contacts Engine || Average || || || WIP || ||

|-
| Email Engine || Average || || || WIP || ||

|-
| Backup Framework || Average || || || WIP || ||

|-
| Synchronization Framework || Average || || || WIP || ||

|-
| rowspan = "3" | Multimedia

| Gstreamer || light || || || mcts-mwts-gstreamer mcts-mwts-gcamera || ||

|-
| PulseAudio || light ||100% ||100% || mcts-pulseaudio-tests mcts-blts-alsa-core || [mailto:hao.h.chen@intel.com Hao Chen] || Dec. 17 for test plan

|-
| UPnP || light ||100% ||0% || mcts-gupnp-tests || [mailto:daniel.tao@intel.com Daniel Tao] ||

|-
| rowspan = "4"| Communications
| Telephony & IM || light || || || mcts-mwts-telepathy || ||

|-
| [[/OFono Test Plan |Cellular Framework]] || Through ||100% ||36% || mcts-ofono-tests mcts-blts-ofono || [mailto:elva.fu@intel.com Elva Fu]||

|-
| [[/ConnMan Test Plan | ConnMan]] || Through ||100% ||43% || mcts-connman-tests || [mailto:jeff.zheng@intel.com Jeff Zheng] ||

|-
| [[/MeeGo Bluez Test Plan |Bluetooth]] || Average ||100% ||16% || mcts-bluez-tests mcts-blts-bluetooth || [mailto:jingke.zhang@intel.com Jingke] ||

|-
| rowspan = "3" | Qt
| Qt || || || || mcts-mwts-network mcts-mwts-telepathy || ||

|-
| Qt WebKit || || || || N/A || ||

|-
| Qt Web Runtime || || || || N/A || ||

|-
| rowspan = "9" | Qt Mobility
| QtM contacts || || || || WIP || ||

|-
| QtM Location || || || || mcts-mwts-location || ||

|-
| QtM Messaging || || || || mcts-mwts-messaging || ||

|-
| QtM Publish & Subscribe || || || || WIP || ||

|-
| QtM Sensors || || || || mcts-mwts-sensors || ||

|-
| QtM Service Framework || || || || WIP || ||

|-
| QtM Versit || || || || WIP || ||

|-
| QtM Multimedia || || || || mcts-mwts-multimedia || ||

|-
| QtM System Info || || || || WIP || ||

|-
| rowspan = "3" | [[../MeeGo_Graphics_Test_Plan | Graphics]]
| OpenGL ES || Average ||100% ||13% || mcts-qtgfx-tests mcts-blts-openles2-perf || [mailto:kui.zheng@intel.com Kui Zheng] ||

|-
| Font Management || || || || N/A || ||

|-
| X11 || Light ||100% ||100% || mcts-x-tests mcts-rendercheck-tests mcts-blts-fbdev || [mailto:kui.zheng@intel.com Kui Zheng] ||

|-
| Data Management || Content Framework || Through || || || mcts-tracker-tests || ||

|-
| SW Management
| Package Manager || light || || || mcts-packagekit-tests || [mailto:huajun.li@intel.com Huajun Li] || Dec. 17 for test plan

|-
| Kernel

| Linux Kernel || || || || mcts-blts-usb mcts-blts-input-devices mcts-mwts-filesystem || ||

|}

=== Released Middleware Test Asset Descriptions ===
[[../MWTS Asset Descriptions | Released Middleware Test Asset Descriptions]]

=== Test Suite Status For OS Base===
{|cellspacing="0" border="1"
!|Category
!|Component
!|Test Coverage
!|Planned #
!|Ready #
!|Auto %
!|Major Contacts
!|Due

|-
| rowspan = "15" | OS Base|| [[../Audio Driver Test Specification | Audio Driver]] || '''Light''' ||31||31||0% || [mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen]||tbd

|-
| [[../Bluetooth Driver Test Specification | Bluetooth Driver]] || '''Light''' || 23 || 23 || 0% ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen]||tbd

|-
| [[../Camera Driver Test Specification | Camera Driver]] || '''Light''' || 12 || 12 || 0% ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen]||tbd

|-
| [[../Functional Key Driver Test Plan | Functional Key Driver]] || '''Open''' || tbd || || || || tbd

|-
| [[../GPS Driver Test Plan | GPS Driver]] || '''Light''' || || || ||Jussi Saavalainen||tbd

|-
| [[../Input Devices Driver Test Specification | Input Devices Driver]] || '''Light''' || 3 || 3 || 0% || ||tbd

|-
| [[../SD-MMC Driver Test Plan | SD/MMC Driver]] || '''Light''' || 33 || 33 || 0% ||Jussi Saavalainen ||Sep.3.2010

|-
| [[../Sensor Driver Test Plan | Sensor Driver]] || '''Light''' || 8 || 8 || 0% ||Jussi Saavalainen ||tbd

|-
| [[../Touch Screen Driver Test Plan | Touch Screen Driver]] || '''Light''' || || || || Juhani Taipale||tbd

|-
| [[../Touchpad Driver Test Plan | Touchpad Driver]] || '''Open''' || tbd || || || ||tbd

|-
| [[../USB Driver Test Specification | USB Driver]] || '''Light''' || 35 || 35 || 0% ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen] ||tbd

|-
| [[../Video Playback Driver Test Specification | Video Playback Driver]] || '''Average''' || 6 || 6 || 0% ||[mailto:kimmo.myllyvirta@digia.com Kimmo Myllyvirta] ||tbd

|-
| [[../Watchdog Driver Test Specification | Watchdog Driver]] || '''Average''' || 3 || 3 || 0% || [mailto:kimmo.myllyvirta@digia.com Kimmo Myllyvirta] ||tbd

|-
| [[../WIFI Driver Test Specification | WIFI Driver]] || '''Light''' || 10 || 10 || 0% ||Jussi Saavalainen ||tbd

|-
| [[../X11 Test Specification | X11]] || '''Light''' || 11 || 11 || 0% || [mailto:kimmo.myllyvirta@digia.com Kimmo Myllyvirta] ||tbd

|-
| [[../Framebuffer Test Specification | Framebuffer Driver]] || '''Light''' || 22 || 11 || 0% || [mailto:mika.niinisto@digia.com Mika Niinistö] ||tbd
|}