Agreed. At a minimum there should be a test plan with test cases, for both existing functionality and any new features. There are quite a few online testing process guides - some of which can be very long.
The manual process which we are doing now is error prone and can be full of interrupts from daily work. Has anyone worked with automated testing? Maybe Jenkins or Atlassian bamboo -Aaron On Fri, Jul 17, 2015 at 2:42 PM, Andy Kurth <[email protected]> wrote: > I would like discuss releasing VCL 2.4.3. This will be a minor bugfix > release. As mentioned in another thread, once 2.4.3 is released we can > proceed to make the transition from Subversion to Git. > > All of the Jira issues tagged for 2.4.3 are resolved. I made some commits > to the backend code earlier this week and I believe things are working > correctly. The only thing I have left to do is to remove the vcld -setup > option added for https://issues.apache.org/jira/browse/VCL-844 because this > feature is not complete. > > I would like to begin to seriously test things next week. We really need > to work on improving our testing procedures after the 2.4-2.4.3 debacle. > Any ideas or suggestions are greatly appreciated. > > Thoughts? > > Thank You, > Andy -- Aaron Peeler Program Manager Virtual Computing Lab NC State University All electronic mail messages in connection with State business which are sent to or received by this account are subject to the NC Public Records Law and may be disclosed to third parties.
