Wiki Test Report Format: Difference between revisions

From Yocto Project
Jump to navigationJump to search
Line 5: Line 5:


==== Test Result Matrix ====
==== Test Result Matrix ====
A general Test Result Summary and a detailed Test Result Summary should be provided here.
''A general Test Result Summary and a detailed Test Result Summary should be provided here.


===== Example =====
===== Example =====

Revision as of 07:05, 3 May 2011

This page is to define Test Report Format for Yocto

Test Summary

Here is a test result summary for a build.

Test Result Matrix

A general Test Result Summary and a detailed Test Result Summary should be provided here.

Example

Test Result Summary

Component Target Status Comments
BSP SugarBay GOOD Zypper install/remove has issue; 3D game running failed;
  CrownBay BLOCK emgd crownbay build failed; matchbox-panel segfault; S3 fail on B0 board
  JasperForest GOOD The only issue is zypper install/remove bug
  Blacksand Buggy mouse/keyboard do not work in X window; zypper install/remove not work well
  Beagleboard GOOD Only one RTC issue exists
  Routerstationpro GOOD Only zypper install has issue
  Mpc8315e-rdb GOOD Only zypper install has issue
QEMU qemux86 Buggy Only zypper install/remove has issue
  qemux86-64 Buggy Only zypper install/remove has issue
  qemuarm Buggy zypper could not work well
  qemuppc Buggy zypper could not work well
  qemumips Buggy Only zypper install has issue
SDK   BLOCK i686 toolchain not copied to sharing folder; unfs does not work with qemuppc;
Poky   BUGGY sstate and non-gplv3 build do not work correctly
Stress   GOOD Sugarbay pass 18 hours stress and Jasperforest pass 12 hours stress
Compliance   GOOD Sugarbay pass LTP and POSIX test
Documentation   GOOD  
' Critical bugs, more than 50% test cases are blocked
Only Normal, Minor or Enhancement bugs, less than 10% test cases failed
Normal, Major and Critical bugs, more than 10% test cases failed

Detailed Test Result Summary