Closed Bug 582305 Opened 14 years ago Closed 14 years ago

[mozmill] Create a local form test page

Categories

(Mozilla QA Graveyard :: Mozmill Tests, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: u279076, Unassigned)

References

()

Details

Attachments

(2 files, 6 obsolete files)

This is a tracking bug for creating a local copy of the basic form test page currently used by several Mozmill tests. Please place the files here: litmus-data: firefox/form_manager/form.html mozmill-data: firefox/test-files/form_manager/form.html Remote URL is attached.
Assignee: nobody → aaron.train
Status: NEW → ASSIGNED
Attached patch local form (obsolete) (deleted) — Splinter Review
Attachment #460621 - Flags: review?(anthony.s.hughes)
Let me correct the same identifiers for the elements so we dont need to change the test.
Attachment #460621 - Flags: review?(anthony.s.hughes)
Attached patch local form (obsolete) (deleted) — Splinter Review
Attachment #460621 - Attachment is obsolete: true
Attachment #460627 - Flags: review?(anthony.s.hughes)
Attached patch local form (obsolete) (deleted) — Splinter Review
Missed the submit button
Attachment #460627 - Attachment is obsolete: true
Attachment #460629 - Flags: review?(anthony.s.hughes)
Attachment #460627 - Flags: review?(anthony.s.hughes)
Comment on attachment 460629 [details] [diff] [review] local form Can you please simplify the select box to 5 options? thanks
Attachment #460629 - Flags: review?(anthony.s.hughes) → review-
Attached patch local form (obsolete) (deleted) — Splinter Review
Attachment #460645 - Flags: review?(anthony.s.hughes)
Comment on attachment 460645 [details] [diff] [review] local form Looks good. Over to Henrik for additional review. Please create a follow up patch for litmus-data once he gives the OK.
Attachment #460645 - Flags: review?(hskupin)
Attachment #460645 - Flags: review?(anthony.s.hughes)
Attachment #460645 - Flags: review+
Attachment #460629 - Attachment is obsolete: true
Comment on attachment 460645 [details] [diff] [review] local form Why do we use name instead of id?
Attachment #460645 - Flags: review?(hskupin) → review-
(In reply to comment #8) > Comment on attachment 460645 [details] [diff] [review] > local form > > Why do we use name instead of id? I'm just copying the online version as it's paired with two of the tests in testFormManager.
Lets be consistent and use ids instead.
Attached patch local form (deleted) — Splinter Review
Swapped name with id (tests will need updating)
Attachment #460645 - Attachment is obsolete: true
Attachment #460854 - Flags: review?(anthony.s.hughes)
Attachment #460854 - Flags: review?(hskupin)
Attachment #460854 - Flags: review?(anthony.s.hughes)
Attachment #460854 - Flags: review+
Attachment #460854 - Flags: review?(hskupin) → review+
Whiteboard: [needs landing]
Attached patch local form (litmus-data) (obsolete) (deleted) — Splinter Review
Attachment #461078 - Flags: review?(anthony.s.hughes)
Comment on attachment 461078 [details] [diff] [review] local form (litmus-data) As with the mozmill-data patch, please give the form elements IDs instead of NAMEs.
Attachment #461078 - Flags: review?(anthony.s.hughes) → review-
Attached patch local form (litmus-data) (obsolete) (deleted) — Splinter Review
Doh, was working on the old file. Fixed.
Attachment #461132 - Flags: review?(anthony.s.hughes)
Attachment #461132 - Flags: review?(anthony.s.hughes)
Attached patch local form (litmus-data) (deleted) — Splinter Review
Attachment #461078 - Attachment is obsolete: true
Attachment #461132 - Attachment is obsolete: true
Attachment #461133 - Flags: review?(anthony.s.hughes)
Attachment #461133 - Flags: review?(anthony.s.hughes) → review+
Assignee: aaron.train → nobody
Component: Mozmill → Mozmill Tests
QA Contact: mozmill → mozmilltests
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Whiteboard: [needs landing]
In the form manager test suite we have a test (testAutoCompleteOff) that checks for usage of autocomplete on an input that is presently not available on the current local page. It's presently using Google's search field. Does it seem reasonable for me to duplicate this bug *and* local page *with* the addition of the attribute on the input (perhaps, form_no_autocomplete.html)? Or shall we wait on that test until we have some local search forms?
The intent was to get a set of "lowest hanging fruit" test pages. In other words, to create a basic set of common test pages so we can make the majority of our tests made local. If there is a test module which requires something not covered by these test pages, let's deal with it on a case-by-case basis. I'll be working on the prioritizing this work once 4.0b3 testing is out of the way.
(In reply to comment #18) > In the form manager test suite we have a test (testAutoCompleteOff) that checks > for usage of autocomplete on an input that is presently not available on the > current local page. It's presently using Google's search field. > The test you refer to here actually requires Google (at least for the time being). The test is checking that we do NOT display the normal form autocomplete dropdown on the search box; instead showing Google's Suggestions dropdown. We'd have to create a specialized test page to mimic this behaviour. However, as I stated in my previous comment, let's deal with that on a case-by-case basis.
Move of Mozmill Test related project bugs to newly created components. You can filter out those emails by using "Mozmill-Tests-to-MozillaQA" as criteria.
Product: Testing → Mozilla QA
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: