• Top open source android automation tools

    Most of the population of our planet has a mobile device. And this is all potential customers for different companies. Obviously, many companies, for this reason, want to have a mobile application to reach the largest number of potential customers. Therefore, a big role is given to testing these applications and experience shows that more than half of users delete the application if they find even a minor bug in it. For these purposes, a large number of tools have been created that can automate the process of testing mobile applications. Below is a description of the main ones.

    read more

  • Basic rules for beginners in automation testing

    Few people doubt that testing should be. A lot of people doubt that they do it well. You will always see beginners and more experienced QA members should share their knowledge with new generation. The main task of the article is not to explain specific tactics or show unique tests. This is not about tools or frameworks. Article was created in order to give beginners useful tips and rules which will help them to automate their tests correctly. So you may consider it as tutorial for beginners.

    read more

  • Regression testing automate or no automate?

    Here we'll talk about boring part of testing - regression testing. And real slogan will be “If you want a regression done right, automate it.” Applications nowadays are often large and complex. They include several levels and many modules with complex relations. Therefore, mobile testing, testing of websites or testing of software requires a lot of time and resources.To simplify such processes, automation is often used. With its help, thousands of test cases can be performed without human intervention. Automated testing becomes the most cost-effective and convenient when applied to regression tests.

    read more

  • Main types of defects in software testing process

    A nightmare of any QA engineer is a bug which returns from production. You work hard, you try to check every possible flow, you test it for 8+ hours per day, and after the release the user within a week reports a critical problem. How is it possible? Why it happens and how to fix it? I split possible defects in process by groups.

    read more