Tesvan

Overview:
Customertimes (the Salesforce partner) is a system integrator and cloud consulting partner, working on the base of Salesforce API, focused on supplying companies with experienced senior consultants and developers as an extension of their existing teams.

Objective:
Performing Manual testing both for Web and Mobile applications
Implementing test automation for Mobile application (IOS)

Challenge:
Installations were the only challenging part for our team.

Solution:
For our project, we chose the most appropriate version of the main testing tool, which perfectly met our requirements.

Result:
Full test coverage of the Web app. About 300 automated test cases at the moment.

Project Overview

ThetaRay is transforming the way financial institutions and payment service providers (PSPs) benefit from data with an AI-based SaaS transaction monitoring solution. The growing volume of global money transfers, including online and app-based payments, requires banks and PSPs to deploy sophisticated solutions to identify financial crimes, including money laundering, fraud, and terrorist financing. The full-stack solution deploys big data expertise and proprietary algorithm science to deliver the best of machine learning along with unbiased use of rules, maximizing efficiency to find anomalies with virtually no false positives.

Objectives

•  Planing and performing Manual testing
•  Automating test cases
•  Performing Regression testing
•  Realizing Smoke testing
•  Covering the whole functionality by UI/API testing

Challenge

Working on this project we had to deal with multiple anomalies in transactions. Here it is important to be extremely attentive to them in order to find and separate anomalies properly so that they could then pass through different procedures.

Our Solution

Writing exact test cases we can identify anomalies among all the transactions. The cases we write don’t let AI/ML confuse anomalies and standard alerts and reduce the risk of any possible negative impacts on the overall system.

Project Overview

Mysterium Network is meant to build a global decentralized network of residential IPs. Becoming a node in Mysterium Network, you share your IP address (anonymously) and spare bandwidth in order to help power the free internet. A Mysterium Node can be run both as a "provider" and a "consumer" of VPN services on Mysterium Network. In provider mode, Mysterium Node is offering VPN service to the network in exchange for payments.

Objectives

•  Creating a user-side documentation
•  Communicating with users and supporting them in case of any problem
•  Checking applications both from user and client sides
•  Reproducing bugs and creating issues
•  Making sure that Node always works correctly on different platforms
•  Checking process of top-up and transaction

Challenge

For the QA engineer of the Tesvan team who is in charge of this project’s testing, it was the first experience of working with cryptocurrencies. Even having enough knowledge about cryptocurrencies and the system it was really challenging to take this on. Besides that here we had to deal with multiple payment methods which were also new and required a deep understanding of them.

Our Solution

To overcome all the challenges we had to do deep investigations to better get into the project and also keep thorough communication with the team to discuss all misunderstandings and fill the lack of needed information.

Project Overview

Vicoland is based on Ronald Coase’s theory on the nature of the firm which says that organizing work in firms makes sense when to-dos are too complex to organize them through market exchanges. Applied to professional services this has meant traditionally: tasks can go to freelancers, projects go-to firms. Such an approach has become a necessity and an opportunity.

Objectives

• Planing and performing Manual testing
• Implementing test cases for features about being created

Challenge

During our working process, we have to create and implement test cases for some features which don’t exist and are just on their way of being created. This is a real challenge for our team which we overcame successfully.

Our Solution

We have to explore deeply all the info having under our hands and discuss all the points with corresponding people on the team and in order to be guided correctly and be able to write the right test cases.

Results

This is what we got as a result: 

•  Writing test cases in advance we could manage the working process properly and save much time.

Overview:
We relied on our hands-on experience with both white box and black box testing and draw on our experience with automated testing tools. Our QA worked on optimizing the existing Gherkin scenarios.

Objective:

• To create detailed,well-structured test plans
• To estimate, prioritize, plan, and coordinate testing activities
• To design, develop and execute automation scripts
• To perform thorough regression testing when bugs are resolved

Challenge:
The role requires advanced infrastructure knowledge, Linux system administration and debugging skills on RH, Debian variants.

Solution:
We relied on our hands-on experience with both white box and black box testing and draw on our experience with automated testing tools.

Result:
Automated test scripts, regression testing.

Project Overview

LegalAtoms breaks down legal cases preparation into a simple guided experience through a series of questions. At every step, you'll see precise info from court officials and lawyers.  Once you're ready you can e-file your documents with a few clicks, all while saving thousands in fees. 

