← General Information

Lauch Prep Testing

What is Launch Testsing

After you have completed a “Final Peer Review” edit list from the Pre-Launch Site Edits trello board, that means the site is officially ready to launch!

A day or so before the site’s official launch date (ideally, though this sometimes does happen day of launch), you should get tagged in the #org-content-launch room by the PC for the FI, including your name as the helper.

You won’t need to start doing things the minute you’re tagged. The person who is doing launches for that day will be notified, and they will begin the process of pushing the site. If they have issues during that time, they will contact you.

Troubleshooting Pre-Launch Errors

TBA

How to Do Pre-Launch Testing

Eventually, you will be tagged by the person doing launches to let you and the PC know that the site is ready for testing. This will include a set of two command prompt commands to run. The first command (it will require you to enter your password) edits your hosts file. After doing that, if the command goes through properly, you should be able to go to the site’s live URL and view their new site, matching UAT.

If the site does not show, check if you’re on VPN.

  1. Yes? Disconnect from VPN, re-run the command, and try the site again.
  2. No? Let the person in charge of launches know.

This is the point where you can officially start your pre-launch testing.

First, go to the Trello card for the site, found on the CMS Site Deployments trello board. You should just be able to use cmd+F to find the site.

The second-to-last last checklist on the Trello card for the site, labeled “Launch”, is what you’ll be following for the launch testing. Here is what each point means–make sure to check it off when done!

  • Check site speed - You can basically ignore this and check it off right away, as any issues with site speed should have been covered in launch testing.
  • Check mobile friendly - Same as above.
  • Check Banno API token in the institution - This is related to the ATM locator item below. If the ATM locator works, you can check this one off automatically.
  • Check ATM/Branch Location page to ensure data is populating - Find the site’s ATM locator. - Check and uncheck each of the Branch and ATM checkboxes to make sure that something is loading for all of them. You can also cross-check this against UAT, since there are sometimes ATM networks that the client never filled out. Basically, if it’s empty on UAT, it’s OK to also be empty on the live site. - If branch/ATM pins are broken, this is something you’ll need to fix. Pull down the repo for the site (if you don’t already have it), and set up the correct icons. Upload to UAT as normal, and push to git. Then, log in to the live site CMS and manually upload the zip for your updates. (It’s not possible to use Agent Smith for this update because the site isn’t actually live yet.) Once the zip is finished uploading, go back to the ATM locator page and check to make sure everything is showing correctly.
    • For branch locations that have images, those sometimes fail to pull through correctly when the site is launched. Notify the PC that the branches have images, and they will take care of fixing the broken images. - If you are seeing console errors when clicking checkboxes, or nothing is loading, it’s likely that something was migrated wrong, so the person in charge of launches should be notified.
  • Check / Reindex Search - Type in a test search term into the site’s search, something like “credit” or “branch” that is guaranteed to get you search results. If you don’t get results for an obvious term like that, it’s likely that the site’s search needs to be reindexed. There are two ways to do this. 1. Go to this URL, replacing bankname.com with the live URL of your site: https://banno.com/a/login?redirect_to=/a/cms/api/site/bankname.com/page/_reindex. You will need to log in to the CMS first, and then it should redirect you to a very basic page that says “true” in the top left corner. Try your test search again to make sure the reindex worked. 2. Log in to the live CMS on Postman, and use the Reindex Search group to reindex the search that way. Make sure to switch your environment back to UAT when you’re done so that you don’t stay logged in to the live site CMS.
  • Check Google Analytics - This used to be a more involved process, but nowadays you just need to check that the analytics have been plugged in. You can open the inspector and do a cmd+F in the code for UA- (usually, sometimes G-), or manually open the <head> and drill down until you find the Google Analytics script. Make sure that the line containing the Google Analytics ID is un-commented and contains something other than placeholder text. If there is no Google Analytics code set up, verify with the PC that the client doesn’t have Google Analytics.
  • Test Micro Site - The microsite is used as a fallback if the main website ever goes down. For this, you’ll need to go to the URL www.yourbank.com/temporarilyunavailable (adding “temporarilyunavailable” to the URL). For new sites, you’ll get an error, and for sites that are existing clients of ours, you may find an existing microsite. Either way, it’s likely that a new microsite was created for the new site’s launch, so you’ll need to merge it in and deploy it.
    1. Go to the microsites repo on GitHub, and click on the Pull Requests tab at the top. Find the microsite for your site and click into the PR. (Some developers include the PR for the site in the launch checklist to save time, so you may be able to skip this step!)
    2. Click the green “Merge pull request” button.
    3. Once it goes through, the button will turn gray/disabled.
    4. Finally, you can open Agent Smith in Slack and run the command push-microsites. Smith will verify that it’s running the command for you, and after a minute or two, will tell you that it’s finished pushing microsites.
    5. Since your microsite was merged in, you should now be able to go to the /temporarilyunavailable URL for your site and view the new microsite. You may need to do small things like fixing the size of the logo, for which you can just create a branch on the microsites repo, merge it yourself, and run the push-microsites Agent Smith command again.
    6. Also verify at this time that the OLB login form on the microsite is the same as it is on the live site, and that both function as expected. This is especially important for sites that are re-launching a new site with us, as they may have updated their OLB in the process.

And with that, you’re done testing! Post in the Slack thread for your site’s launch to notify the PC that everything looks good for you. The PC will also be going through their own launch checklist at this time and verify that things are working for them. When the site is OK’d for launch, the person in charge of the launch will “flip the switch” and put the site live on its launch date (or, they will notify the FI that they can do it, if the FI is controlling their own DNS).

Banno Redesign

If your site is a Banno redesign and the new site is a branch inside the existing repo, see Launching Banno Redesign for steps on finalizing the repo to move to support.