TestCafe Team Blog
This section contains articles from the TestCafe team
Introducing the TestCafe Jenkins Plugin
Published by Pavel Redrukhin, Eugene Titerman – Jul 29, 2020

TestCafe can capture videos and screenshots so you can debug your tests and examine page UI. You can record all tests or only those that failed, generate unique video files for each test or record all of them in one take, and single out specific interactions. (For a full list of available options, see the following help topic: Screenshots and Videos).

Many TestCafe users take advantage of Jenkins — a CI/CD solution — to automate their tests. Until recently, they had to manually match the screenshots and videos taken by TestCafe to the individual test reports. The newly implemented TestCafe Jenkins plugin simplifies this process. Links to screenshots and videos taken during the test now automatically appear on the Jenkins test results page. There is no need to keep the testing server running — all required files are stored inside the Jenkins build folder.

Read More

Upcoming Webinar: 10 Ways to Simplify Your UI Testing
Published by TestCafe Team – Jul 14, 2020

In this free webinar, our Technical Evangelist Paul Usher will show you how to easily incorporate UI testing in your development workflow. Paul will demonstrate how TestCafe can fit in any organization and how its features can be leveraged to deliver high quality web apps that always meet end-user expectations.

Read More

How to Speed up Debugging in TestCafe: Tips and Tricks
Published by Sergey Shurygin, Vasily Strelyaev – Jun 30, 2020

In the previous post, we talked about the approaches you can follow to debug TestCafe tests. In this post, we will focus on best practices that help you save time while debugging. We will also mention a few things to keep in mind in order to write easy-to-debug tests.

Read More

How to Debug Tests in TestCafe: Quick Guide
Published by Sergey Shurygin, Vasily Strelyaev – May 25, 2020

If you've ever written a TestCafe test, you may be familiar with the following errors:

  • Cannot obtain information about the node because the specified selector does not match any node in the DOM tree.
  • The specified selector does not match any element in the DOM tree.
  • The element that matches the specified selector is not visible.

The first two errors are self-explanatory. The last error, however, can easily be misinterpreted. This error frequently occurs if multiple elements match the same selector. The first matching element may be hidden, while the required element is visible.

What should you do next? How do you update the selector so that it produces expected results? What should you do if the test previously passed, but it now fails?

Read More

How to Scroll Web Pages Using TestCafe
Published by Alexander Prokhorov, Anastasia Karabanova – Apr 20, 2020

If you're writing functional tests, you may need to scroll tested pages to display specific elements. In this article, we look at several test scenarios to show how TestCafe navigates pages.

Read More