582779 - Test case - AMO search option for platform

Status: RESOLVED FIXED

(Testing Graveyard :: WebQA, defect)

Description

[Truman Smith [:truman]]

Attachment: add-on search with platform option

Test case does a search using the platform option in the advanced search panel.  It checks that no add-ons in the results have the message 'not available for your platform' when the platform selected in the search is your OS.

A potential problem is that the absence of the message does not necessarily mean success...
1) the message text or locator might change so that TC does not recognize its presence,
2) the message does not normally appear frequently,

To allow a person to do a quick sanity check the TC:
1) Displays all messages near the add-on install button, grouped by OS.  Finding no messages could indicate a problem if the run checked a large number of add-ons.  Finding a new spelling of the 'not available' message might indicate the TC needs to search for a different message. 
2) Checks multiple platform search options.  Finding the 'not available' message for another platform is a good sign.  
3) Prints which platform it thinks that it is running on.  It stops with an exception if it can't determine one.

The code to determine which OS it is running on starts around line 15

Comment 1

[Tanay Gavankar [:tgavankar]]

Comment on attachment 461048 [details]
add-on search with platform option

Rather than have to modify it for each environment for local test runs, maybe we can pull the OS using python for DEFAULT_LOCAL_OS? It's not a necessary change (since we wouldn't be running these tests locally too often), but it would be good for somebody who may be on a non-windows platform when they try to run it and cannot determine why it is failing. Change that if you'd like and commit, modify tests.py. r+

Comment 2

[Truman Smith [:truman]]

(In reply to comment #1)
> Comment on attachment 461048 [details]
> add-on search with platform option
> 
> Rather than have to modify it for each environment for local test runs, maybe
> we can pull the OS using python for DEFAULT_LOCAL_OS? It's not a necessary
> change (since we wouldn't be running these tests locally too often), but it
> would be good for somebody who may be on a non-windows platform when they try
> to run it and cannot determine why it is failing. Change that if you'd like and
> commit, modify tests.py. r+

good idea.

Comment 3

[Truman Smith [:truman]]

commit r72325