Isolated mode: only isolate tests that use the robot fixture

[virtuald]

Some tests don't require isolation, we should detect those cases and run them normally to avoid the speed penalty.

[auscompgeek]

We should probably stop autousing the robot fixture then, right?

pyfrc/pyfrc/test_support/pytest_plugin.py

Line 76 in 27fe979

@pytest.fixture(scope="function", autouse=True)

[auscompgeek]

This is a bit of a killer for my team's code. Our unit tests each take noticeably longer to run with --isolated, doubling the total runtime of the tests (from ~14s to ~29s) on my M2 MBP.

[etiennebeaulac]

Not directly related, but I think it would be a great idea to stop using the robot fixture automatically. My team has a number of tests which do not require the robot at all, but even for them, the overhead of creating and destroying the robot is still there. It also creates a number of problems with testing individual components, when you want to use some ports that are used by the robot.