Test Asset Optimisation Test Asset Optimisation Test Asset Optimisation

We look forward to
hearing from you.

Test Asset Optimisation

Test Asset Optimisation

Focus on effectiveness, efficiency and maintainability

When looking at companies’ testing environments, it is obvious that test assets such as test cases frequently deteriorate over the years. As a result, test execution and test asset maintenance are expensive and the validity of test results is uncertain. The SQS solution Test Asset Optimisation (TAO) changes this by focusing on the test items and cases, restructuring and aligning them effectively and efficiently, so as to make them easy to maintain.

Selecting and optimising test assets

The first step of TAO involves analysing the existing test assets. These test assets are broken down systematically into individual items in accordance with the specification. Test items for the different test stages are identified and assembled in a structured way including assigning the level of criticality and complexity. The existing test cases are then mapped to this new test item structure, and the test cases are further optimised according to the level of criticality. In this way all the test assets are optimised allowing straightforward maintenance and simple completeness checking. Test assets optimised in this way achieve up to 30 % more coverage. This increased coverage leads to significant cost savings, both for manual testing and test automation, through reduced execution / automation effort and simpler maintenance. x

Rearranging test items

SQS uses its proven approach to divide the test process into test stages. Within the test stages the test items are allocated according to the respective part of the software development lifecycle. As the preferred tool set we use our own tool suite, SQS-TEST®/Professional, which allows us to manage the test items, and restructure and redesign the test cases according to our own SQS methodology. x
All test cases for low criticality test items will be restructured. Even where a well-structured template is used, these test cases are usually written in a top-to-bottom manner, and frequently contain much superfluous or wrongly-placed information, which greatly increases the maintenance overhead. Examples include specifying the “login procedure” in multiple scripts, hard-coding environment or release information, and failing to separate the test data from the script. Restructuring the existing assets is much easier than rebuilding them entirely. You merely identify the reusable parts (restructuring), rework the test cases by arranging these parts into a maintainable structure, and remove duplicates. x
Test cases for high criticality test items very often require redesign. The methodology used is the model testing driven approach of equivalence partitioning. This means you can quickly and easily identify which test items are inadequately tested (completeness), and which test items are tested several times (redundancy). The final results are highly maintainable, and the number of test cases is optimised with respect to test coverage. x
Example 1: not good enough
Test cycles at a company are too long and lead to unsatisfactory results. Enormous quantities of unnecessary test cases, test logs and test reports are slowing the process down. Costs are constantly rising and time to market increases with each release.

Example 2: high cost
A company would like to progress from manual to efficient automated testing but is unable to do so cost-effectively. A large number of outdated, not maintainable and unsuitable test assets are blocking progress; test automation is being blamed for high automation costs and a lengthy payback period.

Example 3: redundancy
A company would like to centralize its testing organizations from different countries into a single global testing centre. The aim is to avoid redundancies and ensure that general test cases are not repeated at different sites. In addition, however, regional requirements such as different legal systems are to be taken into consideration. x
  • Total control and transparency as a result of joint work on objectives
  • Increased efficiency due to a reduced number of test cases
  • Cost reduction by means of shorter test cycles and reduced time-to-market
  • Efficient rearrangement of test assets by means of structured and systematic mapping of test cases to test objects
  • Enhanced effectiveness and focus on security- and business critical system components by means of test asset prioritization
  • Avoiding redundancies by centralizing the organization of tests
  • Clear structures facilitate maintenance and extension
  • Improved test coverage at reduced cost
  • Reusability made possible by use of a consistent structure
  • Use and implementation is possible irrespective of manufacturer and format of own tools
  • Efficient results ensured by tried and tested methods, processes, techniques and tools
  • Provides mechanism to migrate efficiently from a manual to automated testing suite

Copyright © 2016 SQS All rights reserved

  • btn_linkedin
  • btn_xing
  • btn_facebook
  • btn_google
  • btn_twitter