Closed boulais01 closed 7 months ago
The xml files are getting saved in the input path, which shouldn't inherently conflict with saving them in the user-defined path, but saving them in the path passed in isn't working. Would it make sense to remove the user trying to pass in the file path the xmls are saved on, and just have them pass in true or just add --view-xml or --save-xml?
Currently planning to have this working with test cases by Monday(Dec 4, 2023)
Okay, code is set up, I've just got to figure out test cases now, if I can.
I'm not sure what I can make for test cases, since there are no returns, so I'm going to request review.
@laurennevill When you get the chance, this now has all the necessary reviews.
Contributed to by: Mordred, Sabrina, Miles, Simon
This is intended to resolve issues #31 and #32
Adds functionality to the
analyze
command with the option to give a path to which one will save XML representations of the code/path initially inputCoverage will likely decrease slightly; unfortunately, this code does not return anything and therefore is difficult to test
Currently testing on Windows, Mac, and Linux with running the commands.