Once GO has an official package dependency tool, this issue should be quite easy to address.
In the meantime, for testing, we need an assert package. Also, to visually report the test results (in the DevOps pipeline), we need go-junit-report. Hence, the need for this PR.
We are in the middle of an MVP and need this functionality asap.
@jorgedr94 - As we discussed, here's the second PR. In a future PR, we can add more flexibility (for instance, we can make configurable the name of the XML file that includes the test report).
@jorgedr94 - I need to update the test cases... so still work in progress.
Once GO has an official package dependency tool, this issue should be quite easy to address.
In the meantime, for testing, we need an assert package. Also, to visually report the test results (in the DevOps pipeline), we need go-junit-report. Hence, the need for this PR.
We are in the middle of an MVP and need this functionality asap.
@jorgedr94 - As we discussed, here's the second PR. In a future PR, we can add more flexibility (for instance, we can make configurable the name of the XML file that includes the test report).
@jorgedr94 - I need to update the test cases... so still work in progress.