Objectives

•  Knowledge of both Cypress and GitHub which we’d had ample experience with.
•  Familiarity with AWS and CircleCI. We had to brush up our skills on these.

Challenge

The forms were really big with dynamically added elements and Angular magic:) Plus, the initial tests were written in Typescript so we had to switch to it from the more habitual Javascript. It took some learning curve and overtime hours to bring our test scenarios to the level of pre-existing, finely designed framework on top of Cypress. Eventually, we adapted to the style and added some recursive functions to traverse the web elements and fill in randomly generated data with minimal code.

Our Solution

We had to think in Typescript which was challenging at first but the challenges were offset by catching the test code issues at compile time and leveraged types and interfaces of Typescript. We developed a fast response routine by setting up email alerts in CircleCI when tests failed on Cypress Dashboard. Our test suite grew and morphed in accordance with the changes in the underlying functionality being tested.

Project Overview

The client represents a marking agency which automates ad placement in various social platforms. The product lets advertisers manage large number of ads from a single dashboard. When the client approached us they had no testing processes in place. The lead architect did the testing before the releases himself. That led to some nasty issues slipping through and going into production website unnoticed.

Objectives

•  Review and analyze system specifications
•  Execute test cases (manual or automated) and analyze results
•  Create logs to document testing phases and defects
•  Report bugs and errors to development teams
•  Help troubleshoot issues
•  Conduct post-release/ post-implementation testing
•  Automate test execution

Challenge

We needed to test websites across multiple platforms, operating systems and geo-locations. The main challenge was to identify quality assurance process bottleneck and suggest actions for improvement. The deliverables were screenshots and/or video recordings of found problems with explanation on how to re-create them.

Our Solution

Our response to this challenge was to own and specialize in specific areas of complex testing. Our QA assigned to this role was the primary point of contact for specific features between our testers and internal development team of our partners. Our QA learned to utilize the tools used internally within our partner’s team to assist with test cases and sales testing. He also backed up QA Lead by assisting with reports, scrums and communication.

Results

After writing thorough test cases that covers the possible testing scenarios including the edge cases we started automated the regression suite with Selenium + Python. We did a little experiment and incorporated “Screenplay” design pattern into our testing which performed surprisingly well both from organizational and performance standpoints.

•  Automated the regression testing and ensured quality practices are built into the SDLC and DevOps practices.
•  Reviewed, analyzed and documented business and user requirements for technology product development.
•  Ensured that business requirements are fully met before each release; certified releases for quality and completeness of functionality.
•  Developed and implemented testing practices and tools as part of the framework which ensure releases are defect-free and perform at or better than expected levels.

Project Overview

A mobile game for pre-school kids available for IOS and Android. Our job involved: testing the game in a systematic way, analyzing the game's performance against the designer's intentions, identifying and reporting problems, and suggesting improvements. However, it also involved creativity and ingenuity, which is used to figure how to ‘break’ the game in different and unique ways. In effect, we acted as the game's first audience by reporting on playability and identifying any aspects that could be improved.

Objectives

•  Categorize and prioritize bugs
•  Develop software quality management system
•  Anticipate different ways the game will be played by people around the world

Challenge

Testing involved playing the same game repeatedly for weeks at a time, testing different levels and versions or revisions of the game. Sometimes, different teams were responsible for specific sections or areas of a game. The work could be repetitive and tedious; however, we were able to stay motivated and test the game long after the novelty and fun factor may have worn off. We had to accept that we had only limited influence over the design and worked methodically on testing within the constrains we faced.

Our Solution

Given our understanding of game design, how games are created, and how the different elements of a game contribute to the playing experience we were able not only identify and record a problem, but also try to work out what is causing it. By honing our communication skills with other members of the team across the world we had them onboard when we came up with our solutions to the testing challenges. Our engineer responsible for QA’ing this project could maintain concentration while playing games for long periods of time because of his passion for playing games.

Results

The game was launched on App Store and Google Play market after successful beta testing.

•  A better user experience for in-app purchases
•  Smooth UX across a wide range of phones and tablets
•  Software quality management system to document finding and maintain a change log

Project Overview

