salesforce.com winter ‘10 prerelease program...salesforce.com winter ‘10 prerelease program 1...

Salesforce.com Winter ‘10 Prerelease Program

1

Thank you for your interest in the Salesforce.com Winter ‘10 Pre-release Program. By participating in the program, you’ll reap many benefits including:

• testing your solutions against new features and functionality prior to general availability

• the ability to get your teams up to speed on the upcoming release • gaining insight into upcoming new features you can leverage to enhance

your applications • assisting you in ensuring the quality your solutions

The document below outlines the steps you need to follow in order to get started. Questions? Log a case in the Partner Portal selecting Platform/Application Support and Pre-Release as the Case Reason.

Overview

Step Description Start Date End Date Page

1 Create one test org from the Partner Portal for each application

Now Sept 8, 2009 2

2 Create 3 sandbox instances per application Now Sept 8, 2009 6

3 Install application into two sandbox instances Now Sept 17, 2009 12

4 Test your application against the Winter ‘10 release prior to production upgrades

Sept 18, 2009 Oct 1, 2009 13

5 Reporting Issues - - 14

Note: If you already have a test account with 3 sandboxes set up from the Summer 2009 Testing, please refresh all three sandboxes prior to Sept 8, 2009, and skip directly to Step 3 (0).

http://sites.force.com/partners/PP2HomePage?p=P_Home


2

Create a Test Environment from the Partner Portal

1. Login to the Partner Portal and select the ‘create a test org’ box or link

https://sites.secure.force.com/partners/PP2PartnerLoginPage?


3

2. Complete the Partner Test and Demo Org Environment Sign up Page, including selecting the box at the bottom agreeing to the terms of the Master Subscription Agreement. Be sure to select the Enterprise/ Platform Edition since the Professional Edition is not supported in the Pre-release. Click Submit when finished.


4

3. You will see the following page once completed

4. Check your email and follow the link provided. Use the Username and temporary password provided in the email to login. Once you change your temporary password you are done for now.


5

5. If the application being tested requires special features enabled (territory management, opportunity teams, etc.), please do so within this test org. This will ensure that the sandboxes created from this org will come with these features enabled. If a specific feature requires the salesforce.com team’s approval, please request this perm to be enabled by logging a case in the Partner Portal (Record Type: Platform/Application Support; Case Type: Pre-Release; General Application Area: Feature Activation; Functional Area: Feature Activation).

Then give a brief description of the feature activation request which you need and submit the case. Please include the Org ID of your test org as well as grant salesforce.com customer support login access until October 10th.


6

Create 3 Sandbox Instances Per Application NO LATER THAN September 8, 2009

1. Once logged in to your Test Org, please click on the Setup link at the top right 2. Click on the Data Management link on the left of the screen 3. Click on the Sandbox link on the left of your screen, which brings you to the Sandbox Sign up page


7

4. Create and activate three sandbox organizations for use in pre-release testing: a) Sandbox 1:

1. Name: Test1 2. Description: Package Upgrade Testing

b) Sandbox 2: 1. Name: Test2 2. Description: Test latest package version on Winter ‘10

release

c) Sandbox 3:


8

1. Name: Test3 2. Description: Test fresh install in Winter ‘10 release


9

5. Once you have created your sandbox orgs in your Test Org, you will have to wait for about 10 minutes per org to setup. Depending on the size of each of your sandbox orgs you may have to wait a little longer. You will be able to see the status of the creation of your sandboxes from the Sandbox link, which will look something like this:

6. Once you have setup your 3 sandboxes you will receive an email for each of the Test sandbox orgs you have created. The email will look like this:


10

7. The email will give a link as well as explain that you must add on .sb1, .sb2, and .sb3 OR .test1, .test2, and .test3 when logging into your respective sandbox orgs that you have created. The login screen to the sandbox orgs with your username will look something like this:

OR


11

8. You can tell you are logged into sandbox because the screen will look something like this:


12

Install Application into Sandboxes (NO LATER THAN September 8, 2009)

Sandbox 1 (Test1):

d) Install a recent, but not latest, managed-released version of your package into the SB1/Test1 org. The installed package should be a version that is used by many customers, if possible.

Sandbox 2 (Test2):

• Install the latest managed-released version of your package into the SB2/Test2 org.


13

Best Practice Testing Suggestions (After Sandbox Upgrades on September 18, 2009)

In general, you should always test the functionality of your application on a new release. Suggested Packaging Tests

These tests cover packaging installs, upgrades, and uninstalls.

Sandbox 1 (Test1): • Upgrade the package in the Test1 org to the latest version.

Confirm your app continues to function as designed.

Sandbox 2 (Test2): • Test the installed package to ensure it continues to work as

designed. Sandbox 3 (Test3): • Install the latest version of your package into the Test3 org.

Confirm your app continues to function as designed.

Package Uninstall Testing: • Select from one of the three test orgs and uninstall your package.


14

Issues and/or Problems with Testing

• If you have any questions/concerns, please log a case in the partner portal

• Case reason: Pre-release; General Application area: AppExchange; Functional Area: Packaging/ Uploading/ Installing apps OR Platform

• Description: o Description of the issue o Provide Org IDs and grant Salesforce Administrator Access

to the publisher and sandbox orgs until October 30, 2009 o Package URL which is experiencing the error


15

• Once completed logging a case, you can add attachments or comments to the case here:

salesforce.com winter ‘10 prerelease program...salesforce.com winter ‘10 prerelease program 1...

Documents