In this case, I called my source member test1.rpgle, and right-clicking on it shows me I can create a new Coverage Test. Since we have the Code Coverage extension installed, you can right-click on most types of sources to create a new Coverage Test. To make sure it works, let’s create a source member and then compile it: Make sure the correct library is on your library list. In any modern install of Code Coverage, it is usually installed into QGPL, but sometimes it ends up in QDEVTOOLS. When you’ve got everything installed into Visual Studio Code, you will see a new extension available in the left-most panel:īefore we get started, make sure that the CODECOV command is on your library list. Install the Code Coverage for IBM i extension into Visual Studio Code.If you’re new to Code for IBM i, read our introductory post for installation instructions.I did find this PDF from IBM containing a slide with the PTF requirements. Believe it or not, I couldn’t find a homepage for IBM i Code Coverage from Googling.

After the early access waiting period, we will release it for free to all. How do I install it?Ĭode Coverage for Code for IBM i is currently in early access, available for those who support its development with Code for IBM i Pro subscriptions.

This is exactly what Code for IBM i can do with the Code Coverage extension. This stack overflow answer explains precisely what Code Coverage is:Ĭode coverage is a measurement of how many lines/blocks/arcs of your code are executed while the automated tests are running.Ī good tool will give you not only the percentage of the code that is executed, but also will allow you to drill into the data and see exactly which lines of code were executed during a particular test. This is the second post in my series on RPG and COBOL development using Visual Studio Code and Code for IBM i.

Visual studio code coverage example