ScaleGrid creates advanced database management products for open source databases. Easily deploy, monitor, backup and scale MySQL, PostgreSQL, Greenplum®, Redis™ and MongoDB® database with a few simple clicks.

Objectives

• Create detailed, comprehensive and well-structured test plans and test cases
• Estimate, prioritize, plan, and coordinate testing activities
• Design, develop and execute automation scripts using open source tools
• Identify, record, document thoroughly and track bugs
•  Perform thorough regression testing when bugs are resolved

Challenge

The role requires advanced infrastructure knowledge, Linux system administration and debugging skills on RH and Debian variants. We needed to delve deeper into Vagrant, LXC / LXD containers and understand and test how database clusters are created, imported, updated, backed up and deleted in various Linux distribution images like Ubuntu, Debian, Centos. And then the testing automation needs to be cross-platform and test the relevant releases of DBs coming from various vendors

Our Solution

To solve these testing challenges we relied on our hands-on experience with both white box and black box testing and draw on our experience with automated testing tools. Our QA worked on optimizing the existing Gherkin scenarios. We used high-level scenario steps to better reflect the business logic make sense for all the stakeholders while performing low-level system interactions on the implementation side. The automated testing workflow looks like this: first we create a feature testing branch from the repo’s main branch, then we start working on the tests by building on the top of NodeJs infrastructure (cucumber.js, chimps.js, javascript). After local tests the code gets pushed on Github and Jenkins picks up the changes, build and runs the tests. We get a report with the results and drill down into any issues revealed by the tests.

Project Overview

Celeb TV is an adult live streaming service where you can interact and share with thousands of social celebrities from around the world. This service provides exclusive access to private celebrity photos and videos, and facilitates direct connection with the models via messaging and video chat. Celeb TV’s products rank in top 35 in Alexa, serve 50 million users daily, operate 2,000 servers and 6 data centers. 

Objectives

•  Cary out full range of software testing activities (functional, structural, manual, automated tests)
•  Design, develop, run and improve automated tests
•  Possibility to work with multiple technologies:  JavaScript, CodeceptJS, Selenium
•  Participate in Requirement and Functional Specification reviews of new features to convert them to comprehensive Test Specifications
•  Document, troubleshoot and follow-up on issues found during testing
•  Report, prioritize, track, and manage deficiencies
•  Mentor other testers

Challenge

The system under test is really complex and multi-faceted. In addition to that we had to pick up an automated testing framework that was altogether new to us - CodeceptJS. Moreover, the existing testing framework was geared to both mobile and web testing and we had to account for that as well. Another challenge is the multi-step pipeline leading to the deployment to production. We had to gain deeper understanding into how Bamboo works and how the configuration change from one environment to another.

Our Solution

In parallel with manually testing the live streaming service we actively engaged in learning how CodeceptJS works also relying on the excellent video and presentation materials provided by the company. Through communication with the long-time employees who worked on the framework we were able be up and running in no matter of time. Our QA engineer responsible for the project participated in KT sessions and Scrum ceremonies seamlessly integrating with the company culture. Also worth mentioning is that we brought in our broad knowledge of testing tools, methodologies and automated testing processes that helped tackle the challenges.

Results

The work is still ongoing but we already achieved some results we can share.

•  More estimated points are closed for testing tasks sprint over sprint
•  Increased test coverage
•  Clearer testing scope definition
•  Keep track of and own team quality metrics that drive QA targets
•  Established post-release testing routine

Project Overview

Staffidoo project creates a platform for managing organization staff. It gives opportunity to administer the roles of the staff member as well as to organize them according to the departments in which they work. This platform gives chance to make surveys and queries for the staff members and to create statistics according to the answers the workers give.

Objectives

•  Create test framework from scratch
•  Automate functional test cases
•  Report bugs and improvements
•  Create final bug report with detailed description (attached screenshots and screen recordings)
•  Perform regression testing after new releases and bug fixes

Challenge

It was essential to have technical skills to accurately design and maintain test automation framework and test scripts, build solutions, and resolve technical issues. Automated testing resources needed to have strong knowledge of framework’s design and implementation.

Our Solution

Our QA engineer responsible for this project was able to thoroughly analyze the project, understand the requirements and all possible challenges that could arise during the automation testing process, which helped us design and maintain compatible automation framework from scratch.

Results

Here are some results we achieved

