QA Processes

QA Processes
for Your Solutions

Jump-start releases with bug-free production
based on metric-driven approach

We combine expertise and latest tech to deliver a top-notch product with improved ROI within time and budget.

Our Best QA Practices

Tech Stack We Love to Use

Icon

Selenium

Open-source framework with browser automation and tools and libraries for functional tests.

Icon

Appium

Open-source tool for development automation of hybrid and native applications on iOS/ Android.

Case Studies

Quality control aligned
with your processes

Ensure your product excellence with Mad Devs QA services.

Vladimir Pan

Vladimir Pan

QA Engineer

Benefits of QA with Mad Devs

undefined

Established in-house standards

undefined

Automation and agility of processes

undefined

Testing with current market conditions

undefined

Transparent and comprehensive reporting

undefined

Active customer involvement

undefined

Cross-disciplinary teams

Insights

QA Engineers - Are They Needed?

QA Engineers - Are They Needed?

In some companies, the entire responsibility for the code lies on developers. It is believed that developers write the code, and they have to test it. Why then are QA engineers needed? And whether they are needed at all?We at Mad Devs aren't asking such questions. We adhere to the rule “people who wrote the code shall not test it”. We have QA engineers in our team, and we appreciate their job. While our developers cover everything in tests, they cannot find all the issues. The reason is simple: developers and QA engineers have different mindsets. They approach a product in different ways. Developers perceive the code as their creation, as a piece of art. It might prevent them from seeing faults.Let me give an example.Imagine that you have created something. It can be just anything, but in our case, we can take a blockchain app. If you have to test it, you check how it works, whether all the processes are performed smoothly, and similar. You aren't thinking of making it break down. Moreover, you don't want it to break down.While a quality assurance engineer does so. It is their job, and they were trained for it. The task of a QA engineer is to find or create conditions that may force your app to break down or work not as expected. They will try to find those combinations of conditions that will make the feature collapse. Moreover, QA engineers have all the needed tools to do so (here, I mean automated, not manual testing. While manual testing is required, we cannot deny that without automation, this work cannot be done at a proper level).