Changes between Version 19 and Version 20 of TestPlan082

Timestamp:

03/03/11 13:48:44 (2 years ago)

Author:

c2dietric

Comment:

--

TestPlan082

@@ -9 +9 @@
   * ~~Use your own license text.  Test by changing, from the Eclipse menu bar, Window->Preferences-> OSSIE -> License and paste in new text.  Generate a component, see if the new text shows up in the source files.~~
 
- * Create a python component.  Test long, bool and string properties, both in OEF and in the generated component.
-  * Properties dialog.  Create component.  Test “string” property.  (Check the XML, call configure() and query().)
-  * Use this component in a waveform that also has a C++ component, e.g., TxDemo.  Make sure that WaveDash can configure properties of both components without crashing the waveform.
+ * ~~Create a python component.  Test long, bool and string properties, both in OEF and in the generated component.~~
+  * ~~Properties dialog.  Create component.  Test “string” property.  (Check the XML, call configure() and query().)~~
+  * ~~Use this component in a waveform that also has a C++ component, e.g., TxDemo.  Make sure that WaveDash can configure properties of both components without crashing the waveform.~~
 
  * ALF should start nodeBooter 
@@ -27 +27 @@
   * ~~Multiple devices to one platform~~
 
+ * Test and document any ALF features not already included in User Guide
+ALF features include:  Launch WaveDash using IP address from ALF, config file (paths)
+ * Test and document new WaveDash features, document any WaveDash features not already documented (HTTP server, WaveCLI)
+ * ~~Test/document OEF updates (multiselect and multiple component instances/waveform)~~
+ * ~~Test and document OEF features not already included in User Guide~~
+
 == Test and Release Plan ==
 
@@ -36 +42 @@
   a. Add the UHD device, nodes, and waveforms to the tarball
   a. Test installation and operation
- 1. Merge ossiedev/trunk into 0.8.x branch, test, submit fixes to 0.8.x and trunk 
-  a. Produce an 0.8.x pre-release tarball (make distclean; make dist), making sure to include updates since the last tarball was made, need to include all new Python files in Makefile.am files, and include new component, device, and waveform directories in bootstrap, configure.ac, and Makefile.am  (This could take a few iterations if we find anything is missing.   Time permitting, I would like to see how to do this and how to add new files to the distribution.)
+ 1. Submit fixes to trunk 
+  a. Produce an 0.8.x pre-release tarball (make distclean; make dist), making sure to include updates since the last tarball was made, need to include all new Python files in Makefile.am files, and include new component, device, and waveform directories in bootstrap, configure.ac, and Makefile.am   
 
 === Test Release ===
@@ -44 +50 @@
    a. Run through installation instructions and examples in User Guide, update as needed (may require new screen shots)
  1. Run labs 1-8, using the latest versions, identify and document problems/changes.  Each lab should take an hour or less, excluding documentation, so this could be done by 2-3 people in a day or two.  Changes for 0.8.2 are listed above.
- 1. Test and document any ALF features not already included in User Guide
-ALF features include:  Launch WaveDash using IP address from ALF, config file (paths)
- 1. Test and document new WaveDash features, document any WaveDash features not already documented (HTTP server, WaveCLI)
- 1. ~~Test/document OEF updates (multiselect and multiple component instances/waveform)~~
- 1. ~~Test and document OEF features not already included in User Guide~~
 
 === Create final release ===