Closed (fixed)
Project:
Search API
Version:
8.x-1.x-dev
Component:
Tests
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
27 Oct 2016 at 12:08 UTC
Updated:
26 Nov 2016 at 09:34 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
niko- commentedComment #3
niko- commentedComment #4
borisson_I don't see why tis is unnecessary. Our tests all seem to pass with it. Not sure if we should do this tbh.
Comment #5
niko- commentedNot sure if this issue is right.
Please check http://prnt.sc/czl160
There is no message "Successfully executed @count pending task." on it.
But in original test we have checked if it available
Comment #6
borisson_In that case, instead of changing the test, we should probably figure out why it's not showing up in your case and fix that.
Comment #7
drunken monkeyHm, no, this indeed seems to fail consistently when the tests are run via the GUI (since that will not use a batch to execute those tasks, thus also not producing that message). Since we afterwards check the number of tracked items, which also asserts that the tasks were executed (whether via batch or directly), I'd say getting rid of that assert really does seem like a sensible option. Or does anyone have a better suggestion?
(We could, of course, skip the assert just when running via the GUI, but I don't think that's a good pattern to fall into.)
Comment #8
drunken monkeyOops, didn't mean to attach that – first created the patch, but then figured out the problem without it anyways.
Comment #9
borisson_Sure, thanks for explaining that @drunken monkey!
Comment #11
drunken monkeyCommitted.
Thanks again for reporting this, niko-!