Like most accidents, that A330 crash had a lot of incidental inputs that let to the final result. Reading through the report, I see very little that says anything other than pilot error. They weren't flying it, and initiated a very critical test with the aircraft in an unstable situation.

If the aircraft starts to roll at a speed below Vmca1, I fail to see what else could be causing the roll other than the thrust asymmetry.

Whoever initiated the test had his eye well and truly off the ball, in not ensuring the aircraft was in the correct state for the test..that's basic test flying 101.

As for the presentation of multiple ECAM messages...I'd much rather the system gave me all of them, rather than relying on even more software and programming to sort them out. It's easy enough to get rid of messages, and you can even inhibit them entirely if you want. The problem with all of this is that we already have too much intervention from software, and software engineers, who seem hell bent on teaching me how to fly..even though they have no idea themselves.