Comprehensive test management solution for complex challenges.
Choose from clearly defined service plans that best suit your situation, and andagon takes care of it. Each package includes binding service level agreements and a transparent service description.
Predictability
No hidden costs for your project.
Risk Reduction
andagon, as an independent entity, assumes responsibility for quality assurance.
Cost Savings
No need for internal resources (expertise and tooling).
Time Savings
Faster time-to-market through early error detection.
Quality Enhancement
Planning and execution by experienced, ISTQB-certified consultants.
Flexibility
Test outsourcing available from just 2 weeks (smallest unit).
Scalability
Test capacity as needed. Avoid bottlenecks.
Transparency
Clear processes, documentation, and dashboards for test progress.
Customer Satisfaction
Enhanced software quality and user experience.
Communication
All consultants are fluent in German and English.
Availability
Over a hundred permanent consultants in Germany, enabling on-site support if needed.
Free Information Session
Our service will be tailored perfectly to your needs through a collaborative discussion.
Team Lead CCQA (Competence Center Quality Assurance), IT-Consultant
Team Lead Hamburg
Of course. Analysis, test concept, test progress reports, and a final test report are essential components of Test as a Service
Click on "Request Now" and inquire about a start date, and we will get back to you within 24 hours. You can also schedule a free information session.
The service is based on standard working hours (40 hours per week). Holidays and other non-working times are added to the 2-week period. For example, if a holiday falls within the 2-week period, that day will be added to the end of the 2 weeks.
To choose the right package, we recommend a no-obligation information session.
No, the test strategy is not included. Test concept and planning are also limited to the work of the TaaS team. We can include the development of a test strategy, but this is offered as a separate service.
No, the package time is fixed and is a minimum of 2 weeks. Within the package time, work can be individually planned with the Test Manager.
No, the time is fully utilized to achieve the best possible test coverage. If the originally planned test scope is completed early, additional test cases will be created or other quality-enhancing measures will be implemented.
If the client provides the necessary supplementary services on time, we guarantee the execution of the number of test cases specified in the package description. The specified number of test cases defines the guaranteed upper limit per service period. Transfer of test cases from one service period to the next due to late provision is not possible.
Generally, yes. Specific services (such as planning or the final test report) can be conducted shortly before or after the service period by arrangement.
Our offer is perfectly tailored to your needs in collaboration with you and customized accordingly.
Test Manager's Role: The Test Manager reviews the requirements for the testing period and estimates the testing effort involved.
Coordination with Stakeholders: The Test Manager clarifies with various stakeholders any necessary services and preconditions for the testing period. .
Test Concept: The estimated testing effort and further planning are compiled into a test concept that defines the timeline for the package.
Test Case Creation: The Agile Tester (AT) creates test cases based on the provided requirements. For the Basic package (1 AT and a 2-week duration), the number of new test cases is capped at 12. If more test cases are expected, an additional Agile Tester must be booked.
Test Case Execution: Once a functional version of the software is available in the testing environment, the AT executes the created test cases.
Defect Management: The AT documents all identified defects and ensures they are retested once a corrected version is available in the testing environment (valid only within the contracted period).
Regression Testing: The AT performs existing regression tests for the application to ensure that new developments haven't impacted existing functionalities. The number of regression tests is capped at 20.
Test Report: The Test Manager prepares a test completion report for the testing period.
Meeting Participation: The Test Manager and AT participate in Scrum meetings (or equivalent) during the testing period and provide suggestions for process optimization.
Management and Communication: The Test Manager oversees the AT during the testing period and serves as the customer’s point of contact.
Scope of Offer: This offer applies to quality assurance for a single development team with one software solution to be tested. If additional teams or multiple software solutions are involved, the effort must be evaluated individually.
Requirement Readiness: Before the testing period begins, all requirements to be developed and tested must be fully prepared and accessible to the Test Manager.
Testing Environment Access: The testing environment and all necessary systems must be accessible to the AT and available throughout the testing period.
Test Data Availability: All test data required for executing test cases must be provided to the AT or be easily generated by the AT.
Software Availability: The software to be tested must be available in the testing environment at the times specified in the planning phase.
Regression Test Cases: All regression test cases must be provided to the AT in a clear format that the AT can execute without deep, customer-specific knowledge.
Technical Contact: A technical contact must be available to address any questions related to the test cases if needed.
Test Manager's Role: The Test Manager reviews the requirements for the testing period and estimates the required testing effort.
Coordination with Stakeholders: The Test Manager coordinates with various stakeholders to clarify necessary services and preconditions for the testing period.
Test Concept: The estimated testing effort and further planning are consolidated into a test concept, which defines the testing timeline for the package.
Test Case Creation: The Agile Tester (AT) creates test cases based on the given requirements. For this package (1 AT and a 2-week duration), the number of new test cases is capped at 12. If more test cases are needed, additional testers must be booked.
Test Case Execution: The AT executes the created test cases once a functional version of the software is available in the test environment.
Defect Management: The AT documents all identified defects and ensures they are retested once a corrected version is available in the test environment (valid only within the contracted period).
Regression Testing: The AT performs existing regression tests to ensure that new developments do not affect existing functionality. The number of regression tests is capped at 20.
Final Report: The Test Manager prepares a final test report for the testing period.
Meeting Participation: The Test Manager and AT participate in Scrum (or equivalent) meetings during the testing period, providing suggestions for process optimization.
Management and Communication: The Test Manager supervises the AT and serves as the customer’s point of contact throughout the testing period.
Scope of Offer: This offer applies to quality assurance within a single development team and one software solution. If additional teams or multiple software solutions are involved, the effort must be evaluated individually.
Requirement Readiness: All requirements to be developed and tested must be ready and accessible to the Test Manager before the testing period begins.
Die Testumgebung und alle weiteren Systeme, die zur Leistungserbringung erforderlich sind, müssen für den AT zugänglich sein und über den Testzeitraum konstant verfügbar sein.
Testing Environment Access: The test environment and all necessary systems must be accessible to the AT and consistently available during the testing period.
Test Data Availability: All test data required for test execution must be provided to the AT or be easily generated by the AT.
Software Availability: The software to be tested must be available in the test environment at the times outlined in the planning.
Regression Test Cases: All regression test cases must be provided to the AT in a clear format, allowing the AT to execute them without deep, customer-specific knowledge.
Technical Contact: A technical contact must be available to address any questions regarding the test cases.
Tool Evaluation: Evaluation of up to two test automation tools, assessing their suitability for automating the test object, with a recommendation provided.
Framework Setup: Establishment of an automation framework designed to create robust, reusable, and low-maintenance test cases.
Test Case Automation: Automation of at least one test case to validate the framework.
Automation of 10 Test Cases: A minimum of 10 test cases will be automated, verified, and executable on the current version of the test object.
Testing Environment: The test environment must have the test automation tool installed and consistently available to the AT during the service period.
Access: The AT must have access to the test environment via Citrix or Remote Desktop.
Licenses: Any necessary licenses for the automation tool must be provided.
Test Data: All test cases must be accompanied by sufficient test data to allow repeated execution.
Software Version: A complete and installed version of the test object must be available, where the test case can be manually executed without errors.
Technical Contact: A technical contact must be available for any questions about the test case.
Maximum Steps: Test cases are limited to a maximum of 15 steps on average. Each step describes a single action, such as clicking a button, navigating (max. 2 clicks), or filling a form (max. 5 fields per step).
Assertions: Each step can include one assertion (check), which must be performed on the current screen. If the assertion requires switching screens, it must be added as a separate test step.
Clarity: All test cases must be understandable and executable without domain knowledge or additional clarification.