Connecting to Snowflake
Last Modified:
Snowflake is an elastically scalable cloud data warehouse known for its data analysis and simultaneous access of data sets with minimal latency.
Snowflake is one of the many database platforms that connect seamlessly with Provar Automation; however, unlike other built-in database connections, connecting with Snowflake takes additional steps to set up.
Setting Up External Libraries
To ensure Provar can work smoothly with Snowflake, you will need to add the necessary external libraries that contain operations related to Snowflake. We also use Excel in the custom API.
Download the pre-bundled external libraries here:
If you’d like to get more up-to-date versions, you can find them on their respective websites.
- The Snowpark Library can be downloaded from the Snowflake Developer Resources.
- Click on the Java button to download the latest version as a bundle zip file.
- Additional libraries used in the Custom API
Start by adding the JAR files to the /lib of your project. You can drag them into the folder via the UI.
You can verify information has been added by opening the .classpath file in the Navigator.
Using the Custom API
Download and unzip the Snowflake Connection API in the zip file below.
Drag the SnowflakeConnection.java file into the src > customapis folder in the navigator.
Select the Copy Files option and click OK.
To use the custom API, find the new functionality on the Test Palette under the “My Cust API’s” section. Like any other test step, simply drag it to your test case to use it.
The Snowflake Connection API is created using basic authentication. Values can be added directly in the test step or as variables. Add variables to Test Settings > Variables for authorization values. This allows for overrides by environment and encryption.
Under the Authorization Details section, you will need the following to connect with your data:
- Snowflake Account : In your connection URL, this is the code before the “.snowflakecomputing.com”
- User Name : your login name
- Password : the login password
- Connection URL : change the “https://” in your connection URL to “jbdc:snowflake://” it should look something like this -> jdbc:snowflake://accountName.snowflakecomputing.com
Next, under the Database Details section, enter the information for the data you’d like to pull.
You’ll need the following information to query the database:
- Database Name : A named grouping of schemas
- Schema Name : A named grouping of database objects (tables, views, etc)
- Table Name : A specific collection of data
- SoQL Query : A SQL query to pull information from the specified table. Be careful of pulling too much information that may cause your connection to time out!
You can see from the Snowflake screenshot on the left that these values are nested.
Last, define where you want the query results to go. The Snowflake Connection API is created to query the data and write the results to an Excel file so that information can be looped through or called in later test or test steps.
In the Result section, you’ll have to define the following:
- Filename to Store Results : the name of the result file
- Result Name : the variable name of storing data before writing it to the file
- Result Scope : defines the lifespan of the results
After you finish designing your test, run the test case. To view your result file, right click on the project level in the Navigator and refresh.
Result files will show in the Templates folder of the Navigator. Right click and open with the system editor to view the file in Excel.
For a video walkthrough, check out the video below:
- Provar Automation
- System Requirements
- Browser and Driver Recommendations
- Installing Provar Automation
- Updating Provar Automation
- Licensing Provar
- Granting Org Permissions to Provar Automation
- Optimizing Org and Connection Metadata Processing in Provar
- Using Provar Automation
- Understanding Provar’s Use of AI Service for Test Automation
- Provar Automation
- Creating a New Test Project
- Import Test Project from a File
- Import Test Project from a Remote Repository
- Import Test Project from Local Repository
- Commit a Local Test Project to Source Control
- API Testing
- Behavior-Driven Development
- Consolidating Multiple Test Execution Reports
- Creating Test Cases
- Custom Table Mapping
- Functions
- Debugging Tests
- Defining a Namespace Prefix on a Connection
- Defining Proxy Settings
- Environment Management
- Exporting Test Cases into a PDF
- Exporting Test Projects
- Japanese Language Support
- Override Auto-Retry for Test Step
- Customize Browser Driver Location
- Mapping and Executing the Lightning Article Editor in Provar
- Managing Test Steps
- Namespace Org Testing
- NitroX
- Provar Test Builder
- ProvarDX
- Refresh and Recompile
- Reintroduction of CLI License Check
- Reload Org Cache
- Reporting
- Running Tests
- Searching Provar with Find Usages
- Secrets Management and Encryption
- Setup and Teardown Test Cases
- Tags and Service Level Agreements (SLAs)
- Test Cycles
- Test Data Generation
- Test Plans
- Testing Browser – Chrome Headless
- Testing Browser Options
- Tooltip Testing
- Using the Test Palette
- Using Custom APIs
- Callable Tests
- Data-Driven Testing
- Page Objects
- Block Locator Strategies
- Introduction to XPaths
- Creating an XPath
- JavaScript Locator Support
- Label Locator Strategies
- Maintaining Page Objects
- Mapping Non-Salesforce fields
- Page Object Operations
- ProvarX™
- Refresh and Reselect Field Locators in Test Builder
- Using Java Method Annotations for Custom Objects
- Applications Testing
- Provar Manager
- How to Use Provar Manager
- Provar Manager Setup
- Provar Manager Integrations
- Release Management
- Test Management
- Test Operations
- Provar Manager and Provar Automation
- Setting Up a Connection to Provar Manager
- Object Mapping Between Automation and Manager
- How to Upload Test Plans, Test Plan Folders, Test Plan Instances, and Test Cases
- Provar Manager Filters
- Uploading Callable Test Cases in Provar Manager
- Uploading Test Steps in Provar Manager
- How to Know if a File in Automation is Linked in Test Manager
- Test Execution Reporting
- Metadata Coverage with Manager
- Provar Grid
- DevOps
- Introduction to Provar DevOps
- Introduction to Test Scheduling
- Apache Ant
- Configuration for Sending Emails via the Automation Command Line Interface
- Continuous Integration
- AutoRABIT Salesforce DevOps in Provar Test
- Azure DevOps
- Running a Provar CI Task in Azure DevOps Pipelines
- Configuring the Automation secrets password in Microsoft Azure Pipelines
- Parallel Execution in Microsoft Azure Pipelines using Multiple build.xml Files
- Parallel Execution in Microsoft Azure Pipelines using Targets
- Parallel execution in Microsoft Azure Pipelines using Test Plans
- Bitbucket Pipelines
- CircleCI
- Copado
- Docker
- Flosum
- Gearset
- GitHub Actions
- Integrating GitHub Actions CI to Run Automation CI Task
- Remote Trigger in GitHub Actions
- Parameterization using Environment Variables in GitHub Actions
- Parallel Execution in GitHub Actions using Multiple build.xml Files
- Parallel Execution in GitHub Actions using Targets
- Parallel Execution in GitHub Actions using Test Plan
- Parallel Execution in GitHub Actions using Job Matrix
- GitLab Continuous Integration
- Travis CI
- Jenkins
- Execution Environment Security Configuration
- Provar Jenkins Plugin
- Parallel Execution
- Running Provar on Linux
- Reporting
- Salesforce DX
- Git
- Version Control
- Salesforce Testing
- Recommended Practices
- Salesforce Connection Best Practices
- Improve Your Metadata Performance
- Java 21 Upgrade
- Testing Best Practices
- Automation Planning
- Supported Testing Phases
- Provar Naming Standards
- Test Case Design
- Create records via API
- Avoid using static values
- Abort Unused Test Sessions/Runs
- Avoid Metadata performance issues
- Increase auto-retry waits for steps using a global variable
- Create different page objects for different pages
- The Best Ways to Change Callable Test Case Locations
- Working with the .testProject file and .secrets file
- Best practices for the .provarCaches folder
- Best practices for .pageObject files
- Troubleshooting
- How to Use Keytool Command for Importing Certificates
- Installing Provar After Upgrading to macOS Catalina
- Browsers
- Configurations and Permissions
- Connections
- DevOps
- Error Messages
- Provar Manager 3.0 Install Error Resolution
- Provar Manager Test Case Upload Resolution
- Administrator has Blocked Access to Client
- JavascriptException: Javascript Error
- macOS Big Sur Upgrade
- Resolving Failed to Create ChromeDriver Error
- Resolving Jenkins License Missing Error
- Resolving Metadata Timeout Errors
- Test Execution Fails – Firefox Not Installed
- Selenium 4 Upgrade
- Licensing, Installation and Firewalls
- Memory
- Test Builder and Test Cases
- Release Notes
- Provar AI Assistant Popup Test