A simple, yet powerful reporting infrastructure is one of the most sought after features from an enterprise grade performance testing tool. Performance analysts rely on reports for visualizing statistical counters that quantify application performance to detect problems.
A tag in Integration Tester is a means of storing a single value for substitution in a test case. A list tag is similar, however it contains multiple values. List tags can be created in a number of ways, such as, by using the Iterate Test Data action, Lookup Test Data action, ECMA script, and by tagging a repeating element from a response. In this blog, we will discuss list tags and how to apply them to a repeating element in Integration Tester.
Starting with version 18.104.22.168, you can publish test suite reports from Integration Tester to Test Control Panel, and then use the Unified Reporting dashboard to access the published reports. You can also publish reports for integration tests scheduled from Performance Tester.
We have recently updated our Testing Portfolio to version 22.214.171.124. This release contains a number of fixes and enhancements. We’ve provided a summary below; if you’re interested in finding out more, please take a look at our release notes:
Read about the new features and enhancements in this release
Performance Tester has an optional SOA extension that can be used for service testing. However, Performance Tester does not include web service examples that can be used to learn the service testing functionality. So, if we have Test Control Panel installed, we can use its sample web services in Performance Tester. This is a great learning aid and provides some additional integration points between the two products.
Test Workbench 9.1.1-9.2 supports Google Chrome up to version 62 (with future fix packs). However, there have been users using higher versions of Google Chrome successfully after a driver update.
Functional Tester is one of the reliable automation tools that provides support to automate the mainframe application testing process. The functional tester connects to the application server through the Functional Tester Extension for Terminal-Based Application. The extension configuration for server connection was a manual process until now.
Let's say a large number of tests that were recorded require a user ID and password to log in. At any point in time, when a password is changed, the password must be changed in all the tests.
DevOps on the Mainframe: How IBM and Rabobank Created an Automated CI Pipeline with End-to-End Tests
DevOps is considered the Holy Grail to achieve highly effective and flexible IT support for business processes. Transaction processing on a mainframe, however, brings challenges to harvest the benefits of DevOps.
We have recently released version 9.2 of our Testing Portfolio with a number of features and fixes that you don’t want to miss. Here’s the highlights, but you can find more details in our release notes.