Simplicity and efficiency are the predominant factors of this tool
Integrates native green screen 5250
Tests interactive processes
Tests batch processes
Full DataBase integration
DB tables and files identification for images, restore images and comparison are automatically handled.
Tests need to be replicable, which means that the data must be reset each time a test is replayed and many test tools, like ours, include this functionality. But the prerequisite is that all data files or tables are identified first. This prerequisite is often left to the end user or some tools just copy entire libraries with all files and tables. ReplicTest does this automatically on the fly and only for the files and tables actually used by the specific test case.
Automated for batch or interactive programs
The same command is used to process recording or replay of the test case. By default, the command automatically detects in which modality it should run; recording or playback and depending on the modality, different behaviors are processed to copy, restore or compare the image data.
Full UI integration and ease of correction in the recording
UI recording provides a level of flexibility and ease of corrections that is unmatched by other forms of media
For interactive programs, we integrate IBM i ACS (IBM i Client Access) as a plugin to record the all test. A script is generated and unlike live performances, UI recordings allow for errors or mistakes to be easily identified and corrected. It is possible to modify, remove or replace sections of the recording that may be inaccurate or unwanted. This allows for an accurate and fast final test case, and saves a lot of time!
User experience
The user experience is very important, especially on the Recording of the Test case and on the flexibility of correcting the Recording already done. Imagine you’ve recorded a test case of an interactive function involving 30 screens and at the end you realize you’ve entered the wrong data on screen 25…the last thing you want is to redo everything from scratch. The tool enables the flexibility to correct it without having to redo the all recording.
Another relevant point is the code coverage and the merging of code coverage which can be retrieved dynamically through an SQL UDF and also in an automated test driven workflow. The merging of code coverage is a KPI on the quality of the overall test.
Last but not least, spool files can also be integrated within the testing.
Case Study
The tool enables a testing governance of high accuracy in correlation with impact analysis of lines to be changed for specific project like Field Resize.
It is also totally integrable with our DevOps solution.
Empowered code coverage
Create test variations with the same initial data
User friendly and efficient
IDE or DevOps integration
CONTACT US
Get in Touch!
FAQ
What is regression testing?
Regression testing (rarely, non-regression testing) is re-running functional and non-functional tests to ensure that previously developed and tested software still performs as expected after a change. If not, that would be called a regression.
What is end-to-end testing?
End-to-end testing is a software testing methodology that verifies the behavior and functionality of an entire application or system from start to finish. It focuses on testing the flow of data and processes across various components, subsystems, and interfaces, ensuring that the system works as intended and meets the desired requirements. In end-to-end testing, the system is tested as a whole, simulating real-world scenarios and user interactions to validate its functionality, performance, and reliability. It involves testing multiple interconnected modules or components to ensure seamless integration and proper functioning of the complete system.
Why is it often difficult to test an IBM i interactive application with 5250 screens?
Traditional 5250 screens are text-based and lack well-defined user interface elements. This can make it challenging to automate the testing process using conventional image pixel-based UI automation tools. Interacting with 5250 screens often requires emulating terminal input and capturing text-based output, which is automatically provided with our tool ReplicTest.
What is the ROI of testing in a digital transformation project?
In a development process, the test represents at least 20% of the budget and can go up to more than half of the established budget in certain cases.
As for the return on investment (ROI) of testing, this can be substantial in a digital transformation project. While the exact ROI will vary depending on the project and organization, here are several ways testing can contribute to ROI:
Early Issue Identification and Cost Reduction: Testing helps identify defects, bugs, or functional gaps early in the development process. By catching and addressing issues early, organizations can avoid costly rework, minimize the impact on downstream processes, and reduce the overall project costs.
Improved Customer Experience: Digital transformation projects often aim to enhance the customer experience. Through thorough testing, organizations can ensure that the transformed systems, applications, or interfaces provide a seamless, user-friendly experience. This can result in increased customer satisfaction, loyalty, and potentially higher revenue generation.
Reduced Downtime and Business Disruptions: Effective testing minimizes the risk of system failures, downtime, or disruptions during the transformation or after the go-live. By identifying and addressing potential issues in advance, organizations can avoid business interruptions, maintain operational continuity, and prevent revenue loss.
Enhanced System Performance and Scalability: Performance testing and load testing activities help identify and address performance bottlenecks, scalability issues, or potential limitations of the transformed system. Ensuring that the system can handle increased workloads or user demands improves overall system performance, user satisfaction, and the organization’s ability to handle growth.
Compliance and Risk Mitigation: Digital transformation projects often involve compliance with industry regulations, security standards, and data privacy requirements. Effective testing ensures that the transformed system meets these compliance needs, minimizing the risk of regulatory penalties, reputational damage, or legal issues.
Increased Efficiency and Productivity: Thorough testing helps identify areas for process improvement, automation opportunities, or usability enhancements. By streamlining workflows, eliminating manual tasks, and improving system efficiency, organizations can realize productivity gains, cost savings, and improved employee satisfaction.
Reduced Maintenance and Support Costs: Proper testing helps identify and rectify issues before the system goes into production. This can lead to a decrease in post-production support and maintenance costs as fewer defects or issues arise, resulting in improved system stability and reduced ongoing support efforts.
It’s important to note that the ROI of testing in a digital transformation project is influenced by various factors, such as the project’s scale, complexity, industry, and the effectiveness of the testing processes implemented. Organizations should consider these factors when planning and allocating resources for testing, aiming to maximize the ROI and ensure the successful outcome of the transformation project.