Have you wondered how the teams working on Telerik products test software? In the next chapter of our detailed guide, we give you deeper insight into the processes of our Business Services. You can find past chapters here.
You’re reading the sixth post in a series that’s intended to give you a behind-the-scenes look at how the Telerik teams, which are invested in Agile, DevOps, TDD development practices, go about ensuring product quality.
We’ll share insights around the practices and tools our product development and web presence teams employ to confirm we ship high quality software. We’ll go into detail so that you can learn not only the technical details of what we do but why we do them. This will give you the tools to become testing experts.
Important note: After its completion, this series will be gathered up, updated/polished and published as an eBook. Interested? Register to receive the eBook.
Register for the eBook Now
To test the visual appearance of a website, we need tools and procedures that check the visual appearance and/or the CSS code directly. For that reason, we have created a Test Studio based solution that compares screenshots of the pages. The solution defines expected results by capturing a screenshot of the final version of a page. We run this test nightly to compare the expected page UI with the current one.
Tests are executed via Microsoft Test Controller and Test Agents. Currently our automation tests are executed on eight different machines, in parallel. The execution is triggered via several Jenkins builds.
We use Jenkins to analyze the tests results:
Dashing Dashboard provides a common place to show all automation test results. A Sinatra-based framework, Dashing enables you to build useful dashboards that combine different sources of information, including Jenkins tests results, TeamPulse status, GitHub status and more.
Next time, we start a new chapter discussing legendary product quality with ever faster release cycles of the developer tools that comprise Telerik DevCraft.
Did you find these tips helpful? Stay tuned for the next chapter and let us know your feedback. And don't forget to register to receive the eBook that will be put together when this series is complete.
If you are interested in trying the latest Test Studio, feel free to go and grab your free trial today.
Anton is a Quality Assurance Architect at Progress. He is passionate about automation testing and designing test harness and tools, having the best industry development practices in mind. He is an active blogger and the founder of Automate The Planet. Ardent about technologies such as C#, .NET Framework, T4, WPF, SQL Server, Selenium WebDriver and Jenkins, he won MVP status at Code Project (2016) and MVB (Most Valuable Blogger) at DZone.
Copyright © 2017, Progress Software Corporation and/or its subsidiaries or affiliates. All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks or appropriate markings.