user32/tests: Fix incorrect usage of broken() function.

[Sebastian Lackner]

On 08.09.2016 13:04, Marvin wrote:
> Hi,
> 
> While running your changed tests on Windows, I think I found new failures.
> Being a bot and all I'm not very good at pattern recognition, so I might be
> wrong, but could you please double-check?
> Full results can be found at
> https://testbot.winehq.org/JobDetails.pl?Key=25673
> 
> Your paranoid android.
> 
> 
> === w8 (32 bit msg) ===
> msg.c:15529: Test failed: wrong error 31
> 
> === w864 (32 bit msg) ===
> msg.c:15529: Test failed: wrong error 31
> 
> === w1064 (32 bit msg) ===
> msg.c:13939: Test failed: WM_NCRBUTTONDOWN on caption: 3: the msg sequence is not complete: expected 007b - actual 0000
> msg.c:15529: Test failed: wrong error 31
> 
> === w864 (64 bit msg) ===
> msg.c:15529: Test failed: wrong error 31
> 
> === w1064 (64 bit msg) ===
> msg.c:13939: Test failed: WM_NCRBUTTONDOWN on caption: 3: the msg sequence is not complete: expected 007b - actual 0000
> msg.c:15529: Test failed: wrong error 31
> 
> 

The test failure in line 15529 looks new, I fear you'll have to send an updated
version and catch this error (ERROR_GEN_FAILURE), too.