From ef0b23ea7dba56647ceffa0b561d971f7f963540 Mon Sep 17 00:00:00 2001
From: patacongo <patacongo@42af7a65-404d-4744-a932-0658087f49c3>
Date: Thu, 22 Mar 2012 22:41:11 +0000
Subject: Prep for NxWidgets 1.0 release

git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@4506 42af7a65-404d-4744-a932-0658087f49c3
---
 NxWidgets/UnitTests/TestStatus.txt | 59 ++++++++++++++++++++++++++++++++++++++
 1 file changed, 59 insertions(+)
 create mode 100755 NxWidgets/UnitTests/TestStatus.txt

(limited to 'NxWidgets/UnitTests/TestStatus.txt')

diff --git a/NxWidgets/UnitTests/TestStatus.txt b/NxWidgets/UnitTests/TestStatus.txt
new file mode 100755
index 000000000..965f83ef7
--- /dev/null
+++ b/NxWidgets/UnitTests/TestStatus.txt
@@ -0,0 +1,59 @@
+NxWidgets Test Status
+=====================
+
+At this point, the NXWidgets GUI toolkit code complete but still not
+completely tested.  This is a list of testing issues that still need to be
+addressed.
+
+The following Widgets have been have completed unit testing.  The level of
+unit testing is, however, superficial.  Many features have not yet been
+tested:
+
+  - CLabel
+  - CTextBox
+  - CButton
+  - CButtonArray
+  - CKeypad
+  - CRadioButton (and CRadioButtonGoup)
+  - CGlyphButton
+  - CLatchButton (and CStickyButton)
+  - CLatchButtonArray (and CStickyButtonArray)
+  - CCheckBox
+  - CProgressBar
+  - CImage
+  - CSliderHorizontal (and CSliderHorizontalGrip)
+  - CSliderVertical (and CSliderVerticalGrip)
+  - CScrollBarHorizontal (except paging buttons)
+  - CScrollBarVertical (except paging buttons)
+ 
+The following components have unit test in place, but do not successfully
+pass the test:
+ 
+  - CListBox (and CListBoxDataItem) which also tests:
+    o CText
+    o CList and CListDataItem
+    o CScrollingPanel
+    
+The following no unit tests (and, hence, are probably non-functional):
+
+  Infrastructure (won't have their own unit tests)
+  - CScrollBarPanel
+
+  Widgets that need unit tests:   
+  - CCycleButton
+  - CScrollingTextBox
+  - CMultiLineTextBox
+  - CScrollingListBox
+
+There are things that require testing after all widgets complete their unit
+tests as well.  As examples:
+   
+ - Need to verify that a screen with many widgets works correctly.  That
+   focus is correctly handled when widgets are removed.  etc.
+ - Need to verify that widget with many children work correctly together.
+ - Need to verfiy that a display with many windows with multiple wigets
+   per window works okay.
+
+Most unit-level testing was performed in a simulated environment driven by
+simulated mouse and keyboard input.  So many features are not tested that
+require human interaction ... such grabbing and dragging scrollbars.
-- 
cgit v1.2.3