Migration Testing Guide

  • Article

Note

This testing guide has been revised as of October 2022. The following steps should take around 30 minutes to complete. The new sections added are:

  • Instructions to render and test AWLI V3
  • Staffing and non-staffing customer setup
  • Staffing and non-staffing consent screen examples
  • Mobile devices testing

Important

  1. Refer to this section for any troubleshooting while testing the AWLI V3 widget.
  2. For any unresolved issues encountered during testing, create a Zendesk ticket detailing the issue along with apiKeys and sample job URLs used for testing.
  3. If you want to build to the AWLI V3 widget directly, create a Zendesk ticket expressing your interest to build to V3 for the next steps

How to Render and Test AWLI V3

Repeat the following steps to test all career site templates that your customers can use:

  1. If you support both staffing and non-staffing customers, find a job page with a working AWLI V2 button for each type of customer (if AWLI V2 does not work , create a zendesk ticket with apiKey and sample job url). Refer to the Staffing and Non-Staffing Customer Setup topic for instructions on how to setup a staffing and non-staffing customer for testing, if needed.
  2. Steps to test when not signed into LinkedIn.
    1. Go to www.linkedin.com and sign out of your account (if you are already signed in).
    2. Follow the steps in the Guide to Render Apply With LinkedIn v3.0 topic to render the AWLI V3 button on the selected job page from Step 1.
    3. Once the AWLI V3 button renders, click the button. A page for Sign into LinkedIn will open in a new window.
      awliv3 sign
    4. Sign into your LinkedIn account by providing your login credentials.
    5. After successfully signing in, you should be redirected to an OAuth consent screen in the same window. The text on the consent screen varies for staffing and non-staffing customers. Refer to the Staffing and Non-Staffing Consent Screen Examples for more information.
    6. Check for the following details on the consent screen
      1. Logo - For Customers (e.g Proprietary ATS or Career Page Solution), the logo should be the customer logo. For Partners (e.g ATS), the logo should be the ATS logo.
      2. Application name - For Customers, the application name should be their application name. For Partners, it should be the relevant customers' application name provided as part of the step for configuring customer application. Partners should check all of their customer application names for accuracy, and if needed, create a ticket on Zendesk with a list of their customers' application client ID and corresponding names.
    7. Clicking Allow on the consent screen should close the consent window and take you back to your career site job page. Refer to Step 4 below for further testing steps.
    8. Clicking Cancel on the consent screen should display the below page for 5 seconds in the same window before the window closes. You should then be taken back to your career site job page.
      awliv3 cancel
  3. Steps to test when already signed into LinkedIn
    1. Go to www.linkedin.com and sign into your account if you are not signed in.
    2. Follow the steps in the Guide to Render Apply With LinkedIn v3.0 topic to render the AWLI V3 button on the selected job page from Step 1.
    3. Once the AWLI V3 button renders, click on the button.
    4. An OAuth consent screen page will open in a new window. The text on the consent screen varies for staffing and non-staffing customers. Refer to the Staffing and Non-Staffing Consent Screen Examples for more information.
    5. Check for the following details on the consent screen
      1. Logo - For Customers (e.g. Proprietary ATS or Career Page Solution), the logo should be the customer logo. For Partners (e.g. ATS), the logo should be the logo of the ATS.
      2. Application name - For Customers, the application name should be their application name. For Partners, it should be the relevant customers' application name provided as part of the step for configuring customer application. Partners should check all of their customer application names for accuracy, and if needed, create a ticket on Zendesk with a list of their customers' application client ID and corresponding names.
    6. Clicking Allow on the consent screen should close the consent window and take you back to your career site job page. Refer to Step 4 below for further testing steps.
    7. Clicking Cancel on the consent screen should display the below page for 5 seconds in the same window before the window closes. You will then be taken back to your career site job page.
      awliv3 cancel2
  4. Steps to test after clicking Allow on OAuth consent screen
    1. Make sure your career site job page displays the applicant’s profile data shared by LinkedIn via the callback function. This callback function is a configuration (data-callback-method) set during the initial Apply With LinkedIn Plugin integration.
    2. Open developer tools by right clicking anywhere on the page and select the Inspect option. Click on the Network tab in developer tools. awliv3 network
    3. Filter the network tab by “apply-with-linkedin”. awliv3 network2
    4. Complete applying to the job by submitting the application.
    5. Once the application is submitted, check the Network tab for a call to the LinkedIn AWLI widget with CONVERSION mode as shown below. awliv3 network3

