Re: "Remove Backspace" test harness

[Brian G. <bri...@da...>]

>can just pick up were we left off and everyone can get up to speed on 
>the issues without too much effort.
>  
>
Here is a copy of my original thoughts sent to Jim:
1. The existing testing only tests a string 1/10 th of the original (at 
a time).  I propose that the input gets switched between a large and 
small string (minimum).  I believe that the transition metrics are of 
particular interest, ie the first run after the imput changes
2. The first run should not be thrown out, but listed as a metric 
(LabVIEW now does a good job on resizing arrays in shift regs, but still 
gets caught when the array size changes significantly.  The existing 
metrics analysis may throw that information out.)
3. Can we randomize the order?
4. Can we create a batch that completely quits LabVIEW between test VI's?
5. We need to verify that the output is correct.
6. Add tests for robustness (empty string, no backspaces, all 
backspaces, string that results in empty string as a result)?
7. OK to remove the example from the test folder so we can make generic 
Tester?

I should have something to share by this weekend.

Brian