Software Quality Assurance and Testing

Our Software Quality Assurance and Testing approach includes a clearly defined set of rules and processes that promote consistency, communication and transparency

We provide QA and Testing services to help you create high-quality products satisfying the needs of your users within a predictable schedule and budget


Archer's Quality Assurance department provides all types of Software Quality Assurance and Testing: we select test methods and relevant level of testing taking into account all aspects of the specific project environment, product requirements and quality criteria so the process is efficient.

The Quality Assurance and Testing is important for producing the qualitative, engaging and stable products. Everyday our team is improving the expertise in Quality Assurance to implement it in the projects we are developing for healthcare, automotive, fintech and other industries.

Our procedure complies with the ISO 9001:2015 quality standard and follows the Project Management Body of Knowledge (PMBOK).


Improve customers and users satisfaction
Accelerate new features time-to-market
Reduce number of issues and bugs
Lower stress for all parties involved in development
Ensure errorless deployment and minimize conflicts
Increase the product quality with every release

We help startups and enterprises digitalize healthcare, automotive and fintech

years on the market
professionals on the team
delivered custom products
global high-tech clients

Our Software Quality Assurance Team

SQA team is guided by software quality assurance plan which includes all types of testing necessary to ensure the product quality within the Software Development Life Cycle – from detection of design and programming errors, prevention of infrastructure errors and infrastructure improvement, to software quality management.
Quality Assurance Analyst
Creates product acceptance criteria and monitors the SQA implications and practices over the whole software development cycle
Quality Assurance Engineer
Monitors and tests software through the stage of development.
Quality Control Manager
Develops E2E tests and API tests, monitors project architecture development over E2E, API tests
Test Automation Engineer
Creates programs to automate the SQA process and compare predicted results with the real outcome

Are you satisfied with the quality and security of your software?

Outsourcing Quality Assurance can make your product more reliable, user-friendly and consistent with customer requirements while accelerating your releases by 10 to 15% and cutting costs.


Quality Assurance not merely makes the product better when built from scratch, it becomes even more important in the later stages when the system architecture gets complex and many interdependencies have to be taken into account.

QA Engineer starts to work closely with the Business Analyst at the requirements gathering stage to define the relevant testing methods, make a rough estimate of the number of hours, the team and environment required for testing the project, assess risks and get the basis for building future Quality Assurance and Control process.
Requirements analysis
We gather the 'wish-list' of features and user scenarios from stakeholders and translate it to the clear, detailed and measurable system requirements
Test planning
We define the scope of the project and the approach to testing the basic functionality of the software and put it together with the description
Test development
We define the objectives and plan the tests that will provide a clear evaluation of the features' performance and correct work and if they fulfill the user's expectations that were defined in the requirements
Test execution
We run the manual and automated tests that were planned to compare the expected outcome with the actual one and compile the data for future analysis
Test reporting
We draft a special document that helps the stakeholders track the progress of the testing activities and provides an overview of the current state and quality of the product development
Test result analysis
We compare the outcomes of the tests with the user scenarios that the team of Business Analysts has included in the requirements and outline the discrepancies
Defect Retesting
We run the failed tests once again after the bugs are fixed to make sure that all the discrepancies are covered with quality code and all the requirements are met
Regression testing
As the product grows we do the regression testing with every new release to make sure that new features do not conflict or damage the older ones and user experience remains satisfactory
Test Closure
We keep track of every error and bug that was found and fixed during the testing and create a comprehensive document with an overview of the complete testing process for future reference


When the development phase launches the QA team then proceeds to test the developed functionality until the product release and afterward to ensure smooth user experience.
Functional testing
Non-Functional Testing
Software testing against the functional requirements/specifications
  • Unit testing
  • Integration testing
  • System testing
  • Sanity testing
  • Smoke testing
  • Interface testing
  • Regression testing
  • Beta/Acceptance testing
Software testing of non-functional aspects: performance, usability, reliability, etc.
  • Performance Testing
  • Load testing
  • Stress testing
  • Volume testing
  • Security testing
  • Compatibility testing
  • Install testing
  • Recovery testing
  • Reliability testing
  • Usability testing
  • Compliance testing
  • Localization testing
We've accumulated an enormous knowledge database to help you set up smooth QA process and deliver engaging, stable and reliable solutions


Test Plan
Describes the whole range of works on testing, discovery and description of objects, strategies, search, criteria for starting and ending testing, to the required amount of work, equipment, special knowledge, as well as risk assessment with options for resolving
Mind Map
Displays the connections in the application, functionality, parameters, as well as the permissible values of these parameters
Test Case & Test Suite
Defines the sequence of actions by which the Quality Assurance specialist can check whether the function under test meets the established requirements
Traceability Matrix
Visualises the number of functional requirements covered with test cases
Check List
Includes a list of minimally detailed test cases, sufficient to reproduce a script for testing functionality
Bug/Defects Report
Describes the situation or sequence of actions that led to the incorrect operation of the test object, indicating the reasons and the expected result


What technologies does Archer use for Test Automation?
We have been using Selenium WebDriver + JUnit for automation purposes for almost every web-project we have delivered. In some projects Selenium has been replaced by PhantomJS.

We use POM (Page Object Model) for writing non-brittle test code and reduce or eliminate duplicating test code and improve readability.

For performance and stress testing we use the following technologies:
  • SoapUI/LoadUI - for quick scenario or scheduled tests;
  • JMeter - for more detailed scenarios and information gathering;
  • Watir and Siculi for Flash projects;
  • Galen framework for testing adaptive layout.
What is Software Quality Control?
Software Quality Control focuses on the documented specifications and the technology employed. It verifies that the application works as documented by testing the logical design and the technology itself. It also ensures that the application meets the documented technical specifications and deliverables.

This level of testing usually requires thorough the test, to be provided to the tester, who then can simply verify that for a given input, the output value (or behavior), either "is" or "is not" the same as the expected value specified in the test docs.
Quality Assurance vs Quality Control
Sometimes people may confuse the term quality assurance with quality control (QC). These two concepts have common features, yet there are important distinctions between them.

QA deals with the overall guidelines used in development process to ensure a product meets specified requirements, and QC is production-focused and deals primarily with inspections and checks to find out defects and bugs.

In terms of software development, the role of software quality assurance (SQA) is to prevent malfunctioning code or products, while the role of QC is testing, troubleshooting and fixing code.


Made on