Testing using realistic scenarios

When you test process versions, use realistic test scenarios that mimic the environment and use cases that are expected in the staging and production environment. Realistic scenarios help to reduce issues found during staging and production testing. It is recommended that you look at these settings in your development environment:

Platforms:
Develop and test on the same platform as the production environment when possible. For example, prepare and perform your development testing on the same application server and database that the production environment will use. You also need to consider using the same Sun Java™ JDK versions.

Operating system and web browsers:
Prepare and test on the same operating system when possible. Also, use the same web browsers to perform your testing and consider using same the patch levels for both the operating system and web browser.

Users, groups, and roles:
Test with user profiles, group profiles, and roles that have similar permissions and system privileges as in the production environment. For many development environments, developers have extended privileges that a typical user does not have in a production environment. For this reason, you need to test with similar user profiles and group profiles as found in the production environment. Configure user profiles, group profiles, and roles in Administration Console. For information about configuring users, see User Management Help, accessible in the Administration Console.

Location of assets:
Test with an identical directory or folder structure for any assets used by the process version you design in your production environment. Assets include forms, images, fragments, SWF files, and data files you design. For example, in a production environment, the form can be located at a URL instead of a specific folder structure in the repository.

Acrobat and Adobe Reader:
It is recommended that you test with the same editions, versions, and patch levels of Acrobat or Adobe Reader that an end user will use in the production environment. For example, if you production environment only uses Adobe Reader, it is recommended that you to use Adobe Reader for testing.

Adobe Flash Player:
It is recommend that you test with the most current supported version of Flash Player that is used in the production environment.
Hinweis: Some versions of Acrobat, Adobe Reader, and Flash Player may not be supported in your production environment.