Data-driven testing is a useful technique to keep your tests efficient, and maintainable. Learn how to use JSON and XML to drive your TestCafe test suite.
Every application needs testing and most of them need End-to-End (E2E) testing. The quickest way to have E2E tests is to do them manually, but repetitive manual work costs far too much for a company. Automation can help reduce the costs of running End-to-End tests and increase the confidence of a team at the same time. It's true that configuring an E2E test runner and including it into our development workflow isn't an easy task, but once you're done, you never look back. We benefit from more confidence in our code with every single test written, and ensure that the combined pieces of an application, or system, work in perfect harmony.
I want to share our experience at TESISQUARE (www.tesisquare.com) in the process of adopting automation. Some of the things can sound obvious but IMHO reviewing it is a must to avoid wasting your time and resources.
Sometimes you need a powerful debugger to get to the bottom of a tricky bug in your tests. Learn how to use the Node.js debugger with TestCafe.
In one of our recent projects at my company, we started using TestCafe for end-to-end UI automation. This article will describe how we ended up choosing TestCafe as the choice of framework for front end automation.
Face it: your end-to-end tests will fail at some point. With TestCafe, you have plenty of ways to get to the bottom of your issues.
If you need to access secure information in your tests, a tool like Vault by HashiCorp can help. Check out how to use it in your TestCafe test suite.
There is plenty of documentation available online for Jenkins and TestCafe. This article is for the beginners to get started with continuous integration without a Docker image. I directly referred to some online documents and added few steps where needed for additional details.
TestCafe is simple to install, but needs some dependencies. If you can't or don't want to deal with it, leverage the power of Docker to run your test suite.
End-to-end tests tend to be slower than other tests. Still, slow tests suck. Here are 5 tips to keep your tests fast if you're using TestCafe.
How can you test external services that you have no control over? Learn how to use mocks in TestCafe to build reliable tests when using third-party APIs.
How does TestCafe Studio fare when creating end-to-end tests for your web app without having to code? Find out in this introduction to the tool.
Mobile Internet usage is on the rise. You need to ensure your website works no matter the screen size. TestCafe helps you automate these tests easily.
Visual testing can be tedious and error-prone work. Learn how to easily automate visual testing with Percy and TestCafe.
End-to-end testing used to follow a very conservative approach. Everyone was using Java/Python/Ruby with Selenium and it really felt that there is no good alternative to this setup. Selenium was everywhere and at some point, it even transformed its protocol to W3C standard. Ok, we have a W3C standard now, so why do we need alternatives?
Making websites accessible to people with disabilities is often omitted. Tools like axe and TestCafe can easily automate accessibility testing for you.
TestCafe has excellent browser support for testing your web application. Learn how to combine TestCafe with BrowserStack to cover all your testing needs.
It's not uncommon for end-to-end tests to fail when the UI changes. Learn how to minimize the risk of failures in your tests with Testing Library.
Testing emails in a web application is often a tedious, error-prone manual process. Automate this testing easily and quickly using TestCafe and Mailosaur.
TestCafe is a powerful tool for creating a robust end-to-end test suite for your web application. Learn how simple it is to start using this tool.
How do you write E2E tests for Amplify apps? In this tutorial, you will see an example using TestCafe. It is easier than you might think.
In this tutorial, you are going to learn how to set up a project with CI/CD. We are going to use the Amplify console to automate our deployment.
A while ago I was setting up integration testing at work for a react app, since we were using GitHub actions to run unit tests it make sense to use the same setup for Integration tests as well. We decided to use the TestCafe to write those tests. This is going to be a very short article about how to run Integration tests for ReactApp with GitHub Actions.
TestCafe is great. It makes it super simple to add e2e testing to your repertoire, making you not only the front-end engineer but the QA engineer too. In my time using TestCafe I have run into situations that I think are common to most test suites. Doing something like creating/deleting user data before and after tests while using concurrency can give you some trouble. I'll show you how I've setup a project to handle this situation.
We often focus on the amount of work it takes for an automation engineer to build and maintain a test framework. While all that is true I would like to take a minute or two to talk about the grey box testers or manual testers or anyone on the team like project managers, who may not develop the test framework but run the automated tests.
Two frameworks have appeared on the scene recently eschewing the long held belief that end to end testing of web applications means building upon Selenium. Cypress and TestCafe are similar in many ways but have some important differences.