Quality Delivery

navigate IT projects safely

Both when launching and during the expedition into the digital vastness, you should make sure that your ship can cope with the imponderables of the rough sea and that irreparable leaks do not occur at the crucial moment.

Product quality tests during the development process and quality assurance are topics that are becoming more and more important due to the complexity of modern software but are often underestimated. To ensure product stability and quality, it is important to integrate quality assurance measures into the development process as early as possible. Companies with a pronounced quality awareness and knowledge of the corresponding methods and tools have a clear competitive advantage over their competitors – and happy stakeholders.

our solution

One problem with establishing a coherent product development process is that many different companies with varying ideas about quality work together. The result is often a more or less well functioning compromise. We offer you a holistic approach with qualified and committed employees who are well experienced in development, testing and consulting – all from one source. In this way, a consistently high standard is guaranteed along the entire value chain. We help to introduce and develop a quality-driven mindset that is lived accordingly.

Your advantages

test management (planning, execution, release and reporting) from one provider

highly motivated, qualified and experienced test managers

training and experience in classical and agile test management

coaching of test methodology and quality by experienced test managers with the appropriate soft skills

presence on site and support off-/nearshore by qualified partners if required

focus on partnership, goal- and solution-oriented collaboration

partners and products

Jira is designed to enable all members of your software team to plan, track and release great software.

aqua – the software that makes IT projects successful. Modern test management, requirements & error management. Simple, audit-proof & efficient. Works hand in hand with Jira.

Manage your software testing and IT quality management with unified processes to deliver applications faster and with greater confidence.

Flexible and DevOps optimized ALM software and solutions that enable you to deliver business innovation software faster and with better quality.

The International Software Testing Qualifications Board is a non-profit certification authority for software testers, and our test managers are trained to its standards.


frequently asked questions

What is a regression test?

  • Is usually performed after updates or enhancements (modifications)
  • Verification that modifications in already existing and tested parts of the software do not cause errors
  • Typically performed at the end of a development cycle
  • To be well suited for automation, test cases should be repeatable and stable

What is a test concept?

  • A document in which the test planning for one or more projects is defined
  • Orientation of or compliance with the company-wide test strategy and guidelines
  • Determination of the test scope and possible risks as well as the test objectives (What is to be achieved with tests?)
  • Definition of the test procedure, test levels as well as test entry and end criteria
  • Definition of the contents to be tested, the roles (testers) with associated test activities as well as metrics for the evaluation of the test results
  • A test concept can be structured according to ISO 29119-3

What does a test manager do?

  • Contact person and coordinator between test team, project management and other stakeholders
  • Creation and, if necessary, review of a test strategy for the company
  • Planning of test activities (approach, estimation of resources and risks)
  • Coordination of the test teams
  • Preparation of test status and final reports as well as reports to PL and other stakeholders
  • Focus on strategic level; representation of the test team towards PL and other subprojects

What are the seven principles of testing?

Based on experience, seven guidelines have been derived as principles of testing:

  1. Testing indicates the presence of error states or errors, not their absence
  2. Complete testing is not possible; even extensive tests are random tests with the highest probability of detecting errors
  3. Early testing saves time and money: the later a fault is discovered, the more expensive it is to correct
  4. Error states are distributed according to the frequency principle. A small part of the modules often contains the most errors. Interfaces, migration projects and frequently used areas are particularly prone to errors: approx. 80% of the errors account for 20% of the system.
  5. Repetitions are ineffective: Repeating the same test cases over and over again usually does not cover new errors à Test cases must be checked and adjusted regularly
  6. Testing is context dependent and must be adapted to the system under test: Testing is relative to the required quality level
  7. Caution: Assuming “no errors = usable system” is a fallacy! Is testing at the “right” place or according to the ideas and expectations?

What are automated tests?

  • Automation of test activities, execution of software tests with appropriate tools
  • Test cases are “translated” into machine-readable descriptions (specifications)
  • Especially frequently repeatable and scalable, stable tests such as regression tests are suitable for automation
  • Suitable in principle for all test levels from component to system tests
  • Not a replacement, but a supplement to manual testing
  • Targets: Relief of the testers and increase of the software quality by better test coverage

What is software quality?

  • Describes the quality of a software; ideally fulfils customer requirements regarding functionality, efficiency, usability and transferability
  • Other criteria: Compatibility with other systems or applications, possibility of adaptation, software can be adapted to changing needs
  • Conflicting goals between the criteria, software can not meet all
  • Possible conflicts: efficiency vs. maintainability (=reliability); robustness vs. responsiveness (performance); performance vs. transferability (high performance systems are limited in compatibility/adaptability)
  • Prioritization required: Which characteristics are particularly important for the respective quality requirements?

more about this topic