TestMatch Modernization Guide
TestMatch is a testing product by Anubex. Explore technical details, modernization strategies, and migration paths below.
Product Overview
TestMatch is a client-based application testing software designed for System z mainframes.
It supports Java, Python, and C#, using HTTP/HTTPS.
Modernization Strategies
Rehost
- Timeline:
- 6-12 months
Lift-and-shift to cloud infrastructure with minimal code changes. Fast migration with lower risk.
Refactor (Recommended)
- Timeline:
- 18-24 months
Optimize application architecture for cloud while preserving business logic. Best ROI long-term.
Replatform
- Timeline:
- 3-5 years
Complete rewrite to cloud-native architecture with microservices and modern tech stack.
Frequently Asked Questions
General
What is TestMatch and what does it do?
TestMatch is designed for testing mainframe applications through 3270 screen interaction. It captures screen data, compares it against expected results, and automates the testing process. It supports various mainframe environments, including z/OS, z/VM, and zVSE/VSEn.
How does TestMatch manage test configurations and parameters?
TestMatch uses configuration files to define test parameters, screen layouts, and expected results. These files specify the application screens to test, the input data to use, and the criteria for determining pass/fail status. The interface allows users to manage and execute tests, review results, and generate reports.
Can TestMatch be integrated with other testing tools?
TestMatch can be integrated with other testing tools and systems through its API. This allows users to incorporate mainframe testing into their overall testing workflow. The API supports various programming languages and protocols, enabling seamless integration with different development environments.
How does TestMatch ensure the security of the testing environment?
TestMatch supports multiple authentication methods, including LDAP and Kerberos, to ensure secure access to the testing environment. It uses an RBAC model to control user permissions and access to test data and configurations. Encryption is used to protect sensitive data during transmission and storage.
Technical
What are the most common commands and operations in TestMatch?
Common operations include defining test cases, capturing screen images, comparing screen data, and automating test execution. The basic syntax involves specifying screen coordinates, input values, and expected output. Configuration files are used to define test parameters and screen layouts.
What types of APIs does TestMatch expose?
TestMatch exposes a REST API for integration with other systems. Specific API endpoint patterns include /testcases, /results, and /executions. Supported programming languages include Java, Python, and C#. Communication protocols include HTTP and HTTPS.
What are the main system components and how do they communicate?
The main system components include the Test Client, Test Server, and Data Repository. These components communicate through TCP/IP. The Data Repository uses a relational database such as DB2 or Oracle. Ports 8080 and 443 are commonly used for communication.
What administrative interfaces are available?
TestMatch provides a web-based GUI for administration. User management is handled through the GUI, with options to create, modify, and delete user accounts. Main configuration parameters include database connection settings, network settings, and security settings. Monitoring and logging capabilities are built-in.
What security features does TestMatch offer?
TestMatch supports authentication methods such as LDAP, SAML 2.0, and X.509 certificates. It uses an RBAC model for access control. Encryption is used for data at rest and in transit. Audit logs track user activity and system events.
Business Value
What is the business value of using TestMatch?
TestMatch automates mainframe application testing, reducing manual effort and improving test coverage. It enables faster release cycles and reduces the risk of errors. The ability to compare test results ensures consistency and accuracy.
How does TestMatch contribute to cost savings and efficiency?
By automating testing, TestMatch reduces the time and resources required for manual testing. This leads to cost savings and improved efficiency. The ability to quickly identify and resolve issues reduces the risk of costly errors in production.
What kind of reporting capabilities does TestMatch offer?
TestMatch provides detailed reports on test results, including pass/fail status, error messages, and performance metrics. These reports help identify areas for improvement and track progress over time. The reports can be customized to meet specific needs.
How does TestMatch integrate with existing systems?
TestMatch integrates with existing development and testing environments, allowing organizations to leverage their existing investments. The API enables seamless integration with other tools and systems, ensuring a smooth workflow.
Security
What authentication methods are supported by TestMatch?
TestMatch supports LDAP, SAML 2.0, and X.509 certificates for authentication. These methods ensure secure access to the testing environment and protect sensitive data. Multi-factor authentication can be enabled for added security.
How does TestMatch control user access to test data?
TestMatch uses an RBAC model to control user access to test data and configurations. Roles are assigned to users, and permissions are granted based on these roles. This ensures that users only have access to the resources they need.
What encryption methods are used by TestMatch?
TestMatch uses encryption to protect sensitive data at rest and in transit. Data is encrypted using AES-256. Secure protocols such as HTTPS are used for communication between components.
What audit and logging capabilities does TestMatch provide?
TestMatch provides audit logs that track user activity and system events. These logs can be used to monitor security and compliance. The logs include information such as user ID, timestamp, and action performed.
Operations
What are the deployment requirements for TestMatch?
TestMatch can be deployed on z/OS, z/VM, and zVSE/VSEn. It requires a relational database such as DB2 or Oracle. The Test Client can be installed on Windows or Linux. Network connectivity is required between the components.
How can I monitor the performance of TestMatch?
TestMatch provides a web-based GUI for monitoring system performance and resource utilization. The GUI displays metrics such as CPU usage, memory usage, and network traffic. Alerts can be configured to notify administrators of potential issues.
What kind of logging capabilities does TestMatch offer?
TestMatch generates detailed logs that track system activity and errors. These logs can be used to troubleshoot issues and identify areas for improvement. The logs can be configured to include different levels of detail.
Can TestMatch be integrated with other monitoring tools?
TestMatch can be integrated with other monitoring tools and systems through its API. This allows users to incorporate mainframe testing into their overall monitoring workflow. The API supports various programming languages and protocols.
Ready to Start Your Migration?
Download our comprehensive migration guide for TestMatch or calculate your ROI.