Fix the plugin state restoration test's binary state check never running

The check is documented as running at strictness level 8 and above but
compared the test's own level (6) rather than the run's, so it was
never executed.

Author: drowaudio

CHANGELIST.md

@@ -16,6 +16,7 @@
 - Added a "Discrete parameter state restoration" test (strictness 8) which checks a discrete parameter has the same value after restoring a state, whatever value it held beforehand. This fails for parameters that keep the raw normalised value from the host instead of mapping it to a step (e.g. `juce::AudioParameterBool`)
 - Fixed false failures in the "Plugin state restoration" test where the first parameter was compared against the last value sent by a previous test rather than the plugin's own value
 - Below strictness level 8, two-step (on/off) parameters are now only sent 0 or 1 when tests randomise parameter values. Arbitrary values are still sent to them at level 8 and above, and to all other parameters at every level
+- Fixed the "Plugin state restoration" test's exact binary state comparison never running. It was documented as running at strictness level 8 and above but checked the test's own level instead of the run's
 - Enabled the editor stress and extreme (real-time allocation / oversized block) tests that were present in the source tree but had not been compiled into the build
 
 ### 1.0.5

source/tests/BasicTests.cpp

@@ -398,7 +398,7 @@ struct PluginStateTestRestoration   : public PluginTest
                 parameter->getName(1024) + juce::String(" not restored on setStateInformation"));
         }
 
-        if (strictnessLevel >= 8)
+        if (ut.getOptions().strictnessLevel >= 8)
         {
             // Read state again and compare to what we set
             auto duplicateState = callGetStateInformationOnMessageThreadIfVST3 (instance);