I need help with this question. We are tasked to write unit tests for each method in the Annulus class as stated in the question. How will I solve such a problem? I need to create an implementation file called TestAnnulus.cpp that will be used to test the Annulus class and its methods. The lab with the URL can ONLY be accessed internally. Please delete the previous question as it was incomplete. This is the complete version.

Thank you for your help

4. Determine what tests you will need to create. a. What methods need to be tested? i. You are to test all of the public methods of the concrete classes, except for the following: 1. destructors 2. constructors of exceptions b. What are the equivalence partitions for the methods? i. What are the "normal" cases? ii. What are the "error" cases? c. What are the boundary conditions? 5. Iteratively write unit tests (i.e. write tests for each class in a method-by-method fashion). a. Start by writing unit tests that pass for the "clean" library (libshapes-clean . a) which is intended to be bug-free. This will help to make sure that you don't have any problems with your unit tests. b. There are 7 unique and intentional implementation bugs in the "buggy" library (libshapes-bugs.a) and your unit tests should identify as many of them as you can. i. If a unit test passes for the "clean" library but fails for the "buggy" library, then you can be sure that you found one of the seeded bugs. These bugs must be reported by creating an issue on your assignment repository When you find bugs, the build pipeline will look like this: us.h [f? 757 bytes