Continuous integration and continuous delivery sounds interesting, but it’s not possible without agile, automated testing of your IBM i code. This is especially true if you’re working on a critical application with multiple code structures which need to be tested for security vulnerabilities. How do you enable continuous testing for IBM i development when most automated testing tools don’t understand IBM i code?
Join Andy Finley, Principal Sales Engineer at Rocket Software, for a conversation about how to introduce automated, continuous testing within your IBM i DevOps environment, including:
How to plan ahead for testing, including determining the best approach
Best practices on the what, where, why, and when of testing
How to incorporate DevSecOps into your testing to minimize vulnerabilities