If one or more variables, methods or properties are privately scoped you should focus your test methods on publicly scoped items. And never change scope to accommodate testing.
Now if classes available can be created in a test project, this is what you do along with setting up _timer for one test as 0, another greater than 0.
In regards to DeactivateButtons, assuming this changes say enabled aspect of one or more controls, that can be done without a test method. Simply place a button on the window with only DeactivateButtons and visually see if it works.
Personally, I create a test class then create a folder named base, add another class, same name as the first. Both must have the same namespace and marked as partial, place any code needed to initialize test there.
Add a method as per below which prepares specific test methods if needed.
[TestInitialize]
public void Init()
{
if (TestContext.TestName != nameof(YourTestName)) return;
}
To get an idea of structing a unit test project.