1. How to Build a Great Test Drive- Tips and FAQ By Jesse Dailey

2. 2 What is a Test Drive?  Fully functional read only version of the application  Allow customers to “kick the tires”  Present data in a dynamic working environment  Appropriate for all Native applications and some Composite applications

3. 3 Top 5 things to remember 1. Your Test Drive is a Demo- Build a Test Drive that tells the story of your application

4. 4 Top 5 things to remember 2. Customize Your Home Page- Build custom home page components that introduce a user to your test drive

5. 5 Top 5 things to remember 3.Include Dashboards in your Test Drive- Dashboards can quickly and effectively demonstrate you app.

6. 6 Top 5 things to remember 4. Include Sample Data- Customize the data in your test drive to accentuate the importance of your application

7. 7 Top 5 things to remember 5. Be Creative!- There are a number of techniques you can use to demo your application in a Test Drive environment.  Custom links that show “what would happen if you bought this app”  A Pre-Recorded demo that links on the Home Page  Hyperlinks that take a user to the correct data records

8. 8 Anatomy of a Test Drive By clicking on “Create Test Drive” a new org is created with your application installed. This org has two users:  Admin User –The administrator for your test drive. –All changes to the test drive are done through this user –(ex. Username = admin@application.com)  Eval User- –The user that your customer logs in as when they click the Test Drive button on your listing. –This user is restricted read only so no data or settings can be changed. –You will need to reset the password for this user as the admin before you can log-in. – (ex. Username = eval@application.com)eval@application.com Click here for step by step on making a test drive

9. 9 FAQ- How do I update my Test Drive after it is published? Scenario: You have updated your application with a new custom object  Option 1- You have the keys to your Test Drive. You can add updates at any time by logging in as the Admin user and deploying to the Eval User. If the changes are minor, it is easy to replicate them in the Test Drive org.  Option 2- Create a new Test Drive using the Create Test Drive button. This is recommended when the changes to your application are substantial. You will need to add data and re-build the test drive if you use this option. Note: After a Test Drive is created it is independent from the application you have packaged. You will need to update your test drive when you update your packaged application.

10. 10 FAQ- How do I associate a Test Drive with my Listing?  Log into the publisher area of AppExchange.com  Edit your listing and add the log-in information for your eval user. Just like you log into Salesforce.com

11. 11 FAQ- I can’t see my custom objects when I log in as the eval user, but I can as the admin user! Deploy your custom objects to the whole org

12. 12 Resources  Watch this first- Step by Step on creating a test drive http://salesforce.breezecentral.com/testdriving/ http://salesforce.breezecentral.com/testdriving/  Customize a home page- https://na1.salesforce.com/help/doc/en/customize_hom epage.htm- https://na1.salesforce.com/help/doc/en/customize_hom epage.htm- (you need to be logged into salesforce.com to view this)