574805 - Test case - search results pagination

Status: RESOLVED FIXED

(Testing Graveyard :: WebQA, defect)

Description

[Truman Smith [:truman]]

Attachment: verify search results pagination elements

Selects the 'per page' options in the advanced search panel.  Checks the # of add-ons in the search, values in 'x - y of z results', list footer pagination tabs

Comment 1

[Truman Smith [:truman]]

Attachment: AMOlocators - web page locators - latest updates

Comment 2

[Truman Smith [:truman]]

Attachment: AMOfunctions - reusable code - latest update

Comment 3

[Truman Smith [:truman]]

Attachment: generalFunctions - reusable code that's not AMO specific

Comment 4

[Truman Smith [:truman]]

Attachment: TCparams - test case parameter values

new parameter - maxSelections

Comment 5

[Tanay Gavankar [:tgavankar]]

Comment on attachment 454128 [details]
verify search results pagination elements

When defining expected_count, why do you have page_number-1?

Probably some reason that I overlooked for it, and rest looks good, so r+.

Comment 6

[Truman Smith [:truman]]

(In reply to comment #5)
> (From update of attachment 454128 [details])
> When defining expected_count, why do you have page_number-1?
> 
> Probably some reason that I overlooked for it, and rest looks good, so r+.

The statement is calculating the remaining add-ons that should appear on the last page.  I had intended to simplify the statement after researching modulo or remainder functions in python.

Comment 7

[Tanay Gavankar [:tgavankar]]

Ah ok.

Modulo in Python works like any other programming language. a % b returns the remainder of a/b, so 42 % 20 returns 2.

Comment 8

[Truman Smith [:truman]]

committed to SVN r71467