That test is already disabled because there is no well-defined behaviour for this function when min and max are reversed.  It is not executed during the unit test run.

````DISABLED_```` tells google test not to run that test.

If it's actually worthwhile to specifically define a behaviour (ie. reverse parameters when min > max or something) then we can do that and re-enable the test.  I wasn't sure that was the right thing to do or even that it was helpful.

The code could also call ````PIOS_Assert(max >= min)```` but I can't test that in unit tests.

If you think it makes more sense to just delete that test rather than disabling it, I can do that too.