Closed Bug 1130460 Opened 11 years ago Closed 8 years ago

Convert Mozmill js test testGoButton.js to a Firefox UI Test

Categories

(Testing :: Firefox UI Tests, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: rbillings, Unassigned)

References

Details

Attachments

(1 file)

This is a replacement for http://hg.mozilla.org/qa/mozmill-tests/file/default/firefox/tests/functional/testAwesomeBar/testGoButton.js This test: 1) Clicks the location bar, types a URL, and clicks the GO button 2) It checks that the URL is opened in the current tab and that the GO button is hidden 3) It checks for the presence of the 'Organisation' element 4) It checks that the URL matches the expected domain name
I changed the steps to remove "Organization", added the mozilla.org url, verified that the url displays after clicking the go button and that the go button no longer displays after being clicked.
Rebecca, is that patch ready for review? If yes, please update the attachment and ask for it. Thanks.
Status: NEW → ASSIGNED
OS: Mac OS X → All
Priority: -- → P1
Hardware: x86 → All
Version: Version 2 → unspecified
I'm unclear what needs to be updated in the attachment, but it is ready for review. Sorry I was unclear on the need to specify that it is ready to review.
Comment on attachment 8560729 [details] https://github.com/mozilla/firefox-ui-tests/pull/74 Ok, then for the future please set the review flag. I will have a look at it tomorrow then.
Attachment #8560729 - Flags: review?(hskupin)
Comment on attachment 8560729 [details] https://github.com/mozilla/firefox-ui-tests/pull/74 (In reply to Rebecca Billings [:rbillings] from comment #0) > 1) Clicks the location bar, types a URL, and clicks the GO button > 2) It checks that the URL is opened in the current tab and that the GO > button is hidden > 3) It checks for the presence of the 'Organisation' element > 4) It checks that the URL matches the expected domain name All of those given steps have not been done yet in this test, so the coverage decreased a lot with the current state of the test. Please see my comments on the PR. I don't think that you have to do check 3) when we have 4).
Attachment #8560729 - Flags: review?(hskupin) → review-
Priority: P1 → P2
Based on your PR comments should I create both a very simple unit test and also the more extensive functional test? The unit test is blocked by bug 865232.
Flags: needinfo?(hskupin)
We might need our isDisplayed method here: http://hg.mozilla.org/qa/mozmill-tests/file/99ae80464f46/lib/utils.js#l385 But you don't have to implement it right now. Just check which of those conditions are met by the go button, and use it directly. Just mark the line as "TODO: use isDisplayed" or such. Yes, please do a unit test for the element type check of the go button. The functional test has to be equivalent to the Mozmill test then.
Flags: needinfo?(hskupin)
The PR https://github.com/mozilla/firefox-ui-tests/pull/74 is ready for review. Changes: added unit test, added more functional test steps and notes, added go button to locationbar class.
Comment on attachment 8560729 [details] https://github.com/mozilla/firefox-ui-tests/pull/74 When an updated PR is ready for another review please set the review flag on the link attachment so I get the correct notification. Thanks.
Attachment #8560729 - Flags: review?(hskupin)
Comment on attachment 8560729 [details] https://github.com/mozilla/firefox-ui-tests/pull/74 The PR still shows 44 commits on this branch, which still contain all of our latest changes. Please fix that so it only contains commits you did personally. Not sure if you followed my advice I gave yesterday.
Attachment #8560729 - Flags: review?(hskupin) → review-
Comment on attachment 8560729 [details] https://github.com/mozilla/firefox-ui-tests/pull/74 PR has been updated to fix issues and remove extra files
Attachment #8560729 - Flags: review- → review+
Comment on attachment 8560729 [details] https://github.com/mozilla/firefox-ui-tests/pull/74 Rebecca, what you want is to ask for review and not to set r+ yourself. Maybe just wrongly picked the menu item. I will have a look later. Thanks for the update.
Attachment #8560729 - Flags: review+ → review?(hskupin)
Comment on attachment 8560729 [details] https://github.com/mozilla/firefox-ui-tests/pull/74 I made a couple of comments on the PR. It's good to see that you were able to fix the problems you had before, but as seen we are still in a feedback cycle due to all the remaining work to do. Please also note the Travis CI failure with exceeding line lengths. Make sure to wait with the review request until Travis reports green, or ask if you have trouble interpreting the results.
Attachment #8560729 - Flags: review?(hskupin) → feedback+
Comment on attachment 8560729 [details] https://github.com/mozilla/firefox-ui-tests/pull/74 I have updated the PR with all of the fixes for each comment. The travis build failed due to blank lines containing whitespaces- there are no longer any lines which are too long.
Attachment #8560729 - Flags: review- → review?
Comment on attachment 8560729 [details] https://github.com/mozilla/firefox-ui-tests/pull/74 Rebecca, please do not forget to set a proper person as reviewer. Otherwise your request can get lost.
Attachment #8560729 - Flags: review? → review?(hskupin)
Comment on attachment 8560729 [details] https://github.com/mozilla/firefox-ui-tests/pull/74 I gave all my comments on Github, and it looks like there is still a bit of work to do.
Attachment #8560729 - Flags: review?(hskupin) → review-
I don't have time to complete this, so I am removing the "assigned" tag.
Assignee: rbillings → nobody
Status: ASSIGNED → NEW
QA Contact: hskupin
Rebecca, thank you for getting started on this test. Lets see that we can find someone else to continue with it. I will mark the PR as closed, but it will be easy for someone else to pick up the work when necessary.
Product: Mozilla QA → Testing
Marco, is that something we would still need for Firefox UI tests? I believe that is already covered by a mochitest.
Flags: needinfo?(mak77)
browser_locationBarCommand.js seems to cover the go button, I'm not sure it physically checks that the button is visible/hidden... I don't know what is the 'Organisation' element, the identity panel? I think it has its own tests already. We could probably file a bug to improve browser_locationBarCommand.js to check for elements visibility, and wontfix this.
Flags: needinfo?(mak77)
Yes, the `organization` is part of the identity panel, so we should keep it away from this test. I also had a look at the referred mochitest and it synthesizes a mouse click onto the Go button. As such it is an implicit visibility check, and we won't need something else.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: