More than 30 types of tests detect all the defects and thus improve your software quality.
More than 150 employees optimize the software quality of our customers on a daily basis.
In 94 % of the projects we implement automated software tests

Uncover defects in your software before your customers do

Eliminate defects early on. It reduces costs and the duration of the project or efforts in agile sprints.

The later a defect is discovered, the more expensive and time-consuming it is to fix. The earlier a defect is found in the development process, the less expensive it is to fix.

Thanks to early and high-quality software testing:

  • Avoid unforeseen extra work and costs
  • Make your budget transparent and calculable
  • Bring your product to market on time
  • Increase customer loyalty

We can support you in every phase of your project with the following software tests.

  • Functional test
  • Automated
    functional test
  • Manual functional test
  • Load and performance test
  • Functional test

    Functional test

    • End-2-End Testing / GUI Level / System Testing - This category includes automated and manual functional testing

    • Integration test / interface test - Complex software frequently has various interfaces that can serve both internal communication with other components (component integration) or exchange of information with other systems (system integration). The integration test ensures that the interfaces have been implemented correctly and that communication takes place as defined.

    • Components / Module / Unit Test - In the component test, the smallest parts of a software parts of a software package that can be tested on their own. These are often individual classes and their methods. Ideally, unit tests are implemented directly by the developer first within a test-driven development, to get quick feedback on the basic functionality.

    • Regression test - A regression test describes the process of a repetitive test with a previously previously defined set of test cases. This is intended to ensure that the system functions as desired and, in particular and, in particular, that no new defects have crept into previously functioning areas as a result of previously functioning areas as a result of changes to the software. The more regression tests are available, the more more certain one can be of the quality of its software. In the best case the regression test is accomplished after every change to the software, but at least at the end of a development phase. Due to the high expenditure with manual execution of a regression test, here an automation of the appropriate test cases offers itself of the corresponding test cases.

    • Error retest - If a defect has been detected in the system, this is usually followed by debugging and finally troubleshooting. At this point, however, it can happen that the attempt of the error removal fails, but the development is unaware of it. For this reason, a defect that is reported as "fixed" should be subjected to a retest. If the previous defect can no longer be reproduced as previously reported, it is considered to be fixed. Otherwise it is reported back to the development.

    • Acceptance test - An acceptance test or acceptance test is usually carried out by the client to check whether all agreed criteria have been met and whether the software meets the expectations. In order to avoid unpleasant surprises, it offers itself to check this in the a preliminary test. This can be done, for example, as part of an alpha or beta test. It is particularly important that the test is simulated under real operating conditions.

  • Automated
    functional test

    Automated
    functional test

    • Automated Web Test - The automated web test focuses on checking the functionality of a web application. From predefined requirements or user stories test cases are derived with the help of test design procedures and valid candidates are selected for automation. These test cases check important functionalities or entire process flows in order to prove the correct behaviour of the software. As the scope of the software grows, automated tests can also identify side effects and detect undesirable behaviour.

    • Automated Mobile Test - In automated mobile testing, one of the main goals is to run the automated test cases on different mobile devices and operating systems and operating system versions. The high number of different devices and operating system versions makes a manual test very time-consuming. Since the software to be tested almost always looks the same on all devices versions of the same operating system, an automated test is the best solution here. automated test is the best solution. This can then be carried out on different devices in parallel and thus saves a lot of time.

    • Automated fat client test - To reduce recurring test efforts and to quickly and reliably detect side effects of changes that were made, one should develop an automated test cases for the fat client software. It allows to quickly check the desired functionality at any point of the development process without having to resort to ad hoc additional forces. On the one hand, this helps to build trust in the system developed, on the other hand, it relieves the development team, as relevant problems can be detected promptly and thus be solved in a cost- and time-efficient manner.

  • Manual functional test

    Manual functional test

    • Manual test - The manual test can be divided into different sub-disciplines. sub-disciplines. When one speaks of a "classic" manual test, one often refers to checklist-based tests. are meant. This means that the testers are given a fixed test sequence, carry it out and draw attention to possible deviations in TARGET / ACTUAL comparisons. Special disciplines of manual testing are, for example, explorative testing or usability testing.

    • Exploratory test - The exploratory test is a special discipline in the field of manual testing, when test planning, test execution and documentation take place at the same time. There is usually a so-called test charter for the test objectives and possible test ideas. Exploratory testing can be a powerful tool to uncover defects away from the "happy path" and is thus an ideal complement to structural tests and test automation. The success of explorative tests depends largely on the intuition and experience of the tester.

  • Load and performance test

    Load and performance test

    • Performance test - Performance tests are used to examine individual methods or use cases to determine whether response times, throughput and resource consumption correspond to the performance goals of the application or system. Performance tests can be carried out in the development process as soon as individual components of the system are available.

    • Load test - Load tests are used to determine the behaviour of a system or an application under the conditions of workloads to be expected in production operation. Performance characteristics such as speed or stability within the planned resources are tested.

    • Stress test - Stress tests are used to examine the system behaviour under workload conditions beyond those expected in production operation, and validate performance characteristics. In addition to excessively high load, there are other typical conditions that can be investigated, such as limited memory, insufficient hard disk space or server failure. Stress tests are used to determine under which conditions an application fails, how it fails and which indicators can be monitored to warn of impending failure.

    • Capacity test - The capacity of a system is the total workload that it can handle without violating predetermined key performance acceptance criteria. Capacity testing is conducted in conjunction with capacity planning, which is used to plan for future growth, e.g. for a larger user base or a larger volume of data. In order to cope with future loads they need to know, for example, how many additional resources (e.g. processor capacity, memory usage, disk capacity or network bandwidth) will be required.

    • Long-term test - A long-term test is designed to test the performance characteristics or validate the performance characteristics of the product under test over an extended period of time. During long-term tests the application is workload over a longer period of time, that allows to detects defects that would have remained undetected over a shorter period of time, such as memory leaks.

As individual as your project.

On hourly basis

We support you on an hourly, daily or monthly basis with an individual number of experts.

  • Individual enhancement of your team
  • Quickly scalable within 2 business days
  • All the consultants are certified by iSQI
Learn more

Managed Services

We take responsibility and management for your software testing and scale both the expert team and the infrastructure automation.

  • Full project focus due to reduced workload
  • Better control over time and budget
  • Low effort and high scalability
Learn more
If you want to train your employees: We offer individual training and certification for your team on-site or online.

For companies from different industries with different challenges.

For companies that rely on IT infrastructure.

Internet companies, stores, banks, insurance companies, media companies, etc.

For holding companies and corporations

For complex technological processes and a strong focus on quality

For companies which development transparency is

indispensable for compliance with standards, laws and licenses

What problem can we solve for you?

Please write us a short email, and we will get back to you promptly.

By clicking the button, you consent to the processing of your personal data and our privacy policy.
Tel: +49 221 4744 1010 · E-Mail: info@andagon.com
Tom Noll
Tom Noll
Yana Gogoll
Yana Gogoll

Your free Check-Up

We help you evaluate existing risks and determine the actual level of quality assurance in your company.

After the check-up you will receive
Individual Evaluation
of the essential QA areas of your software
Recommendations
for a fast and effective improvement based on the check-up results
+ all documents as PDF to your email inbox
Your contact details
By clicking the button, you consent to the processing of your personal data and our privacy policy.
Anne Kathrin Wilk
Anne Kathrin Wilk

Find the right specialists for your project.

Please briefly describe your request. We look forward to contacting you promptly to discuss further details.

Your request
By clicking the button, you consent to the processing of your personal data and our privacy policy.
Tom Noll
Tom Noll

We take over the responsibility and management for your software testing.

Please give us a brief description of your request. We look forward to contacting you promptly to discuss further details.

Your request
By clicking the button, you consent to the processing of your personal data and our privacy policy.