Testing Environments

Before deploying an app to production or release it to customers, developers migrate apps to a dedicated Testing Environment where they can perform integration tests with large sets of data, do security checks for multiple users and profiles, and uncover bugs or discover enhancements they would like to add.

Automated test scripts can’t determine a user’s level of satisfaction with the app, so there is a need to train several new users to evaluate the application in a real-world setting without affecting the business data. In essence, developers need to create another development environment that mimics the Production Environment, and have these trained users/testers use it.

It can be Production Environment or Development Environment specifically used for testing application’s functionality before deploying to production or releasing to customers.

Developers have multiple options for creating a dedicated Testing Environments.

• One is to create a Sandbox copy of their Production Environment and deploy directly from the Development Environment to their sandbox. Using this way, developers will not only test the finished application, but also the procedure used to deploy the completed application as well.
• If there is no sandbox then they can use a Developer Edition environment as their testing environment. The standard Developer Edition environment may be limiting because of license and storage limits.
• There is also Partner Developer Edition for partners who are looking for a production-like environment with more users and storage to run real-life tests.

Scenarios:

Scenario 1:

A Developer looking to get started for free building a Force.com application.

Developer Edition

Scenario 2:

A Customer who wants to build a new Force.com application for their Production Environment.

Developer Edition Environment or set up a Sandbox

Scenario 3:

A Partner who wants to build a Force.com application to sell.

Developer Edition or Partner DE

Let us now look at Chapter 4 – Data Modelling.