TESTING WITH DIFFERENT PROFILES

Transcription

1 TESTING WITH DIFFERENT PROFILES Another simple, practical guide for getting started with Provar

2 Introduction 3 Testing with Different Profiles 3 Introduction 3 Creating the Callable Test Case 3 Creating the Calling Test Case 13 Exercise: Testing with Different Profiles 19 Appendix: Adding a Secondary (Non-Admin) Connection 21 Obtaining User Details 21 Creating a Login-As Connection 23

3 Introduction Welcome to the Testing with Different Profiles module of the Provar Quickstart Extension. This guide is intended to increase your knowledge of Provar through topics not covered in the original Quickstart Guide. This guide is currently in BETA. If you want to know about features not covered in this guide, or if you have any questions about the topics covered here, please contact us at Testing with Different Profiles Introduction In this lesson you ll be creating a Test Case and learning how to execute it from the perspective of a different user. This is a useful facility of Provar but setting it up the first time can seem complex. We will run through the process step by step. Creating the Callable Test Case Start by opening Provar Desktop and creating a new Test Case titled CallableAccount : 3

4 Leave Launch Test Builder Session ticked, and press the Finish button. Once Test Builder has launched, map the steps to create a new Account record, where the Name of the Account is Test Account. Follow the steps below to complete this. Start by clicking on the Account tab. Once you are on the tab, right-click on the New button and select Add to Test Case : Once the draft Test Step appears, click the Add & Do button: 4

5 On the new Account screen, right-click on the Account Name screen and select Add to Test Case : 5

6 Once the draft Test Step appears, enter Test Account in the Value field and then click the Add & Do button: Finally, map a click of the Save button so that the new Account record is created. Now you will delete the new Account record and handle the confirmation alert. On the newly created Account, right-click on the Delete button and select Add to Test Case : 6

7 Then click Add & Do in the draft Test Step: 7

8 The following alert will appear in the browser: At this point leave the Test Builder session running but navigate back into Provar Desktop. Go to the Test APIs Palette and locate the UI Handle Alert, then click and drag it into the Test Case: 8

9 If the new Test Step is not indented to the same level as Click the Delete button, click and drag the Test Step up so that it is indented as follows: In the Expected Message parameter of the Test Step, type out the message body of the alert: 9

10 Check that the Response is set to OK, not Cancel, to indicate that the OK button should be clicked on the alert. Then save the Test Case and navigate back to Test Builder. Click Step Forwards ( Builder to execute the new step. ) on the Test Once the step has been executed, the Account will be deleted and you will be navigated back to the Account home screen: This completes the steps needed for this Test Case. Click Stop ( ) to close this Test Builder session and navigate back to Provar Desktop. Make the Test Case callable by setting the Callable parameter on the topmost Test Step: 10

11 Finally, set the Test Case so that it can receive different Connection details when it is called. To do this, click the Add Parameter ( ) icon on Test Case Parameters: 11

12 In the dialog box that opens, click the Expand icon ( ) against the Salesforce Connect Test Step. Locate the Override Connection parameter and click on it: This will automatically populate Name, Title, Summary and Default Value. 12

13 Then click OK. On the Salesforce Connect Test Step, check that the variable {ReuseConnectionName} has been created in the Override Connection parameter. In the same section, set the If already open parameter to Re-use the Connection : This means that, if the Test Case is run independently, it will use its default Admin Connection (as defined above, in the Connection parameter of the Salesforce Connect Test Step). However, if it is called by another Test Case which passes an Override Connection value to it, it will accept and re-use the Connection that is passed. Finally, save the Test Case. Creating the Calling Test Case Finally, you will create a new Test Case using a different Connection that represents a different (nonadmin) user group, e.g. a Sales user. If you were provided with a Provar test project file to use alongside this document, a non-admin Connection, SalesUser, has probably already been set up for you. You can check whether this exists by referring to the Connections tab in the Test Settings view. 13

14 If you do not have a non-admin Connection already set up, you should create one before proceeding. Refer to the Appendix for more information on setting up a non-admin Connection. Once you have a non-admin Connection set up, you can return to this point and continue creating the new Test Case. In this new Test Case, we will connect to Salesforce as SalesUser, call the CallableAccount Test Case you built earlier, and execute it from the perspective of the SalesUser. Start by creating a new Test Case called CallAccount (Sales). This time, set Connection Name to your new non-admin Connection (e.g. SalesUser ), and untick Launch Test Builder Session : 14

15 Then click the Finish button. Once the Test Case is created, find the CallableAccount Test Case in the Navigator and drag it into the new Test Case to create a new Test Step: 15

16 Then in the Override Connection parameter of the Call Test Step, select the non-admin Connection (e.g. SalesUser ): If you do not get this option in a picklist, make sure the Editor is set to Connection Editor and then try again: 16

