Aelita Technologies - Quality Assurance

Quality Assurance

Aelita Technologies has a dedicated Test Department. All test engineers are assigned to Aelita Technologies projects in the form of test teams as a part of the project team. The test team works in close communication with other sub-teams in the form of meetings, verbal, and e-communication.

The Testing Strategy focuses on answering such questions as:

• Test Project Requirements – each formal requirement will have appropriate test cases on how it can be tested and which approach to use. For example some requirements might be high priority and have to be included into a formal Automated Acceptance Tests, some need a thorough functionality testing and can be done through Test Cases and some requirements might need automation.
• Test Case approach – this approach of testing focuses on product functionality. A preliminary list of Test Cases may be extended when testing is started.
• Automated Acceptance Test approach – this approach means creation of test scripts with step-by-step instructions for testers. The result of each step will be indicated as Passed or Failed. These tests are used for acceptance of candidate builds on corresponding project phases such as Alpha, Beta or RTM.
• Defects Priority - Testing Strategy will also determine descriptions of all Defect Priorities basing on which QA engineers will assign priorities to newly found defects.
• Automation Tools – if there is a need of testing automation this should be explained in Strategy as well as the choice of Automation Tool.
• Testing Configurations (Scenarios) – Testing Strategy contains information against what configurations we plan to test the Application Under Test. Test Configuration is a set of hardware and software components used for testing. Configurations can be assigned for Case Testing, Acceptance Testing or Automated Testing.
• Out of Scope – This strategy contains areas that will be dropped from testing. It also contains a reasons why this or that is not planned to be tested.

During the test designing phase, the Aelita Technologies test team will design a comprehensive plan based on all types of industry-standard test categories:
Function tests, Security tests, Volume tests, Integrity tests, Compatibility tests, Structure tests, Stress tests, Benchmark tests, Contention tests, Load tests, Performance profiles, Configuration tests and Installation tests.

Regression testing is any type of software testing which seeks to uncover regression bugs. Regression bugs occur whenever software functionality that previously worked as desired stops working or no longer works in the same way that was previously planned. As per our policy, regression tests are reviewed for possibility of automation; coding and maintenance time required for automating tests will save manual execution time in future.

Aelita Technologies testers are experienced in using the following test automation tools: Mercury Astra QuickTest, Mercury QuickTest Professional, Mercury WinRunner, Segue SilkTest, Rational Robot. In addition to using special regression tests, it is customary practice to reserve some time in the testing schedule for performing regression re-testing of fixed bugs and re-running additional tests not included in the list of regression tests in accordance of the current project state.