Note

Once the applicant/user gives consent to share a profile with an employer, the OAuth consent screen for the same employer will not appear for the next 30 minutes

Staffing and Non-Staffing Customer Setup

  1. For Non-Staffing Customers
    1. Enable a customer for the AWLI integration via LinkedIn’s Onboarding widget. The configuring customer document provides details on how to integrate with LinkedIn’s Onboarding widget and how to enable a customer for AWLI.
    2. Make sure the AWLI V2 button renders and works for this customer.
  2. For Staffing Customers
    1. Enable a customer for AWLI integration via LinkedIn’s Onboarding widget. The configuring customer document provides details on how to integrate with LinkedIn’s Onboarding widget and how to enable a customer for AWLI.
    2. Use the “integration context” from the above step to create a Zendesk ticket to enable the customer for Staffing set up.
    3. Make sure the AWLI V2 button renders and works for this customer.

The consent screen for Staffing and Non-Staffing customers varies in text as shown below

Non- Staffing Customer Consent Screen

awliv3 nonstaffing

awliv3 staffing

Mobile Devices Testing

To test that the AWLI button renders correctly and that the end to end flow works correctly for iOS and Android devices such as mobile phones and tablets, use a browser device simulator/responsive mode.

More information on using browser simulators can be found below:

Guide to Render Apply With LinkedIn v3.0

To test if there are any problematic customizations, complete the following steps detailed below:

  1. Find a page on your career site with a currently working AWLI button

  2. Test the new version of AWLI by setting a local storage value in the career site with the following key and value. You can return back to the current version of AWLI by removing these values.

    localStorage.setItem(‘in.awli.v3.enabled’, ‘true’)
Key -  “in.awli.v3.enabled”
Value - “true”

  3. Refer to the below topic Enabling AWLI V3 using Local Storage Flag for details with screenshots

Note

To test with your test/stage developer application, simply browse to a test job page with a working AWLI button and it should render the AWLI V3 button

Enabling AWLI V3 using Local Storage Flag

Listed below are the steps to enable AWLI v3 using local storage flag:

  1. Open Chrome developer tools by right clicking anywhere on the page and select the Inspect option
    awliv3 1
  2. Click the Application tab in the developer tools
    awliv3 2
  3. Click your career site URL where AWLI is being loaded in the local storage section. In the screenshot we are using linkedin.com as an example but your career site will be different
    awliv3 3
  4. Right click the empty row under the Key column and select “Add new” to add a new row
    awliv3 4
  5. Type “in.awli.v3.enabled” as the key name
    awliv3 5
  6. Right click the Value column for the newly added row and select Edit “Value”
    awliv3 6
  7. Type “true” as the Value
    awliv3 7
  8. Refresh the page, the AWLI V3 widget should appear
    awliv3 8

Issues and Resolution

Below are common issues that might occur while testing the new AWLI along with their corresponding resolution:

  • If multiple sites appear in Step 3 (above) and AWLI v3 is not working even after enabling the flag on your career site, try setting the key on all of the sites listed in local storage
  • In case the AWLI V3 widget does not appear as shown in step 8 (above), then repeat step 3 and add the key to all sites listed in local storage

Here are some sample issues to look out for:

  1. New AWLI widget/button does not render:

    1. CSS or Javascript customizations have been made on top of LinkedIn’s AWLI widget. These customizations need to be removed in order to properly render the new AWLI widget
    2. The page is already loading LinkedIn’s in.js script. This preload of “in.js” script needs to be removed or load “in.js” with the same API key used for AWLI. Note that LinkedIn uses API key to uniquely identify a customer. Please create only one API key per customer and avoid loading multiple instances of in.js with different API keys on a page

  2. New AWLI widget/button renders but there are multiple buttons on the same page

    1. Make sure to integrate with AWLI only once per job page

  3. New AWLI widget renders but it is not aligned properly or is cut-off

    1. File a Zendesk ticket detailing the issue along with apiKeys and sample job URLs used for testing

  4. New AWLI widget renders but when clicked, a new window with something went wrong opens:

    1. File a Zendesk ticket detailing the issue along with apiKeys and sample job URLs used for testing

  5. Company logo is incorrect or blank in the OAuth consent screen:

    1. File a ticket via Zendesk and attach the correct logo. Our teams will then process the update and confirm once it is completed