2. Data Environments
Data Environments enable testing environments to be managed
and protected ready for testing to commence. During testing,
logical checkpoints are created that allow testing environments
to be reset or advanced, allowing test scripts to be rerun.
Once a test script has executed, the database effects
can be viewed, showing the before and after image of each
record that has changed; including program reference information.
Additional functionality that allocates testing environments
and refreshes libraries when file formats change, simplify
the management of the testing environments.
Data Environment commands can also be embedded within
the test scripts, so you can test the impact on the database
concurrently with testing the impact on the user interface.
|
Creating Environments
& Protection: Testing environments can be made
up of one or more data libraries. Once configured, they
can be protected (journalled) so that the testing environment
can be reset or advanced after a test script has run.
Starting a Data Run: Each
time a user requests a test, a data run is started. From
that point, until the data run is closed, all the database
effects will be recorded to that run instance. Any number
of data runs can be active at any time in multi user testing
environments.
Checkpoint Management: Each
time a data run is started, a new checkpoint is created
if no other data runs are open. Checkpoints mark the logical
testing boundaries within the database and provide pointers
to rollback or advance the database. Checkpoints are used
to manage and control the integrity of a multi user testing
environment.
Data Rules: Data rules can
be constructed to check specific records and fields in
a database to determine if a test has passed or failed.
Compare Database Files:
Physical or logical files can be compared and the differences
displayed or printed.
Compare Spool Files: Spool
files on the system or in database format can be compared
and the differences displayed or printed.
Change Management Interface:
Commands are available to refresh a testing environment
configured in SmartTest400 from within a change management
system, when file formats change.
Data Environments Advanced Program
Interfaces (APIs): SmartTest400’s open design means
Data Environments commands can be used within other SmartTest400
modules and PDM.
To view the full SmartTest400 brochure in PDF format please
click here.
For a live demonstration via the web please contact sales@thenon.com
or phone +44 (0)20 8607 9336
All trademarks are the property of the respective owners.
All rights acknowledged.
|
