It feels like this should be in a setUp or tearDown method to happen before/after all tests - otherwise, if something unexpectedly increments the counter (i.e. in a test where you haven't anticipated that and reset it), it'll affect other tests.