The reasoning, explained at Aviation Week, was that Lockheed Martin couldn't put together enough units [F-35s - gvb] in that configuration to run the Block 2B OUE in time.
The Block 2B tests were also impacted by restrictions imposed after a June 2013 engine failure in an F-35A unit. That impacted software tests, because the restricted flying hours “reduced the number of accessible test points”.
It looks like there are not enough F-35s in the correct configuration to run the tests. Unfortunately, this is typical of all programs I've been involved in in my career - software development gets starved for hardware and software test gets screwed over for lack of both hardware and software. The reason is simple: hardware is first in the timeline, software is second and gets hammered by hardware slips, and test is last and gets nailed by both hardware and software slips.
Nowadays, software can make a lot of progress on surrogate development systems, but software/hardware integration and software/hardware test still requires real hardware.