Challenge

The client’s product for this project, a test management tool, was designed to be integrated with Jira and other issue tracking applications. After a series of updates, the client needed to make sure that the updated version of the product could be released and retained all of the functionality users had come to expect. Specifically, our scope of tasks included:

• Verifying the existing functionality
• Checking the presence of all UI elements
• Making sure that each UI element delivers the anticipated response
• Testing the compatibility of the solution with different platforms
• Confirming the correct localization of the product in four new languages
• Ensuring proper integration of the solution with third-party tools

The major challenge of this project was working under strict timeline constraints. For example, our team had to create a large number of test cases (200+) from scratch in a limited time. Another challenge was to plan and test all the possible integrations of the product with third-party solutions.

Solutions

Having collaborated with the client on multiple projects in the past, we were able to build effective collaboration from the start within time constraints. We appreciated the availability of comprehensive documentation that allowed us to quickly get the hang of the features that needed to be tested.

We started by enhancing the existing test suite, making sure that every possible feature of the product is covered by our testing efforts. Then we moved on to following our initial test plan. We also paid special attention to all the possible integrations of the product with third-party services to ensure the correct operation of the solution across all potential combinations.

The team for this project consisted of four manual QAs and one part-time QA lead. The types of testing we performed included:

• Smoke testing
• UI/UX testing
• Functional testing
• Confirmation testing
• Cross-browser testing
• Integration testing

Through weekly meetings with the project stakeholders and the development team, we achieved complete transparency and were able to quickly remove any roadblocks and get timely feedback to move forward with the project.

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.

Solutions

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. 

Challenge

The client contacted us when they were finishing working on another update of their product with a request to perform comprehensive testing of the whole solution, test the tickets supplied by the development team, and then perform complete regression testing of all basic functionality, even if it was not affected by the changes in the code.

One of the main challenges of the project was the fact that the solution works with a large variety of databases (including SQL and MongoDB-based ones), which meant that knowledge of the database technology was integral for testing the product correctly.

Moreover, there were over twenty databases deployed on the client’s side, which sometimes posed an additional challenge for us because we couldn’t quickly access those databases in case there were any hiccups in their operation. Our productive cooperation with the client’s team, including the Product Architect, helped us overcome this challenge by establishing a fast response procedure for these situations.

Solutions

Part of the client’s request was to create new test coverage, which meant we had to write new test cases to ensure that. In the duration of the project, our team created 150+ test cases from scratch, as well as worked with the existing ones.

To overcome the challenge of multiple databases and complex technologies required for all-encompassing testing, we selected members of the team who specifically had experience with databases to work on the project.

The types of testing used on this project included:

• Exploratory testing
• Functional testing
• Regression testing
• Smoke testing
• Build verification testing
• Acceptance testing
• Cross-platform testing

To speed up the testing process, increase test coverage, and improve the efficiency of testing, we employed the services of automation testing engineers. They also helped create and test scenarios that relied on the knowledge of software code to be successful.

In an effort to better meet the client’s technical and business needs, we used a dynamic team setup, expanding and downsizing the team as needed. Overall, the team working on the project consisted of:

• 1 QA Lead
• 5 to 8 Manual QAs at different stages of the project
• 2 Automation QAs

Despite the fact that our testing team and the client’s development team were located in different time zones, we managed to make it work by establishing an effective collaboration process with a combination of synchronous (including weekly calls) and asynchronous communication.

Challenge

By the time the client contacted us for the project, the application had already successfully operated in its home country for several years. However, this year, the company started planning to expand its presence to a new location in the region and decided to update and enhance the original application to better serve customers in the new market. Moreover, the updated application had to fit advanced security requirements, as well as usability and legal regulations, so there was a considerable chunk of work being done by the development team. 

During the initial discussions, the client pointed out the most important aspects of the upcoming testing project. Specifically, they needed an application that had an appealing user interface, delivered spotless functionality and performance, and complied with all security requirements and industry standards of the target market. The client also emphasized how important it was to release the product on time so that user adoption would go over smoothly.

The key challenge of the project was the fact that by nature, financial and banking applications deal with a lot of sensitive information. This is why, in order to protect the integrity of the software, the client designed a complex access control system for the testing team. Another challenge was that the mobile application was still in the active development phase, which meant we often had to test various modules separately without yet knowing how they affected each other’s operation.

Solutions

After getting a clear understanding of the client’s needs and project requirements, and after taking a few days to familiarize ourselves with the product, we immediately set out to work. To shorten the introduction period and start delivering the results faster, we originally engaged a larger team and then gradually scaled it down to better fit the needs of the project.

Given that the mobile application was not yet fully developed, we had to use a dynamic approach to testing: first, we tested everything that was already available to us, and then, as new modules were added to the application, we also tested them individually and together with the whole system. The client did not previously use a bug tracking system, so we suggested our own template and it perfectly fit every party’s needs. The types of testing we used on this project included:

• Functional testing
• Cross-platform testing
• UI/UX testing
• Exploratory testing
• Ad hoc testing
• Confirmation testing
• Regression testing

As is always the case with our testing projects, we made sure to test the solution on physical devices: specifically, we used four different iOS and Android smartphones to see how the app would perform on devices with different hardware characteristics and display sizes.

