To use or not to use – every customer asks themselves this question, when it comes to mobile automation testing. They say that development and supporting of UI auto tests costs too much. But let’s return to the statement a little bit later. And now we are going to discuss the following questions: what is mobile automation, who is it for, what for and do you actually need it?
Testers on the project usually deal with described requirements for which it is necessary to make an assessment of the testing time, write a test plan, compile a set of tests and conduct tests. When performing this work, the tester very often encounters the need to clarify the requirements, rewrite incorrectly formulated or contradictory descriptions. In the process of clarifying the requirements there is a need to modify, supplement, rewrite tests. Since the tester verifies positive and negative scenarios, the work of users with different access rights, the operation of the script with different preconditions, then the number of test scenarios written for the requirements is usually greater than the scenarios described by the analyst. If the analyst makes changes or rewrites a requirement, then the tester needs to make changes to all related tests. This work takes a very long time. How to reduce the time to work with requirements during testing?
Writing test cases is one of the basic options within a QA engineer’s arsenal. Properly written test cases may be applied to almost any development methodology, testing technique or project size. They can provide QA team with a crucial success or easily become the most annoying part of the testing process. This guide is intended to help QA engineers of any experience to achieve the first and avoid the latter.
Our previous article described how to build a template for a testing round and what and why we need for that. But such template is just a tool and it is useless when not used correctly. So let’s drill down into QA process and its procedures we are using to let the testing be flowing fast and easily. Below, we are going to share the detailed instructions as well as some QA process improvement ideas.
This article describes our best practices in building the QA process for a software development project. What are our main goals in it?
Fast and featureful
First, the delivery of new software versions to end users as fast as possible is vital for software development nowadays. Fierce competition in the software market compels software companies to release new features sooner than their rivals to attract users. As a result, the Agile techniques have spread widely as they combine flexibility and short delivery cycles.
Performance testing is a type of testing proceess to determine the responsiveness, throughput, reliability and scalability of a system, it has under a certain load. The goal of the performance testing is one of the listed below:
- To assess readiness of the system for the production release,
- To evaluate performance of the system against some baselines,
- To find the best configuration settings of the system,
- To find the source of performance,
- To determine throughput levels.
The role of API has grown over the last few years. The growing use of cloud based technologies leads to more API-interfaces providing access to web-services. API supports this important interaction between the client and service. In this case, not only the proper operation of API methods is very important, but also their performance. Let’s take a look at the tools which are the leaders in conducting automated API testing such as SoapUI API testing.