Try my back-yard: the sprinklers broke and we procrastinated fixing them.

Most software projects functional tests are sequentially executed and don't have intricate failure driven scenarios(not to the extent of a robot on mars). I mean the robot is prone to unpredictable damage on an uneven surface. There is also the issue of signal loss + delay in transmission.

If you are writing code for the transmission engine module for example, would you write test cases for all connected subsystems that might fail? If so, I imagine the dependency between systems probably gets really complicated and almost impossible to remember. So how do you ensure all systems respond and behave correctly in all possible known and unknown failure scenarios.

Edit: I just realized this is no different than writing code for cars. I guess there are protocols in place and as long as your parts conform to the standards, the complexity is reduced.

The yard in the middle of the Atlas Building on the Harwell Campus?

We've been adapting some of the work that the RAL Space team did on the ExoMars Rover for use in farming. We're in London (based in Makerversity atm) if you fancy a chat :)