Home > Case Studies > QA for Windows server desktop solution (SQLCM)

QA for Windows server desktop solution (SQLCM)

Testing a Windows server desktop solution that monitors available Microsoft SQL servers, both local and remote, connected over a network, and analyzes databases and the operations performed on those databases for compliance.

This client came to us after we did a trial project for them. Since then we’ve already been working together for two years. In regards to this project, the client’s request was to thoroughly test the solution, ensuring that code updates would not hamper the existing functionality and the final product build would be stable and reliable for use.

Challenge

The system was rather old and heavy, and every new change introduced by developers caused a bug in the connected functionalities of the solution, making it unusable. We were hired to fix it. Our goal was to ensure that all updates to the code went through, and the product would be stable and reliable for the client’s use. This required meticulous testing of various components within the Windows server desktop solution.

Solution

To tackle this challenge, we employed a comprehensive QA strategy that involved a range of testing activities, such as:

Exploratory testing
Ad hoc testing
UI testing
Functional testing
Confirmation (retesting)
Regression testing
Build verification testing (acceptance testing)

Regression and confirmation testing were performed several times during a project to prevent reappearance of bugs after each new update. By executing regression testing as frequently as the code changed, we were able to catch recurring issues early in the development cycle and address them before releasing the updates to the client.

We also did a bit of automated testing using the Ranorex tool for writing test suites. However, most of the testing was executed manually to ensure thorough coverage and accuracy. The project spanned across MySQL servers and AWS and underwent rigorous testing for almost a year.

Through the project, we closely collaborated with developers and product managers. This helped us stay on the same page and ensure that any issues that arose during testing were promptly addressed and resolved. The team chose Skype for communication. Other tools we used for collaboration are Jira, where we tracked bugs and TestRail for writing down test cases.

In general, the composition of the team on our end included six testers and a Team Lead who worked part-time.

Technologies

MySQL servers
Ranorex
Chrome
Firefox
Edge
Internet Explorer 11

Result

Through our QA efforts, we successfully stabilized the software. The client received a robust product that worked smoothly and fully met their requirements. As of today, they have already come back to us twice with other projects, and we’re anticipating more interesting opportunities to collaborate in the future.

We Work With

Having one outside team deal with every aspect of quality assurance on your software project saves you time and money on creating an in-house QA department. We have dedicated testing engineers with years of experience, and here is what they can help you with.

Software is everywhere around us, and it’s essential for your testing team to be familiar with all the various types and platforms software can come with. In 21+ years, our QA team has tested every type of software there is, and here are some of their specialties.

There are dozens of different types of testing, but it takes a team of experts to know which ones are relevant to your software project and how to include them in the testing strategy the right way. These are just some of the testing types our QA engineers excel in.

The success of a software project depends, among other things, on whether it’s the right fit for the industry it’s in. And that is true not just for the development stage, but also for QA. Different industry have different software requirements, and our team knows all about them.

Full-Cycle Services

By Platform

By Type

Industries