We communicated with the client through bi-weekly team calls and regular messaging and reporting. Our team also built close cooperation with the client’s development team, which is why we could promptly retest the application after the developers introduced any changes. The QA team on this project consisted of:

• 3 to 5 QA Engineers (at different project stages)
• 1 QA Lead

Solutions

The first part of the challenge — working with an unfamiliar product — was resolved thanks to the existing experience our team members had with the product as a test management solution. As for the second part, the expertise of our Automation QAs helped us manage the existing test cases with maximum efficiency in a limited time period.

To deliver the required scope of testing, we performed functional testing to verify the core functionality of the product, and then we used regression testing to make sure that the recent changes did not have any negative impact on the product. Other types of testing we employed in this project were:

• Acceptance testing
• Security testing
• Performance testing
• Edge case testing

This was also a project where we used both manual and automated testing. We employed automated testing with the help of Selenium to check the consistency and integrity of the test cases created by the previous team working on the project. 

Our team consisted of five QA engineers, including two Automation QAs and a QA Team Lead.

Challenge

Our main challenge was to review and update existing test cases in the scope of this project prior to executing them. We had to review test cases for both bug fixes and smoke verification, check their consistency, and make necessary updates. All of that, including executing those tests and documenting new bugs, had to be done within a short period of time. 

Solutions

Due to the intense project implementation process, the QA activities were attached to the development sprints and strictly planned into limited timeframes. Thanks to the efficient collaboration with the client’s development team and our usage of ready templates for presenting the review results, we’ve managed to complete all necessary activities before the deadline.

Our QA team consisted of: 

• 2 QA engineers
• 1 QA automation engineer
• 1 QA Team Lead

The team effortlessly fit into the client’s operations and performed every single type of testing that was requested from us, including:

• Exploratory testing
• Functional testing
• Smoke testing
• Regression testing
• UI/UX testing
• Confirmation testing
• Cross-browser testing
• Cross-platform testing

The team members would also reach out to the client whenever we had questions or suggestions about the project, and we have always been available in case the client wanted to make additional requests or comments.

Challenge

Shortly before requesting the help of our QA department, the client transferred the code to a new environment, so our ultimate goal was to make sure that the updated solution works as flawlessly as it did before the transfer. Specifically, our team had to do the following:

• Check the UI to determine how enjoyable the user experience is;
• Go through the complete customer journey, from selecting the product to finalizing the order;
• Test the payment functionality with different user scenarios;
• Investigate the way the product works on different platforms (web and mobile).

Moreover, the client reported some search engine optimization-related issues and asked us to perform an SEO audit.

The peculiarity of this project was the initial involvement of several contact points from the customer’s side, including the key stakeholders and specialists from their outsourced development team. QArea team has successfully overcome this challenge by using the best project management practices in our work and keeping quick and transparent communication with the client.

With a clear understanding of what needed to be done, we set out to work on the project.

Solutions

To complete the project and deliver everything expected of us, we did the following:

• Created a checklist for comprehensive testing.
• Wrote test cases for every possible user scenario in close collaboration with the stakeholders.
• Performed several types of testing, including UI/UX, functional, and exploratory, to test all the aspects of the product, even less obvious ones.
• To verify the correct operation of the website on various platforms, we used several different Windows and iOS devices for testing.
• Performed regression testing after bug fixes to make sure that the product was not impacted negatively by the code changes.
• Ran multiple tests with a scanner tool to find SEO-related flaws and possible areas of improvement on the website.

Solutions

We set issue identification and documentation as an essential part of our development process. This would guarantee that all errors are captured, prioritized, and resolved efficiently. Considering all requirements were specified and explicit, we chose Waterfall as a development methodology for the project. 

We used .NET to build four fast, efficient, and secure websites. Our flexible and adaptable UI/UX process allowed us to ensure the website is easy to use, the content is accessible and presented clearly, and the overall layout and color scheme of the website is pleasing to the eye.

We built an effective workflow within the team by making regular communication with the client a priority. Skype, Google Hangouts, and daily email reports were a core part of our work with the client. This effective workflow resulted in four great websites being delivered to the client within the defined time frame and budget. 

Solutions

In the course of development, our team used Python for back end, Angular Universal for front end and Ionic for hybrid mobile app development. We utilized Gitlab tools and effectively configured back end with the mobile applications to ensure the system is easy to use and runs smoothly on every platform requested by our client – Web, Android and iOS. The platform’s functionality includes, but is not limited to one-time password login system, time tracking, job monitoring, vacancy and candidate search engine, employment and settlement mechanisms. We succeeded in implementing all the required functionality for users to enjoy the convenience of every step of the job hunt and employment processes.

Solutions

Based on the business analysis conducted and the client’s feedback, we decided to use Python, React Native, JavaScript, and Figma tools to best meet the technical and design requirements for the project. We utilized our experience in full-cycle software development to build a highly scalable system, which can be easily integrated with new features and third-party service APIs. The app has minimum load time and features seamless navigation. Our experienced betting software developers supercharged the system with impenetrable security to protect the integrity of data stored. Last but not least, we made sure the app is compatible with all the devices listed in the requirements.