Visualforce Developer Guide

Introducing Visualforce
Tools for Visualforce Development
Getting a Quick Start with Visualforce
Customizing the Appearance and Output of Visualforce Pages
Standard Controllers
Standard List Controllers
Custom Controllers and Controller Extensions
Advanced Examples
Overriding Buttons, Links, and Tabs with Visualforce
Using Static Resources
Creating and Using Custom Components
Dynamic Visualforce Bindings
Dynamic Visualforce Components
Integrating Email with Visualforce
Visualforce Charting
Creating Maps with Visualforce
Render Flows with Visualforce
Templating with Visualforce
Developing Salesforce Apps with Visualforce
What is Salesforce Mobile Classic?
Salesforce Platform Development Process
Setting Up Your Development System
The Development Process and the Importance of Testing
Testing Visualforce Pages in the Salesforce App
Understanding the Salesforce App Container
Tell Me More: Where Visualforce Pages Can Appear in the Salesforce App
Guidelines and Best Practices
Adding Visualforce to a Force.com AppExchange App
Using JavaScript in Visualforce Pages
Best Practices
Standard Component Reference
Appendices
Glossary
PDF

Newer Version Available

This content describes an older version of this product. View Latest

The Development Process and the Importance of Testing

It’s important to test your Visualforce pages before deploying them in production. Test your pages across different environments, devices, and users.

For instance, we don’t recommend developing for the Salesforce app exclusively on your desktop or laptop and testing your pages by navigating to the /one/one.app URL. The Salesforce app and Lightning Experience share the one.app container depending on the device that connects to it. While you can fool /one/one.app by changing your browser’s user agent, this can lead to bugs down the line—desktop and mobile browsers can behave very differently.

If you’re developing functionality that you need to support across a range of possibilities, your test plan should take into consideration the need to test across:

  • Each different supported device.
  • Each different supported operating system.
  • Each different supported browser—including the Salesforce app, which embeds its own.
  • Each different supported user interface context (Lightning Experience, Salesforce Classic, and the Salesforce app).

Running the Salesforce app in an emulator isn’t supported for normal use. We understand that device emulators are convenient. But they aren’t a substitute for full testing of your custom apps and pages on your organization’s supported mobile devices. During development, regularly test your app on every device and platform on which you intend to deploy.