17 Once SalesUser is selected, save the new Test Case and run it in Debug mode. To check that the callable Test Case is being executed as Sales User, click on the Salesforce Connect Test Step of the callable Test Case and check the Encoding Username : Alternatively, go to the Variables view for the same Test Step and check Variables (after) > Admin: Another option is to check the browser as the Test Case is executing and look for the Logged in as banner in the top-right corner: 17

18 Congratulations! You have completed Testing with Different Profiles. 18

19 Exercise: Testing with Different Profiles Now that you have completed this lesson, practice your skills with the following exercise. In this exercise you will create a Test Case which connects to Salesforce using a non-admin Connection (e.g. SalesUser ). This Test Case will call two other Test Cases which create an Account and a related Contact record respectively. After the Account is created, the Account Owner hyperlink will be clicked and a printscreen taken of the Account Owner s Chatter profile: Please ensure the following: The CreateAccount and CreateContact Test Cases can re-use any Connection which is passed to them when called. The CreateContact Test Case creates the Contact via the related list on the Account record: All three Test Cases are stored in a new folder within /tests called ProfileExercise. Here are some hints to help you complete this exercise: Create your CreateAccount Test Case by copying the ManageAccount Test Case and modifying its steps. Use the Click Interaction to click the Account Owner hyperlink and take a printscreen of the Account Owner s Chatter profile. After creating the Account, make sure you add add an Output Parameter to capture the Account ID, and consider the scope required for the parameter (defaults to Test Case ): To make sure the Contact is linked to the correct Account, you will need to parameterize the field which defines the Account ID, so that this value can be passed from the calling Test Case. 19

20 If you are not sure how to get started, use the screenshot below to get an idea of how this Test Case could be structured: These tasks are covered in depth in the Data Driven Testing lesson, so refer back to this lesson if you are unsure of what steps to take. After you have completed the Test Case, watch the exercise solution video to check your work: vimeo.com/

21 Appendix: Adding a Secondary (Non-Admin) Connection This appendix describes how to set up a secondary (non-admin) Connection in Provar. You will need to do this to complete the Testing with Different Profiles lesson of this guide. Obtaining User Details To set up a non-admin Connection from scratch, you will first need to obtain some user details. You will need one of the following combinations: Username + confirmation that the user has granted Account Login Access to their company s administrator. Username + password + Security Token Note that the first option is preferred, as there will be no requirement to maintain the Connection. If you choose the second option, you will need to keep the password and Security Token updated. If you have a non-admin test user already set up that you can use, go ahead and retrieve the above user details, then move on to the section below, Creating a Login-As Connection. If you do not have a non-admin test user already set up, follow the steps below to create one. First log into your test environment using your admin Connection details. A fast way to do this from Provar is to open the Org Browser, click on any Object, then when the records load, click on a hyperlinked record ID): 21

22 Once you are logged into Salesforce, go into Setup > Users > Manage Users, and click the New button to create a test user. For example: Once your test user is set up, you will need to check that your test user has granted Account Login Access (if you are using this option). To check this, go to the Manage Users page in Setup. If the user has provided Account Login Access, there will be a Login hyperlink next to their name: If this is not present, you should to log in as your secondary user to grant this access their settings. To grant Account Login Access, log in as the secondary user, go to My Settings > Personal > Grant Account Login Access, then apply an Access Duration for Your Company s Administrator, e.g. 1 Year : 22

23 Then click Save. If you choose not to grant Account Login Access, make sure that you have the user s password and Security Token before proceeding to create the Connection. Creating a Login-As Connection Now that you have your Secondary user details, you can a new Connection for this user. Navigate back to Provar Desktop and into the Test Settings view, making sure it is open to the Connections tab: Then click New ( ): Provide a relevant name for the Connection, e.g. SalesUser, set the Connection Type to Salesforce and the secondary dropdown to Normal Salesforce Connection : 23

24 If your secondary user has granted Account Login Access, select the radio button Use Log-on As via an Admin Connection. This option will not require you to set a password and Security token. In Log-on As Connection, select your Admin connection, then enter the Username: If your secondary user has not granted Account Login Access, leave selected the radio button Normal Log-in, and provide Username, Password, Security Token and Environment in the relevant fields: Note that you will need to update the Connection each time the user s password or Security Token changes. Click the Test Connection button to check the details entered are correct: 24

25 Once you have this confirmation, click OK on the Test Connection dialog, then OK again to create the new Connection. Once this Connection has been created, it will appear under Connections in Test Settings, and the Org Browser will open to the new Connection: With this Connection created, you can now return to complete the Testing with Different Profiles lesson. 25