Testing Materials

Without a doubt, every tester-researcher needs to find not only a bug but also its essence. However, classical exploratory testing is much more than just a monotonous search for a problem. The following are 10 useful and time-tested tips on how exploratory testing can be helpful.

We all know that a bug bash is a good method to implement multi-level exploratory testing. Such an event brings together employees from different teams and areas of activity. This reduces snow blindness and helps to benefit from the experiences and perspectives of many people.

An approach to the development and implementation of automated tests for an application-in-test depends on numerous factors. A size and complexity of an application, a structure of a project team, instantly appearing deadlines, requirements for security, and many other details define the most suitable strategy. Further, we will describe some working strategies that can be helpful for any project that requires automation.

One way or another, all software testers have the common wish to make every future software user happy. This means that they need to learn how to interact with the product owner in any case. The following are 4 simple steps on how to set up such cooperation and profit from it.

Many testers around the world actively use Google Chrome since this is one of the most popular tools. Below we will describe its most useful and effective extensions, which can significantly simplify testers’ day-to-day work (with screenshots and cookies).

This article provides some resources to help you find interesting test areas and charters. They are also good for calculating perceived risks. Namely, we’re talking about such recources as CDMET – Conversation, Documentation, Monitoring and Earlier Testing. Let’s take a closer look at them.

Sometimes you can meet the following question on specialized IT forums: what is the best ratio between testers and developers? You can use various ratios and each one will have either benefits or drawbacks.
Further, we will analyze some examples of them in detail.

Every tester is in some way familiar with the concept of randomly failing automated tests. An analysis of the results of these tests can be really time-consuming and some teams prefer running tests once again if they fail. But is this efficient? The answer is not as obvious and clear as it seems.

Is it possible to finally get rid of defects and other bugs in the software? Why are there so many of them and what’s the nature of their appearance? It is significantly important to understand at least the basic reasons of bug occurance to improve the process of software testing.

Software development and testing are very specific processes. Especially when it comes to performance verification, quick bug fixation and releases. In this case, the best option is metrics measuring tools. And today, we’ll talk about one of such tool for iOS – MetricKit.