Tableau - Testing in Non-Production Environments


Introduction

Background

Testing your content with a new version of Tableau Server is important, especially if you use advanced features, integrations, or Web Data Connectors (WDC).

NOTE: For production use always use https://tab.med.umich.edu

 

Environments

Status

Name

URL

Version
Staging

Maize

 https://tab-maize.med.umich.edu

 2024.2
Live

Blue

 https://tab-blue.med.umich.edu

2023.3

 

 Testing

 https://devtab.med.umich.edu

2024.2

 

NOTE: Non-Production Environments are only for testing functionality and not to be used for the creation, sharing, viewing, refreshing, and/or revising of visualizations or data sources and any similar content development or review.

 

What should you do if there is an issue?

If you find an issue with the new environments submit a ticket to let us know and ask it to be routed to the Analytics and Business Intelligence Group so we can take a look at it. 



Instructions

Table of Contents

Maize/Blue Upgrades

Starting in 2024, the Blue/Green upgrade strategy will replace the traditional in-place method. This new approach intends to improve the user experience by minimizing downtime and reducing risks during upgrades. 

Preparation and Testing Phase

Once the staging environment is upgraded, the Tableau Server team will inform users it's ready for testing. This phase is critical, as the staging environment will eventually become the live production environment. During this time, users should:

    • Explore and familiarize themselves with new features.
    • Test and validate their content to ensure everything functions as expected.
    • Identify and resolve any issues to facilitate a smooth transition.

The Upgrade Process

During the Blue/Green upgrade, there will be an 8-hour freeze period. This time will be used to transfer production content. Here's what you need to know:

    • Dashboards will remain accessible to end-users.
    • Schedules for Extracts, Subscriptions, and Flows will be paused.
    • While content is viewable, data dependent on Extracts or Prep Flows may be delayed.

Once the transfer is complete and validated by the Tableau Server team, schedules will be reactivated, and the system will redirect to the upgraded environment.

What to Test

DataConnections

Ensure that at least one connection for each data source or database is tested. Verify that both live connections and extracts work as expected. Key areas to check include:

    • Database Types: Oracle, SQL Server, MySQL, etc.
    • Specific Databases: Common databases like HSDW or Clarity, plus any others in use.
    • ODBC Connections
    • Web Data Connectors (WDCs)

If your databases have IP restrictions, contact the Tableau Server Team in EDIS for an updated list of IPs.

Extracts

While schedules are paused, manually test extracts by:

    • Clicking the context menu (...) on a workbook or published data source.
    • Selecting 'Refresh Extracts.'

Live Connections

Ensure live connections operate correctly by simply loading dashboards, which should trigger database connections and queries.

Flows

Test Prep Flows to confirm they function correctly. You may need to create a test version to avoid overwriting existing data when outputting to a database or published data source.

Customizations and Integrations 

Thoroughly test any custom or unique elements, such as:

    • Dashboard Extensions
    • Analytics Extensions (e.g., RServe)
    • Scripts or custom code
    • APIs
    • WDCs

 

Embedded Visualizations

For Tableau Dashboards embedded within applications, websites, or SharePoint, verify compatibility with the new version.

How and Where To Test

 Utilize the staging environment to test your dashboards, flows, and to manually refresh extracts. Explore any forthcoming features as well.

Other Non-Production Environments

In needed, you may be instructed to test on devtab.med.umich.edu, particularly for especially for diagnosing specific issues or evaluating changes.