Currently, we have no unit tests that ensure that query results are ordered by score.
When we have a query, results are to be noted by score and then id. However, all ordering tests pass even if score-based ordering is not included in the request.
I discovered this as I was working on converting Works Search to use a template. I had not yet added sorting, and the only two tests that failed with the new code were the date order ones.
Currently, we have no unit tests that ensure that query results are ordered by score.
When we have a query, results are to be noted by score and then id. However, all ordering tests pass even if score-based ordering is not included in the request.
I discovered this as I was working on converting Works Search to use a template. I had not yet added sorting, and the only two tests that failed with the new code were the date order ones.