Find malfunctions as early as possible: BetterQA, an award-winning software testing firm, will help you test almost anything

In a software development process, Quality Assurance or QA testing is an integral step. By identifying the defects in the early stage of the development cycle, QA will save you enough time and money. Proper QA testing will reveal errors, redundancies, and inconsistencies in the newly developed software. This step is critical, and it will ensure that it can survive in the real world and has longevity. Testing should occur throughout the lifecycle of a project to avoid going back multiple steps to fix something in the later stage. A QA tester must be agile enough to understand even a minor change in the software to understand its impact and test it.

A chef should not certify the dish they made. Someone who developed the software should not be testing it. Companies hire independent testing teams for a reason – the most important of that being – a developer shouldn’t certify their own code. If they do, that just outrightly violates the basic principle of software testing. QA offers a sense of confidence to the management, and BetterQA is an award-winning software testing consulting/services company that helps companies gain this confidence. BetterQA provides software testing services., including software automation services as well. They follow the ISTQB methodology during testing, as their team has ISTQB certifications. The company conducts tests on Mobile, desktop, web, wearables, and games software products. BetterQA is your one-stop solution for all your software testing needs. The company was founded in 2018, and it is based in Cluj-Napoca, Romania.

In conversation with Tudor Brad, Owner of BetterQA

Q. How do you help clients to ensure a continuous balance between meeting market demand with a high-quality end product?

Each project has its own particularities, so we take time to understand them and adapt our process. Most of the time, we create a project workflow in JIRA to match the team’s velocity. We ask for a testing environment, request that we have control of the deployments on the test environment; we create a system test plan, where we execute written test cases against the newly developed features. Ideally, here is our flow:

Bringing on a QA team to participate in the following:

• Once the feature spec has been written out, we review it, so we can address and find problems before it gets implemented; the most cost-effective bugs are the ones found in documentation;
• Writing automated/manual test cases for the spec while the development team is writing the code;
• Executing the selected test plan (also including the written test cases) against the newly implemented feature; component integration testing; standalone component testing;
• Bugs will be found - then we need to decide (with the product owner) which ones should get fixed now (in the current sprint) and which ones should get deferred;
• Once the bugs get fixed, we’ll do another test plan execution and to see if other areas of the product have been affected or not by the new changes;
• When there are no more bugs to be fixed in the current sprint related to this feature, close out the story ticket and call it as accepted

Q. Unrealistic Schedule biggest problem in most of the STLC, and it impacts on Quality of the product/project. Testers should get enough time to test the application. How do you help your clients to face such a situation without compromising the end result?

Each one of our clients would like their entire product tested in one day or less. That just doesn’t work. Once we get on a project, we always propose how we should handle the testing process, with up to date test cases, test suites, and test plans, which need to be executed and pass, before shipping a release. That’s not always the case. In this regard, we try to take a risk-based approach and validate what’s most important. With all of the cards on the table, the client finally decides to pull the trigger and release the new update.

Q. QA/Software testing is one of the most significant and fundamental parts of building any product or technology. Do you have qualified individuals who can maintain your service standards?

Of course, we always allocate time to perfect our testing processes. Each one of our team members is presented with our testing process at the beginning of their ramp-up. We re-evaluate these processes and update them per-project basis regularly.

Q. Does Artificial Intelligence have any role to play in QA/Testing?

Mostly, it is useful, for example, in automation testing. When some aspects on the screen get changed due to UI updates, AI can play a role in identifying and automatically fixing the scripts without human intervention.

Q.What are your plans for the future development of your company?

We plan on growing new local talent from the younger generation, which needs a second chance. This is our way of giving back to the local community. Also, we plan on gradually growing our projects each year by increasing our marketing team. To be able to handle the growing number of projects, we always need to have a backlog of Software testing engineers ready to jump on the next one.

Q. What are your trajectories for the next five years?

If things go well, we are planning to have multiple QA departments, managed internally by their managers. Equally important is the marketing department. We are also working on making a name for ourselves so that potential clients know about us. I always say that recommendations are the way to go. In this regard, we strive to be the best each day.

Meet the leader behind the success of BetterQA

Tudor Brad is the owner of BetterQA. He initially started as a QA intern in 2009 at a Romanian outsourcing company. Brad replaced one of their colleagues who had to travel to Germany for a couple of months. In two weeks, they had to put another developer on the project as the bug rate was 50% higher. That’s when he knew that he had an eye for detail, so Brad proceeded with the software engineering career. He finished his BSc in applied electronics, and from 2012 till the end of 2015, Brad worked at a software outsourcing corporation. In 2018, he started BetterQA, and since then, he’s always on a lookout to improve work by using new tools.

“Dedicated support, seamless feedback, and incredibly passionate testers will keep your developers and customers happy.”