Our approach to Testing & QA
Our optimum QA strategy relies on good taught strategies, therefore in QA testing we pay attention to
one thing at
a time, use regression test, report and track bugs, leverage analytics, use unit and integration tests
last but not
least focus on the UI.
When it comes to requirements review, we have a thorough analysis of determining user expectations
consideration. These should be quantifiable and detailed. The requirement analysis serves as a
foundation for test &
project plan, it is also an agreement between developer & customer, it is a process to have clear
validating these for completeness, unambiguity and feasibility.
Plan, estimate and prioritize QA activities
You can’t move forward without a well thought plan. Our experience in this domain proved that test
planning is an
essential part of software testing, no matter the size of the project or the team. A test plan
keeps testing in line with overall project goals, and keeps everything on schedule.
Create test cases and well organised test plans
We use test cases in order to set instructions on ‘HOW’ to validate a particular test objective or
target, which can be
useful when testing the expected behavior of the system. First we define test plans and organize
runs, we execute
them and capture the results providing real-time insights, reports 7 & charts.
Set up the environment and prepare the test data
In order to ensure a successful software testing we always set up the right testing environment. If
step is not
well envisioned it could reflect later into extra cost and time to the client. We do not want that
Report and track defects
We rely on defect reports because they are meant to provide vital information for application
staff, that offer a great insight into the areas of the application that do not work properly. This
effective manner of communicating, tracking and explaining defects to clients, managers and
Manual Test Execution
Test Execution is, without doubt, the most important and ‘happening’ phase in the STLC and also the
lifecycle. The reason is – every team/team member’s contribution and work gets validated here.
We rely on two approaches in test automation: graphical user interface testing - this generates user
interface events &
API driven testing - this uses a programming interface to the application to validate the behavior
Provide reports with the test results
Through test results reports we put at our client’s disposal a summary of test activities and final
results & an
assessment of how well the testing was performed. Using these two documents the client can evaluate
the product was
tested and make a sensible decision regarding the release of the software.
Monitor relevant QA KPIs
We rely on the effectiveness of KPIs when we want to measure the predefined levels of quality through
every stage of
product development. The metrics that really matter: Quality beats quantity!
Some of our QA Tools &
Technologies we use
LambdaTest, Atlassian Confluence, Atlassian JIRA, Atlassian Bamboo, Selenium, Jenkins and Java.
More about us