SAML login, HAR import, and more!
This month we launch support for SAML external login, HAR replay, and many more features. This blog is part 1 of 2 because there are so many new and improved features! The second part will follow next week.
SAML External Login
If your company uses a SAML compliant single-sign on solution like OneLogin or Okta, Testable now supports this form of login. Once setup, your team will have a dedicated landing page at [subdomain].testable.io and no longer need to setup a Testable password.
See the documentation for more details.
Http Archive (HAR) Replay
A HAR file is a method of recording a set of interactions with a site via a web browser. This set of steps can be useful as a load test scenario to replay at scale. See this page for more details on how to capture a HAR file.
Once captured there are two methods for using this file within Testable:
1. Import Into a Recording
Create a recording scenario and click the Import HAR File button on the scenario page. You will be prompted to choose a HAR file. The steps will be imported into the recording and can then be replayed at scale.
2. Use in a Node.js Script
Often times simply replaying a HAR file is not realistic because it contains cookies, user credentials, etc. A mechanism for manipulating the steps on every iteration is needed.
Enter the new har-replay NPM module. Upload your HAR file to a Node.js scenario and read it via the har-replay module. The module has callbacks that allow you to manipulate each request as well as get notified of results. This allows you to pass credentials between steps as an example.
Metric Drilldown
Any timing metric (e.g. Response Time, DNS Lookup Time, Connection Close, etc) including a custom one now has a drilldown view. The view displays all aggregators for that metric including percentiles, min, max, average, and standard deviation.
To view, click the magnifying glass next to the metric value in the Metrics section of the results.
Multiple Histograms
A single chart on the results page can now display more than one histogram. For example HTTP status codes and HTTP methods. This includes support for custom user defined histograms.
New NPM Module: request
Node.js scripts can now make use of the popular request module, a simplified HTTP client. All network calls are instrumented and metrics are automatically reported back into your test results.
On Premises Test Runners: View Total Capacity
If you run on premises test runners you can now view the total memory and CPU capacity of each of those regions.
To view this information either go to Account => Test Runners and hover over the on premises region name or do the same while creating a test configuration.
Smoke Test Memory/CPU Utilization
When smoke testing your scenario (i.e. run a scenario 1 time as 1 user) it can be useful to know how much memory and CPU were required. This helps in sizing the test parameters appropriately (e.g. number of instances).
Selenium Webdriver.io Improvements
Since our Webdriver.io launch at the end of last year we have been busy making various improvements to our functionality.
- Simplified configuration: All Testable specific configuration requirements have been removed (e.g. proxy settings, reporter, etc). They are now automatically added for you at runtime. See our latest example configuration file for more details.
- Shared virtual desktop: The Webdriver.io script and the Selenium standalone now both run within the same virtual desktop (via xvfb). This allows for use cases like initiating a copy operation in the script and executing the paste within the Selenium driven browser.
- Updated drivers: The Gecko and Chrome drivers have been updated to the latest stable version.
In addition to these features several fixes and minor improvements were applied in this release as usual.
Please check out the new feature and let us know if you have any thoughts or concerns. Happy testing!
