In today’s post we will discuss the steps necessary to enhance an XLT-based test suite with multi-browser support. We will show how to tag your test cases to conveniently run them in different environments and execute the test suite in a local or remote fashion.
Xceptance maintains a MIT licensed test suite at GitHub which demonstrates functional testing for large scale projects. With the suite we’ve put an emphasis on clear structures, naming and test case organization. Targeting Demandware’s SiteGenesis storefront at heart, the underlying concepts and mechanisms are valuable for everyone building test suites for comparable web applications with XLT. Next to being a template for test automation and best practices in test suite design, it can be a starting point ready to pick up in your very own projects. We regularly utilize it and want to encourage you to explore, employ and contribute.
A regular challenge in testing ecommerce applications is the variety of different browsers and platforms that are available today. As you probably know XLT, the test automation and load testing framework from Xceptance, is based on Selenium browser automation and the Webdriver API. Supporting multiple browsers therefore comes naturally. This blog post will demonstrate how XLT is able to streamline different testing environments directly in your test suite. You will learn how to execute your tests locally and remotely with the help of Sauce Labs and similar automated testing platforms. Along the way you will pick up some details about XLT as well as Script Developer and quickly find yourself equipped with a ready to use multi-browser test suite example.
Continue reading Multi-Browser Support for Test Automation with XLT
Recently we received a support request regarding special characters in Script Developer. Perhaps other XLT users stumble across a similar requirement, so it’s a good idea to make the discussion available to the public.
First of all, some bad news: Up to now, Script Developer does not have explicit support for special characters, such as Line Feed (\n), Horizontal Tab (\t), Backspace (\b) or similar. For example, typing multiple lines of text – each line delimited by a newline character – into an element on your page is not possible just like that. Upon loading your script, XLT Script Developer normalizes all white-space characters contained in the target or value field of any command.
Of course, we don’t want to leave you out in the rain but provide a feasible solution.
Continue reading Special Characters in Script Developer
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
Many of our customers have asked for it, and today we’re delivering it: the XLT Community Forum: https://ask.xceptance.de/.
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.
The XLT Community Forum is powered by Discourse.
Today, we are happy to announce the release of our new Demandware SiteGenesis Community Test Suite! It is a test suite for automated storefront testing of the Demandware SiteGenesis reference e-commerce storefront.
The test suite’s intention is to share experiences, transfer knowledge, and to demonstrate best practices in test automation. The test suite is built using XLT of course. XLT is freely available and extends concepts you already know from Selenium.
Continue reading Our Demandware SiteGenesis Community Test Suite
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.
Load testing is even more fun now. Continue reading Xceptance released XLT 4.5
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.
By the way, Internet Explorer even seems to run faster at Sauce Labs than on a desktop machine. Also note that Sauce Labs supports Maven builds.
Continue reading Use XLT with Sauce Labs and BrowserStack
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.
EC2-AMIs with Java 7
- eu-west-1 : ami-3650a641
- us-east-1 : ami-d33a01ba
- us-west-1 : ami-5ef4c91b
- us-west-2 : ami-ce97f4fe
- ap-southeast-2 : ami-fd0c92c7
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