Quality and Performance Engineering

Why Quality Assurance Matters?

Quality Assurance (QA) activities are crucial for the success of any project and should start simultaneously or even before development, when the first project requirements are specified. Each QA phase includes time for test plan development and for intensive ongoing testing. At the end of each phase, time for stabilization, regression, and post-deployment testing must be reserved.

Another important role of quality assurance engineers is to be internal product owners: have the necessary understanding of the system, which ensures a fully functional testing on the one hand, and development team expertise – on the other.

Our quality assurance services

 Planning
 
Mission, goals, test activities.
 Control
 
Actual progress against the plan.
Analysis and Design
 

◉ Transformation of test activities into test conditions and test scenarios

◉ Designing and prioritizing test scenarios based on Acceptance criteria for the story

Implementation and Execution
 

◉ Manual test execution

◉ Developing automated test scripts

◉ Test environment maintenance

◉ Logging test execution results

◉ Repeating test activities as a result of action taken for each inconsistency

Evaluating Exit Criteria and Reporting
 

◉ Review failed tests: either create bug or update test

◉ Test closure activities

◉ Collection of data from completed test activities to consolidate experience, test ware, facts and numbers

All listed QA activities are repeatable at project milestones, system release, maintenance release etc.

While Performing QA, Raneso Expert Make Sure That:

  • Test coverage of all core functions is close to or equals 100%
  • Existing functionality was not affected by the changes
  • System performance corresponds to the requirements
  • System throughput is not degraded and has enough capacity for growth
  • Extensive testing will be integrated into each development phase

QA metrics

The QA team is responsible for providing management with detailed information about the quality of the developing solution so they can make important decisions regarding the project. Management needs to be equipped with metrics from all aspects of QA.

There are four categories of metrics for functional testing that are typically used by Raneso in the projects:

Automated Testing Metrics
 
This metric indicates a performance (past, present, and future) of the implemented automated testing process and related efforts and artifacts.
It can also be differentiated as: unit test automation and integration or system test automation.
Test Case Metrics
 
Percent of test case execution indicates the progress of testing by giving the percentage of test cases executed with the result of a pass, fail, or blocked result.
Test case pass rate indicates how many tests have passed, grouped by test type, phase tested, and/or functional area.
Defect Metrics
 
Trend analysis indicates the number of open or unresolved defects by date and aids in determining the quality of testing as well as the progress of resolving defects.
Defects by severity indicates the number of defects grouped by severity level.
The number of defects in each level indicates the quality of the solution.
Requirements Metrics
 
Indicate the percentage of tests that have at least one associated requirement.
This metric determines the amount of test coverage for the requirements.

Get in Touch

You can also email us directly at contact@raneso.com