Did you ever have to create multiple versions of your test cases to accommodate small differences of your test objects? Looking for a trade-off between good testing practice and minimizing project complexity. The following blog post reflects on this challenge and introduces you to a potential solution: Conditional Expressions.
Xceptance introduced its test automation and load testing tool XLT 4.6 in February 2016 and with it we brought you conditionals. Today we want to shed some light on this new feature, the discussion that came along with it and why we finally decided to introduce it. This blog post will equip you with everything required to employ conditional expressions in your test scripts.
In computer programming, a condition or conditional expression performs an action depending on whether a given statement (the condition) evaluates to true or false. The programmer has the possibility to execute a part of the program only if certain circumstances are met. Now don’t worry, you do not need to become a full-fledged programmer to create your test cases with XLT Script Developer. But you should not skip on the possibilities this new feature is offering.
In testing typically you want your flow of execution to be linear, deterministic and transparent. The individual execution steps of your test case should be well-defined and yield the same results in a constant environment. If one execution step fails – e.g. an assertion does not check out – the whole test case always breaks and evaluates to failed. Run, rinse and repeat.
On the contrary often enough your real world test cases need to cater various scenarios. Think multi-region support of your page for example. Area specific content and functionality can quickly bring you into a catch-22 situation. Follow good practice in test case design, but deal with complexity and organizational nightmares in your test suite. Tiny differences in your test objects force you to keep multiple versions of your (already lengthy) test cases. Farewell maintainability! Continue reading Conditional Expressions in XLT→
This is your place to discuss test automation and performance testing with XLT. We would like to hear your opinion about the product, know your feature wishes, and see what you have done with XLT. Of course, this is also the place to ask for help, offer support, present solutions, and share results.
Xceptance will use this forum to:
announce new versions of XLT
present features and ideas
share general knowledge around testing
respond to support questions that are of general interest
You can ask support questions at any time and because this is a community forum, we encourage everyone to respond and share their wisdom. Xceptance might or might not engage in those conversations.
If you have support questions that need a guaranteed response, we recommend that you buy a support package. You can buy one online with the help of the XLT Self Service Center.
Please note that all contributions to this site are licensed under Creative Commons by Attribution 4.0 International. By engaging in a discussion you automatically agree to that.
Xceptance released version 4.5 of its load testing and test automation product Xceptance LoadTest (XLT). This release enables you to write better test documentation, delivers more scripting capabilities, and shows really cool charts.
Script Developer has been enhanced to let you maintain the documentation of your script library directly in Script Developer. This way you can create and maintain your test documentation together with the code and don’t need to be able to read the code to understand the test cases.
On January 19-20, 2015, Xceptance held its first XLT Summit. About thirty representatives of well-known companies from a variety of fields, including finance, retail and eCommerce, all of whom use XLT to help them in developing web-based software applications, accepted our invitation to meet at Xceptance’s headquarters in Jena, Germany. The goal of the conference was to give XLT users the opportunity to discuss their experiences using our tool both with each other and with the internal XLT development team.
To kick things off, on January 19 we enjoyed a casual dinner in a local restaurant. The next day there was a varied program consisting of presentations contributed both by Xceptance colleagues and external users. Our customers reported on their practical experience using XLT, and had a chance to discuss their results with the other users. The many different applications of XLT–from load testing to test automation to application monitoring–were thus illustrated in light of actual day-to-day practice. A selection of these presentations can be found here: http://goo.gl/fPJj1Q, and parts of the presentation provided by our guests from OTTO.DE can be read here: http://dev.otto.de/.
In addition, the XLT development team presented the newest XLT features. Our guests had the opportunity to speak directly with the developers about their specific feature requests, some of which we were able to immediately agree to implement.
In short, the conference was a great success. In response to the overwhelmingly positive feedback from the participants, the XLT Summit will now be a regular annual event.
Last but not least, we would like to thank all the attendees, without whose engagement, interest and suggestions the event would not have been possible!
Sauce Labs and BrowserStack – What Are They and Why Use Them?
This approach still work fine, but we came up with a much better one. Head over to GitHub and see our Multi-Browser-TestSuite for XLT. It will make multi browser testing a breeze. By the way, all the code is licensed under the MIT license, so absolute flexibility for you.
Sauce Labs and BrowserStack allow you to run automated test cases on different browsers and operating systems. Both provide more than 200 mobile and desktop browsers on different operating systems. The benefit? You can focus on coding instead of having to maintain different devices. You can easily run your test cases written on iOS on an Internet Explorer without actually buying a Windows device; and last not least, you don’t need to worry about drivers or maintenance.
Xceptance has released version 4.3.2 of its load testing and test automation product Xceptance LoadTest. This is an improvement and bug fix release. More information about this release can be found in the release notes.
Improvement: Support for Firefox 27.
Improvement: Usability improvement when sorting test data entries or module parameters.
Improvement: Native platform line endings are used when exporting Java code now.
Improvement: Script migration errors are now written to the log panel instead of to messages boxes.
Fix: No error message anymore when two scripts have the same name but are located in different packages.
Fix: Query parameters were incorrectly parsed because the fragment (#…) was included.
Fix: WebDriver features were not exposed when WebDrivers were reused.
We continue to share cool things with the community of software testers and developers. Today we are announcing the availability of our no coding test suite for XLT under the Apache License v2.0.
You want to fire just a couple of URLs to load test your application? You have to investigate the performance problems of a feature and you need accurate measurements as well as a lot of load generated? You like XLT and its capabilities, but you don’t have the time to compile a sophisticated test suite from scratch? Whatever your motivation, our new test suite for XLT is the solution you are looking for. Continue reading TestSuite-NoCoding – Load Testing with CSV Files→
Xceptance released version 4.3 of its load testing and test automation product Xceptance LoadTest. It features a wide range of improvements and new functionality.
As always, this update is free of charge for every user. You can use XLT freely for your daily automation work, regression testing, and performance validation. If you are an eligible Open Source project, you can get a full XLT license for your load and performance testing needs for free as well.
Enjoy more automation with less clicking. The new information panel summarizes the specifics of the currently selected item, so you do not need to open it anymore. Additionally, the new log panel lists all executed commands and their respective parameters.
If an element is styled with the CSS property text-transform, then the element’s text on the screen may have different character casing from what is defined in the page’s DOM tree. The WebDriver specification mandates to return the text as shown on the screen. Script Developer will now record text with the the character casing that appears on the screen and it will also take the CSS property text-transform into account when replaying text assertions.
The XLT load test reports have been improved by adding more charts and data details, such as overall statistics for all timers. Arrival rate charts have been added to visualize the load development over time and make sure the desired load factor was reached.
Charts can now optionally be configured to be logarithmic. A capping can be added to hide larger spikes, which usually make charts hard to read, without removing the important information altogether.
The new networking section summarizes all general network-related statistics and charts on a separate page.
The error and event page has been redesigned and includes a new error chart that contains separate graphs for all transactions/actions/requests so that the temporal distribution of transaction/action/request errors is displayed in one chart. A new error summary table groups all errors by their error message to help you see which types of errors occurred and how many of them.
Load and Performance Testing
The master controller features two new commands to validate the availability of agents and display their current configuration. A new command line option permits the skipping of result downloads when XLT is used as a load generator only.
A set of new commands is available in Script Developer and in the framework: commands such as assertAttribute, assertStyle, assertClass, assertEval, and their matching store and wait equivalents.
XLT can now send and receive IDs as part of the request to ease the correlation of server-side logs and test results. XLT may send a randomly generated alphanumeric ID as request header or extract such an ID from an arbitrary response header.
When dealing with different test environments, different load profiles, and/or different test data at the same time, managing different combinations of configuration settings can be challenging. The new property file include feature makes it easier now to predefine aspects and reuse them later in different configurations without copying and pasting.
When a test case reads a certain setting from the configuration, the framework uses a fallback strategy when doing the property look-up. This strategy performs an additional look-up step now, based on the transaction name (the short name to which the full class name is mapped). This additional step lets you parameterize different transactions differently, even if they are mapped to the same class and therefore share the same code.
The webdriver that will be used when executing functional tests can now be configured via properties. This allows greater flexibility and hardcoding is not necessary anymore.
When XLT executes XML script test cases with a WebDriver instance that is capable of taking screenshots, it can take a screenshot after each action, if desired.
A new look matches the overall styling of reports. Also, the navigation bar can now be resized, requests are color coded to visualize the content type, and the first page is displayed automatically. URLs are now active links, so you can click them easily.
XLT is shipped with an empty test suite project that can be used as a template for your own projects.
HtmlUnit has been upgraded to version 2.12.
WebDriver/Selenium has been upgraded to version 2.39.0.
EC2 admin console permits setting a tag name now.
Amazon Machine Images
The Amazon Machine Images (AMI) listed below are available for public use. Using these images is free of charge, but require that you own an Amazon Web Services (AWS) account. Please make sure that your EC2 security group permits communication on port tcp/8500. AMIs with Java 6 are no longer provided.
eu-west-1 : ami-ceae46b9
us-east-1 : ami-2510394c
us-west-1 : ami-e4ccfca1
us-west-2 : ami-9ebadeae
ap-southeast-2 : ami-617be45b
If you need XLT-AMIs in Tokyo, Singapore, or Sao Paulo, please let us know.
Purchase Licenses and Support Online
Licenses and support can be conveniently ordered through our XLT Self Service Center. You can instantly download licenses and purchase support right when it is needed. All your invoices and previous licenses (when purchased online) are accessible at any time.
We will notify you before your license or support runs out, so that you will never miss that again. This enables you to continue your daily automation and load testing work without interruption. Please note that we do not renew your contracts automatically, so no strings attached.
Visa and MasterCard are accepted. All credit card data is processed and secured by Wirecard.
By clicking Opt-Out, we will place a non-personalized cookie on your machine that indicates that you don‘t wish to be tracked.