For reasons lost in the mists of time, your project has a code coverage standard. Unfortunately, some new code has gone in which takes the coverage below this figure. John Doe is duly assigned to write more tests (since Jane Doe is off snowboarding). John is unfamiliar with the code and drags the coverage over the line by calling various constructors and methods with mocks. None of these adhere to the accepted given... when... then... pattern and so the purpose of the new test code is hard to ascertain.
Leaving aside the rights and wrongs of:
a) A code coverage figure
b) The tests not being written at the same time as the code
Do the new tests constitute technical debt? What should be done about them (if anything)?