Add RPGUnit test case and test suite generation

[SanjulaGanepola]

Changes

Add RPGUnit test case and test suite generation

TODO:

• Handle all types
• Handle nested structs
• Handle when test file exists and test case is generated
• Can we not generate prototypes if they already exist?

Checklist

• have tested my change
• have added myself to the contributors' list in the README

[worksofliam]

Liam to move getReturns into parser and write test cases for it.

[SanjulaGanepola]

Got it working with most of the common types. Generates a test that passes!

I'm going to add a bunch of new tests to verify all the APIs I added here work properly. I will do this outside this PR so we can at least still get this in. This is ready for review. Could we get a release out once it is merged?

[worksofliam]

@SanjulaGanepola I am looking but codeActions.ts has a lot of conflicts. I think it might be worth you looking at this so I am not to break anything.

[SanjulaGanepola]

@worksofliam Conflicts gone. Ready for review

[worksofliam]

Really a simple change. I would like this to generate POSIX paths with single quotes around it.

[worksofliam]

I think some logic needs to happen for uniqueIncludes.

If uniqueInclude is a POSIX path (IFS/local), then please use single quotes around the /copy//include path:

/include 'qrpgleref/empdet.rpgleinc'

And to confirm, members should use this format:

/include qrpgleref,empdet

[SanjulaGanepola]

I update the PR to add single quotes. In general, test case generation for members and even IFS files won't work yet given how the file creation is currently implemented. Thus, I haven't made the change to fix the includes for members. I added it to this TODO list (#383) so I can make that change outside this PR.

[worksofliam]

@SanjulaGanepola Just additional non-requirement for this PR: there are a lot of new functions for this test action in codeActions.ts. Perhaps down the line we should put all the 'create test' specifics into a unique file.

[SanjulaGanepola]

Perhaps down the line we should put all the 'create test' specifics into a unique file.

@worksofliam Yes I agree. Added to the TODO list!