On Thu, Feb 23, 2012 at 2:12 AM, Philip Rhoades <..hidden..>
I presume we could be testing from the beginning and if we are not
using the newly worked on features or the ones waiting to be worked on,
we should be good? - in terms of the data being maintained up to a
proper release? My immediate demand is for just minimal, basic
accounting . . a few large incomings and regular small outgoings, bank
Once the business unit code is all in and breakage corrected, and the customer/vendor db redesign complete (nothing major here, just a few tweakstweaks!), then transactional testing can begin.
I would note a couple things:
Financial storage and financial information storage routines are not changing in 1.4. So bugs should be more on the "this is broken and doesn't wtweakstweaksork" line rather than the "this is saving incorrect data." I don't anticipate very many of these actually.
As we get into reporting though, you will want to be double checking the reports as you upgrade. Check the changelogs for details before you do and compare old/new reports, flagging differences. Also truly new features like transaction import of things like timecards and chart of accounts entries may have a greater likelihood of bugs/incorrect entry.
Also I believe we will probably clear the Fixes.sql so it goes back no more than one beta, so if you are doing this you'd need to stay up to date.