|
Beta testing of Daybook Enterprise normally begins in 'single-user
mode' using test data, checking out the main business processes and
user operations. Later on, the product is run up on a server for
multi-user testing, again using a test data file.
What's involved in beta testing Enterprise 6?
At each stage, any bugs found are reported and feedback is given on
your reaction to the product in general. Daybook then acts on your
feedback, releasing further pre-release versions for you to test and
giving you news about what is happening in terms of fixes and features.
Finally, if and when you are satisfied that the version is robust
enough to use in a live environment, then you can do so. This is an
important part of the process, since there are many things that only
become apparent when software is being used in the real world.
There is an important caveat here, however: once you have made the move
to Ôgo live', there is no going back, so it is vital to ensure that all
business processes have been thoroughly tested before this is
attempted. You also need to be absolutely certain that you wish to
transfer your licence to this version and to pay any charges that may
become due. You should also be aware that by using the version in a
live environment, you would be considered to have gone through
acceptance testing, as defined in the licence. You would also be
required to upgrade to the final release once it became available.
Please also bear in mind that Daybook reserves the right to add or
remove features and to change functionality in the final release.
So, what are we looking for?
We would like you tell us about:
1. Any bugs that you encounter.
2. Any points you may have about screen design or navigation. The
smallest details can be very helpful.
3. Suggestions for improving the way that a feature or function works.
4. Any other suggestions for improving the product.
5. General comments about the look and feel of the system.
6. Anything that you think works inefficiently.
Please see the document provided for specific areas that are changed
you should read this and provide a copy of it to anyone testing the
system for you.
Please bear in mind that we do not guarantee that everything you report
will be actioned in the release, but if it is not we will add it to our
Ôwish list' for forthcoming releases.
What's in it for you?
So, what's in it for the Ôbeta tester'? Well, quite simply it gives you
a great opportunity to influence the development of our software, to
ensure that it works well for you and that you like the look, feel and
whole experience of using it.
Practical information
This is a beta product for you to evaluate and provide feedback.
Be careful opening a data file that you do not open your live data.
Open a copy of your data AND take special care if your data file is
segmented that the copy also includes a copy of the extra segments and
that the current live segments are not visible to the application when
opening. This is because the path to the segments is stored on the
first segment and it is possible that the segments may open, when you
open the data file it should ask your where segment 2 is etc.
You must have either 4D Mono(single user) or 4D Server. Version 2003.3
or above(2003.5 is available from the 4D website).
If you are testing on a MAC with OS9 you will need to set the memory
allocation for 4D client to 60,000k(or more). On PCs or OSX this is not
required.
You will need licences to test(you can open the file and use the
temporary licence), These will be issued to you shortly and be valid
for 30 days
|