•  Increased test coverage
•  Detailed knowledge of working with Jira
•  Improved skills of creating automation test framework from scratch
•  Improved skills of doing regression testing

Project Overview

Billidoo project is designed to administer the paying process of staff members bills and invoices. It gave company’s staff members chance to upload their invoices regarding company’s expenses and get refunding from company. The project managed only specific categories of invoices which could be refunded by the company.

Objectives

•  Prioritize and plan testing activities
•  Automate functional test cases
•  Report bugs with detailed information in Jira
•  Create final bug report with detailed description (attached screenshots and screen recordings)
•  Perform regression testing

Challenge

It was required to make the test plans and tests cases understandable as much as possible for staff members not very closely familiar with code. Our challenge was to create test framework which made our test cases look clean and comprehensible, meanwhile not lose their functionality and stability.

Our Solution

We decided to implement our test cases using “Cucumber” which is a behavior-driven development tool designed to make the test cases easily comprehensible even for people who do not have thorough knowledge of code. We rewrote out Mocha test cases to make them Cucumber based which helped our client to review our tests more easily.

Results

We are happy to announce some of the results we achieved by overcoming the challenges

•  Deep knowledge of Cucumber tool
•  Understanding BDD approach
•  Improved skills of creating automation test framework
•  Improved skills of doing smoke and regression testing

Project Overview

Funkgeraete is an online shop website designed to sale and rent radios and related bundles. It has separate modules for products, cart, checkout and payments. Funkgeraete shop website was administrated by the admin side, which gave opportunity to publish and configure product information which appeared on shop website.

Objectives

•  Thoroughly analyze and understand test flows from admin to shop side
•  Automate functional test cases
•  Report and follow-up bugs found during testing process
•  Perform regression testing after newly implemented features

Challenge

The shop website required thorough knowledge of working with product process and final order bill. It required usage of JS mathematic functions to generate correct final price for each product.

Our Solution

We researched and analyzed JS mathematic functions and found those suitable for each case. We adopted those functions to be suitable for German price format. Using already existing functionalities we created our own functions designed for specific project.

Results

Some results we achieved are:

• Experience in working with website admin side
• Improved skills of creating Cucumber automation test framework
• Improved skills of doing smoke and regression testing
• Skills of documenting and following-up on issues found during testing

Overview:
Rocky mountain sewing and vacuum is an online shop for sewing machines.

Objective:
Perform Continuous integration and continuous delivery testing

Challenge:
The only challenge we have faced during our testing process, was the lack of documentation.

Solution:
As we didn't have detailed documentation to follow, we discuss and clarify all the essential parts of working process with our team during daily stand-ups.

Result:
System functionality is covered by automated test scripts.

Project Overview

Rental Radio (RR) is a very comprehensive project designed to administer the process of receiving and forming sale and rental orders for radio products and bundles. Being a very complex project, it had wide range of configuration settings related to user account management, shipping or billing addresses as well as payment information.

Objectives

•  Develop and implement automated test scenarios for complex modules
•  Analyze and prioritize the feature of the project to be tested
•  Develop automated test framework from scratch
•  Document all implemented test scenarios
•  Implement automated test scenarios based all already written manual tests cases

Challenge

One of the challenges that was arisen when working on RR project was the necessity to prioritize the features of the website without any specific documentation and requirements. Our team was required to estimate all features and create Jira tasks for tests based on those estimations.

Our Solution

To solve the above-mentioned challenge, we started our working week with analyzing and prioritizing all of the features that has not been tested yet. Our team created their own Jira tickets, guaranteeing that all features and workflows are prioritized and implemented as expected. Thorough research and understanding of Jira Kanban board helped us manage the arisen challenge.

Project Overview

Fleet Management is a software package for managing the structure of radio stations and repeaters operating in the MOTOTRBO® Capacity Plus environment at a company site. This application comes with a pre-configured server and supposed to be working directly at the customer’s site being connected to the main repeater and a radio station.

Objectives

•  Develop automated test framework from scratch based on specified requirements
•  Create Initial Test planning document
•  Create final Test Report document
•  Create final bug report with detailed description

Challenge

Some functions of the website require connection with a network cable to a network switch to which the main repeater is connected, so those functions would be unavailable without connection to the radio station. Unfortunately, our team did not have access to that station which made some key functionalities unavailable for us.

Our Solution

