Wait till the counter has the desired value, instead of assuming that
the counter already has the expected value. This fixes the tests on
slow browsers.
Furthermore, the wait isn't needed any more, now that the counter
queries are race ondition proof.
The waitForIconMarkReadInvisible was the wrong wait function here, since
the whole article will be hidden instead of the read icon. This could
lead into race condition related errors if the article is hidden before
the waitForIconMarkRead() functions runs. The article variable that is
used to address the child read icon can refer to an (DOM) object which
doesn't exist any longer => StaleElementReferenceException.
The correct wait function in such a case would be waitForArticleInvisible().
- more flexibility and explicitly with the expected dataset
- use radio button to select unittest.db
- add tests:
- previous/next article with arrow key left/right
- no alerts are displayed by default
- alert is displayed on first feed page if feed has parsing error
- keyboard shortcuts are disabled with modifier keys shift, alt and control (except IE)
- display logic on subscription page
