QA

Created by Google as an in-house testing tool, EarlGrey was open-sourced in 2016, and it quickly gained a sizable following in the iOS developer community. In this article, Toptal Senior QA Automation Engineer Ciprian Balea explains why the Toptal talent app is tested using EarlGrey and demonstrates why you should consider it, too.

As products and services deploy faster and faster, quality assurance (QA) has to adapt and deliver more coverage in less time while maintaining high quality. In this article, Toptal Software Engineer Jade Russel Hancox examines how we can use the user flow to boost the speed and efficiency of QA processes without compromising on quality.

Providing production support to an application is one of the most challenging aspects of software development. In this article, Toptal Freelance Java Developer Flavio Pezzini shows us techniques that can prevent bugs and make finding issues in production much faster.

Your software isn’t fully tested until you write integration tests for it. While unit tests help ensure that functions are properly written, integration tests help ensure that the system is working properly as a whole. In this article, Toptal Software Engineer Luka Blažecki uses Node.js to explain why integration testing is important for every development platform and how to write clean, composable integration tests.

Although database programming does not evolve at nearly the same pace as traditional application programming, recent advancements in several fields are bringing new techniques and technologies within the reach of small and independent developers. In this guide, Toptal Freelance Software Engineer Jeffrey Shumaker explains how developers can quickly and easily tap these methods to identify database issues they may not even be aware of, and how they can build excellent data mining tools without spending a lot on expensive software licenses.

Using React.js props your application's front-end. In particular, testing user interactions and viewing renderings is vastly improved with React UI testing.

In this article, I will show that unit testing itself is quite easy; the real problems that complicate unit testing, and introduce expensive complexity, are a result of poorly-designed, untestable code. We will discuss what makes code hard to test, which anti-patterns and bad practices we should avoid to improve testability, and what other benefits we can achieve by writing testable code. We will see that writing testable code is not just about making testing less troublesome, but about making the code itself more robust, and easier to maintain.