akrennmair/newsbeuter — pull request #137 by ahitrin (2014-05-24 15:05:44+00:00)
Title: Already read items still appear in search results as unread

Newsbeuter is pretty and very useful for me, but, unfortunately, it suffers from some small bugs. One of this bugs annoys me very much. It can be reproduced very easily:

* start a search in an RSS feed
* read some articles
* quit search
* run new search

And voila! You can see your read articles **again**, marked as _unread_, among with other articles that are relevant to the search string.

I tried hard to create working UI test that demonstrates this, and after all, here it is. Here I start a search that finds two articles (31), read one of these articles (39), reset a search (45) and start a new one (56). After that I expect that already read item should not be shown (60). But it is.

Here is a test log:

I: On (1,3), found `1 N Aug 30 212 |RSS 2.0 testbed f| RSS 2.0 Item 1' as expected.
I: On (1,3), found `1 Aug 30 212 |RSS 2.0 testbed f| RSS 2.0 Item 1' as expected.
I: On (2,3), found `2 N Aug 28 170 |RSS 2.0 testbed f| RSS 2.0 Item 3' as expected.
E: On (1,3), expected `1 N Aug 28 170 |RSS 2.0 testbed f| RSS 2.0 Item 3', but found `1 N Aug 30 212 |RSS 2.0 testbed f| RSS 2.0 Item 1'

Unfortunately, I'm not able to fix this issue yet, but I hope that working test could help identify root cause of this issue, Therefore, I just provide a test at this time. I hope this issue could be fixed!