With Code Checker, it is just a right click away in RDI when using the Arcad DevOps Suite, or it can be a stand-alone install with an eclipse client. Regardless, the functions stay the same, with the server running on IBM i or Windows.
Before moving on to unit testing, just a few more key points on Code Checker:
- Supports multiple IBM i languages such as the RPG’s, COBOL, CL, and SQL Support
- Pipeline and automation friendly
- Loaded with preconfigure rules to get you start
I know, code quality may not fall under the true definition of testing, although it plays an integral part to ensure you have a solid code foundation but security violation checking does since the impact to Production can be enormous.
Arcad’s iUnit for unit testing again slides right into the Shift Left, Fail Fast methodology. This allows your developers to test the modules and procedures without having completed the entire program. So, whether you code in RPG, COBOL, or even CL, iUnit has you covered. With its automatic discovery of simple or complex parameters in RPG or its mocking capabilities or the inheritance of JUnit features, it has what you need.
Some of the areas that can be tested include Functions, procedures, Programs, service programs as well as SQL procedures. All this function is available right from RDi and coming soon — a deeper integration into the Skipper Plugin found in the DevOps Suite. This new feature will allow right click access to unit testing.
With the inheritance of JUnit features, this is yet another way Arcad encourages new developers from the Open System world to step into the RPG world and the IBM i. Since it has the JUnit feel, it also hooks right into the automation pipeline with Jenkins, if so desired. Personally, I find that being able to test modules on the fly to be the best result for fast results.
Regression Testing with Verifier
To round out the testing phase comes regression testing. How do you ensure that previously developed and testing applications still performs the same after a change? This testing usually falls on a QA department or just as often falls on whomever is available. With Arcad’s Verifier, you can run both manual or automated tests across a single scenario or a campaign to handle multiple areas. The question comes around, which scenario do you run? With Verifier, it builds an ongoing cross-reference repository to determine which scenario to run. If you change program PGM001, any scenario and campaign that runs against that program will be highlighted or selected to run. This feature alone can save you time, which will save you money in the end. Verifier handles both 5250 and Spooled File comparisons, which is nice, but it digs into the DB2 on IBM i to show file and field level differences. With the DB2 on IBM i review, the use of tools like Selenium can be used to ensure that the data entered and processed at the web entry is what is expected within the backend DB2 database. You can even compare a 5250 entry to a Selenium captured entry just to help identify any errors in the processing aspect of the application. In addition, it tests for differences in the UI as well. And its supports both batch and interactive jobs. As the pipeline flows closer to deployment, regression testing will be that last line of defense against any defects making it into production, including finding issues because of a modernization project.
The final word: CT in the CI/CD
The main objectives to incorporating Continuous Testing in CI/CD workflow:
- “Shift left’ and find issues as early as possible.
- Move from a manual to an automated process to ensure consistency, auditability, and scalability.
- Drive an agile development process.
We have discussed three major areas to the testing pipeline each of which is covered by an Arcad solution. The ‘bonus’ here is these products can function in an existing Arcad DevOps pipeline or be added to existing development pipeline as stand-alone installations.
If you are looking at this and wondering, where do I start, the easiest answer is what need do you have? You don’t need to implement in a specific order. Find the problem area and we can help map a solution. Happy Testing!
And you thought we were done. Did you know you can also pull information from these tools to reflect in a Dashboard? Sometimes this can help see the larger picture. Below are just a few samples of what can be derived from the Arcad VSM Dashboard in conjunction with the testing suite of tools.
Figure 1 - Code Checker via Dashboard
Figure 2 - Verifier via Jenkins and Dashboard
Now feel free to run off and test, test, and test.