Removes the usage of testify.Suite from the codebase.
Motivation and context
Using testify is ok however multiple community resources discourage the usage of the Suite resources.
After considering the tradeoffs, I decided to remove all the usages of testify.Suite from the library.
How has this been tested?
Please describe in detail how you tested your changes.
Include details of your testing environment, and the tests you ran to
see how your change affects other areas of the code, etc.
[x] Unit tests added / updated
[x] The tests run on docker (using make test)
[ ] The required test data has been added / updated
Types of changes
What types of changes does your code introduce? Put an x in all the boxes that apply:
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] This change requires a documentation update
Checklist
Go over all the following points, and put an x in all the boxes that apply.
Please, please, please, don't send your pull request until all of the boxes are ticked. Once your pull request is created, it will trigger a build on our continuous integration server to make sure your tests and code style pass.
Description
Removes the usage of
testify.Suitefrom the codebase.Motivation and context
Using
testifyis ok however multiple community resources discourage the usage of theSuiteresources.After considering the tradeoffs, I decided to remove all the usages of
testify.Suitefrom the library.How has this been tested?
Please describe in detail how you tested your changes.
Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc.
make test)test datahas been added / updatedTypes of changes
What types of changes does your code introduce? Put an
xin all the boxes that apply:Checklist
Go over all the following points, and put an
xin all the boxes that apply.Please, please, please, don't send your pull request until all of the boxes are ticked. Once your pull request is created, it will trigger a build on our continuous integration server to make sure your tests and code style pass.