Case Studies

Every project we take on for quality assurance is an exciting challenge. Here are some highlights:

search engine for art

Founded in 2011 Barnebys is a world’s leading search engine for art, antiques and collectibles. It allows their users to have the best experience through web and mobile app.

Barnebys had no testing process in place. When we join we wanted to ensure quality requirements are met. It was challenging due to the big size of the development team, but we set up a testing process. Now as a QA team we can achieve product goals more confidentially.

We started to look out for product quality also through test automation. We deal with great amount of quality challenges every day. Constant development and implementation of automation helps achieving that.

Testing techniques:

  • Performance testing
  • Regression testing
  • Automation testing
  • API testing
Barnebys-min

Online Grocery Shopping in UAE

One of the challenges to face were regression tests – they were present, some scenarios were created, but it was bare minimum. We solved this problem with our experience with exploratory tests – this way we learned how the app works, which areas are the most important ones and most vulnerable after any code changes.

Our client had little to no experience with working with a QA – instead at the beginning they were following their own philosophy, this being ‘introduce changes as quickly as possible’, hence they focused more on development than testing. 

With the proper QA on board this philosophy had to be changed – this was done (indirectly) by finding a lot of bugs they skipped and (mostly) through a lot of conversations during retros and explaining the proper ways to work. As a QA we are responsible for more than just the app, but the whole development process from the beginning to the end.

Testing techniques:

  • Manual testing
  • Automation testing
  • Mobile testing
  • Regression testing

educational content creation in the sciences

It was an unusual projects in 3D technology (Unity). It required a completely different approach (from us) and automation would just not do us any good. Despite having to do a lot of manual work, we were able to overcome this challenge.

Due to the fact that QAs are usually the ones who know the app the best, we were tasked with preparing a proper documentation for both the mobile and the web version of the app. Our choice was Confluence – not only is this a good wiki-like tool, but also due to the integration with Jira.

Testing techniques:

  • Integration testing
  • End-to-End testing
  • Exploratory testing
  • User Acceptance testing
cyber science 3d

SaaS for Auction Houses

While Agile tends to shift away from preparing documentation towards just building a working application, that does not mean there should be no documentation. We took the matter into our own hands by writing down the important information while familiarizing ourselves with the app. This included test cases, test scenarios etc.

By preparing them we make sure nothing is skipped while testing and every functionality is covered (i.e. registration, bidding, payment, shipping, admin panel etc.). 

It’s a good idea to do a thorough regression testing before every release. However, such tests take a lot of time if they are carried out manually, so we provided automation. By writing automated tests scripts we were able to make sure regression tests are always top-notch and that they take a lot less time than manual tests (which can be spend for functional tests).

Testing techniques:

  • Usability testing
  • End-to-End testing
  • Automation testing
  • Manual testing

What's Your Project?