Our team was able to successfully integrate Mock Server in order to have access to all functionalities of the website. This gave us chance to carry out full range of software testing activities and cover all workflows of the website.

Results

We've got some results

•  Improvement of the existing documentation
•  Mock Server integration
•  Analysis and prioritization of main features and workflows
•  Increased test coverage

Project Overview

Etisalat is a telecommunications company providing services in many countries around the world, using the mobile virtual network operator business model. The purpose of Etisalat was to provide cheap calls to home for emigrants. Etisalat provides pay-as-you-go and contract based mobile SIM cards, offering wide range of mobile bundles, Top-Ups and Bolt-Ons, including recurring orders.

Objectives

•  Analyze workflows for main features
•  Write test cases and test steps using Zephyr for JIRA
•  Execute manual tests using REST/SOAP requests
•  Automate REST API tests in Java

Challenge

Etisalat project consists of multiple microservices which makes it challenging to fully understand the workflows of main features related to product orders, purchases, payments, etc. The project has specific business logic related to telecommunication field as well as online payments using third party tools.

Our Solution

In order to fully perceive the main workflows of the project, at first place, our team concentrated on Knowledge Transfer Sessions and Confluence Articles. Understanding the full flow was a priority for our team, which made the test execution and automation process easier and more effective.

Results

We've got results!

•  The introduction of Postman and SoapUI in the workflow
•  REST API automation with Java
•  Analysis and prioritization of features and workflows
•  The introduction of Zephyr for Jira in the workflow

Project Overview

Ask Finny project is a great platform for those who want to acquire knowledge in the financial field. This platform supports users with quizzes and financial problems, solving which they learn of finance, widen their logical abilities, and have fun.

Objectives

•  Do full manual testing
•  Do full automation testing for functionalities
•  Report bugs and improvements
•  Create final bug report with detailed description (attached screenshots and screen recordings)

Challenge

It was crucial to have deep knowledge of JavaScript and its frameworks for saturated automation testing, also it was essential to have an understanding of production process management tools to maintain project balance. Also, we needed knowledge in testing emails through API, which helped us automate authentication of the page. There was also a bunch of work with databases for which we dealt with database management tools.

Our Solution

Our QA engineer responsible for this project was able to cover all the requirements for this project, understand the possible challenges during the testing process and due to the deep understanding of this field could overcome all the difficulties.

Results

Here's what we achieved

•  Increased test coverage
•  A routine of working with the DB
•  Introduction of production management tools

Project Overview

SlideCamp is a well-designed tool for those who are interested in slide management. It allows users to design slides, edit and categorize them, share, make teams, acquire slide templates, make a presentation, and so on.

Objectives

•  Prioritize and plan testing activities
•  Automate functional test cases
•  Report bugs with detailed information
•  Do automated visual testing

Challenge

It was required to do thorough functional and visual testing for both client and admin profiles of users. It was significant to create detailed test cases for this project and maintain the stability of the tests.

Our Solution

We decided to create our test cases with a comprehensive Page Object Model, which helped to have understandable tests both for us and the client. We also implemented visual testing, which helped to make the web page not only perfect with its functionality but also with the visual part.

Results

And we were glad with what we came up with

• Thorough testing coverage with Cypress
• Functional testing suite expansion
• New smoke and regression tests
• Advanced visual testing

Project Overview

In All Media is a cutting-edge technology and innovation consulting organization, facilitating digital transformation in multiple industries. In All Media harnesses the collaborative synergy of the international talent pool using Agile methodologies, to deliver excellence efficiently and with the utmost quality. In All Media brings together a globally managed community, with experts guiding and managing talented engineers; working to bring together the best talent in the world, regardless of where they are. This makes In All Media a truly global company driven by a community of dedicated, talented individuals self-organizing into multi-disciplinary teams, producing the best possible output for our world-class clients.

Objectives

•  Planing and performing Manual testing
•  Automating test cases
•  Covering the functionality by UI/API testing

Challenge

While working on this project we faced difficulties related to set-ups, as there were many specific tools to be installed that we didn’t deal with before which demanded another approach than other tools.

Our Solution

We spent enough time on inverstigations and could do all needed set-ups on time.

Results

This is what we got as a result:

•  Increased test coverage
•  Experience with working with DB
•  Proficiency using management tools