Do you know that you don’t need to test the app, when you purchase its development from IT Company?

Testing - is under responsibility of the software development team and this is their job to deliver the product you’ve requested. A working, all dancing app as per requirements.

Yes, you’ll still need to run through the app to validate that’s it’s matching your requirements and expectations, however prior submitting the done job, Software Development company should run “crash tests” internally. 

Such “crash test” are usually performed by QA, QC or Tester. Below i describe the role of each, so you could understand the development process better.

Let’s start from: What is QA (Quality Assurance)?

This is a full cycle of ensuring the quality of product development, to ensure that the product meets the requirements of the customer: test planning, development of test scenarios, analysis of the development process and planning to improve this process, analysis of technical tasks from customers, risk analysis, testing and more.

At @ITFAQ we have a dedicated QA and he is involved in the development process at all stages and depending on the size of the team, functions can be divided as follows:

1. QA Engineer - makes analysis of technical documentation, test planning, analysis of development processes and planning for improving the quality of these processes.

2. QC Engineer - If QA is more aimed at ensuring the quality of development as a whole, then QC already works directly with a specific product: develops test scripts, analyzes the results and monitors bug fixes.

3. Tester - directly tests the product according to the developed scenarios, using different devices and online device simulators. When the tester finds bugs, he enters them into a special bug management system, for example: Redmine or Jira (on the DOW, these videos were recommended at https://www.youtube.com/playlist?list=PLaD4FvsFdarSWUyuv6cto4gunIvVzDTGD). (A list of other programs can be found even in @Wikipedia https://ru.wikipedia.org/wiki/Error_Tracking System).

In addition to description of the bug, the Tester makes a detailed description of how he found it: in which browser it was tested, which OS was used, which device, etc.

When the bugs are fixed by the development team, the Tester again checks the product.

Testing can be manual (Manual) or automated (Automation).

At @ITFAQ we use Manual Testing most of the time, because we provide customized software development and each project is unique. While Automated tests are working better for routine test scenarios, to reduce time for testing.

Also, testers can be divided as follows:

• Test Analyst - compiles a map and test plan, documentation, denotes testing requirements, provides an understanding of quality requirements.

 Very detailed here:

https://www.software-testing.ru/library/testing/test-analysis/2583-test-analysts-who-is-this

And here

https://software-testing.ru/library/testing/test-analysis/2034-test-analysis-

• Test Design is a test script designer in accordance with the quality requirements and testing objectives.

Very well and described in detail here:

https://software-testing.ru/library/testing/test-analysis/2500-roles-and-responsibilities-of-test-designer

• Test Executive is directly the one who performs the tests according to the created scenarios.
• Test Manager - from the name you can guess that this is the manager of a team of testers, monitors the progress of testing, plans a test schedule, makes sure that everyone performs their tasks in accordance with the requirements. It can act as a link between a team of testers, a client, a QA engineer and a team of programmers.