Kinesis CI 1.8 offers cutting-edge new features, including enhanced Publish to Tableau task that enable users to publish Tableau workbooks and data source with changing data base connection details and migrate Tableau files between Tableau Environments. This will enable true Continuous Delivery for your Tableau Projects. The new release supports ‘New Browsing Experience’ in Tableau 2018.3 and enhanced Performance testing.
Change Data Source Connections, Deploy and Migrate Tableau Workbooks Effortlessly
New Options for Publish to Tableau Task
Deploy or migrate dashboards
Deploy your Tableau Workbooks and data sources to different Tableau environments connecting to different data sources with different credentials, or migrate between Tableau environments. Simply Publish workbooks from Kinesis and specify new data source connection details that will be used to publish the workbook. You can automatically reset data base connections and credentials within Kinesis CI, there is no need to use Tableau Desktop and manually change connections in every single workbook.
This enables true Continuous Delivery for your Tableau projects. Cover your dashboards with a range of test cases set up in Kinesis and deploy them automatically to your next environment for Staging or Production.
Test your Dashboard under Concurrent Load
Enhanced Performance Testing
Improved Performance testing
Drive Load to your Tableau Server and assess response time against your SLA requirements based on load time and availability for your specific dashboards. Verify and monitor if newly added features on your dashboards impact user experience. Simulate concurrent load to assess scalability for your Tableau server.
The enhanced Performance Testing is compatible with the newest versions of Tableau on Windows, as well as on Linux. You can expect the same, solid performance testing features with enhancements in the back end.
Set up test cases easily in the UI with browsing the content of your Tableau Servers and create dynamic snapshots
No Server Admin Role Required
Tableau Server admin role no longer required for browsing the content of your Server
Set up your test cases easily in the UI with the ability to browse the content of your Tableau Server and simply select Tableau dashboards to test with a mouse click. You can now also access data sourcesthis way for example for publishing purposes, not only workbooks.
Create snapshots in Kinesis to be able to use the metadata behind your dashboards when setting up test cases, such as daat columns, filter or parameter names, dashboard layout and underlying data. Server or site admin role is no longer required to access this feature in Kinesis, empowering an even larger number of users in corporate environments to fully capitalize on the features in Kinesis UI to make the setup of test cases a seamless and easy process.
Test your workbooks displayed in the 'New Browsing Experience'' in the newest Tableau
Support for New Browsing Experience in Tableau 2018.3 and beyond
Run Kinesis tests with the newest versions of Tableau
Enjoy the New Browsing Experience Tableau offers in their newest releases and continue to test your workbooks in Kinesis with a range of tests. Kinesis CI now fully supports the new layout of Tableau, so when you upgrade to the newest releases, you’ll be able to continue testing with Kinesis CI.
Issues Resolved – Kinesis CI 1.8.11 (September 15, 2020)
Fixed an issue with Google Chrome same site cookies enforcement, which resulted in Kinesis being unable to open Tableau visualizations on Windows Tableau Server
Fixed an issue when publishing Tableau workbooks didn’t always work when changing datasource connection
Issues Resolved – Kinesis CI 1.8.10 (August 16, 2020)
Added support for Tableau Server 2020.3
Issues Resolved – Kinesis CI 1.8.9 (June 15, 2020)
Added support for Tableau Server 2020.2
Fixed an issue with SSO login, now standard login steps are not run when SSO login is required.
Issues Resolved – Kinesis CI 1.8.8 (April 20, 2020)
Added support for Tableau Server 2020.1
Added support for OpenJDK 11
Issues Resolved – Kinesis CI 1.8.7 (December 2, 2019)
Added support for Tableau Server 2019.4
Fixed issue when Image assertion was not working on Tableau 2019.4
Issues Resolved – Kinesis CI 1.8.6 (November 15, 2019)
Fixed issue when number of rows taken in baseline didn’t correspond to definition in Settings
Issues Resolved – Kinesis CI 1.8.5 (September 30, 2019)
Added support for Tableau Server 2019.3
Issues Resolved – Kinesis CI 1.8.4 (June 10, 2019)
|Fixed issue when errors were not listed in Performance Test reports on the Availability tab|
|Added Refresh Page command in Functional Testing – Drive Browser task|
|Webdriver no longer runs for Performance Tests|
|In Functional Testing – Publish to Tableau task, filter REST queries with URL encoded strings, fixing space issues|
Issues Resolved – Kinesis CI 1.8.3 (May 20, 2019)
|Tableau Server 2019.2 compatibility enabled|
|Set Tableau 2019.1 as default Tableau Version in Context Variables|
Issues Resolved – Kinesis CI 1.8.2 (March 25, 2019)
|Tableau Server 2019.1 compatibility enabled|
|Updated Performance Testing for Tableau Server 2019.1, including new labeling for performance events|
|Updated Slack logo in Integrations|
|Removed PhantomJS webdriver option|
|Fixed issue when tabs in context group modal are mixed up when editing properties|
|Fixed issue when reports were sometimes not visible in the list|
Issues Resolved – Kinesis CI 1.8.1 (March 4, 2019)
|Fixed an issue when reports have not displayed in order of test runs|
|Allow self-signed SSL certificates for the purpose of publishing Tableau documents|
Issues Resolved – Kinesis CI 1.8 (February 11, 2019)
|Support ‘New Browsing Experience’ introduced in Tableau Server 2018.3|
|Performance testing – upgraded to support newer versions of Tableau Server. Below Tableau 10.3 Performance testing is not supported in Kinesis|
|Fixed issue when Tableau Server version was sometimes not picked up from context variables correctly, resulting in issues with Filters|
|Fixed issue in case multiple Drive Browser tasks were used within one test case, and second or subsequent Drive Browser tasks did not follow-on from steps done by the previous tasks|