Opened 10 years ago

Closed 9 years ago

Last modified 5 years ago

#9460 closed task (fixed)

[meta] Editor tests

Reported by: bill Owned by: bill
Priority: high Milestone: 1.4
Component: Editor Version: 1.3.0
Keywords: Cc:
Blocked By: Blocking:

Description

I'm planning on checking in a bunch of test files for the editor, so just making a separate ticket to track them all.

Hopefully can use DOH robot to at least test that basic functionality is working, although not sure how to write mouse tests that click over a certain word, etc.

Change History (15)

comment:1 Changed 10 years ago by bill

(In [18424]) Prep to put all the editor tests (not just tests for plugins) into the tests/editor directory.

Refs #9460.

comment:2 Changed 10 years ago by bill

(In [18426]) Move all editor test files to editor/ directory. Refs #9460.

comment:3 Changed 10 years ago by bill

(In [18427]) Initial tests for EnterKeyHandling? plugin in blockNodeForEnter=BR mode on IE.

Includes tests for #9459 and #9462.

Refs #9459, #9460, #9462.

comment:4 Changed 10 years ago by bill

(In [18433]) Remove separate branch for FF initialization. It doesn't seem to be needed anymore. In the old days there was a split because FF was using iframes where other browsers were contentEditable, but now everything is iframes.

Tangentially refs #9460 !strict.

comment:5 Changed 10 years ago by bill

(In [18823]) First robot editor test. Small, but it's a start. Refs #9460.

I'm seeing some timing problems if the machine is running slowly, that the next DOH command will start running before the typeKeys() is finished. Should fix that or maybe increase the delays in this test (as a fudge factor).

comment:6 Changed 10 years ago by bill

(In [18836]) Flesh out Editor a11y test. Refs #9460.

comment:7 Changed 10 years ago by bill

(In [18840]) Normalize IE's Editor so that attr("value") returns text with <b> and <i>, not <strong> and <em>. Makes testing easier and in general, consistency is a good thing.

Refs #9460 !strict.

comment:8 Changed 10 years ago by bill

(In [19112]) Can't run the back/forward state tests on webkit, refs #9460.

comment:9 Changed 10 years ago by bill

(In [20125]) CTRL-rightArrow has slightly different behavior on mac and webkit vs. FF/IE. Test now passes on safari/mac and chrome windows. Refs #9460

comment:10 Changed 10 years ago by bill

Milestone: 1.41.5

This is ongoing...

comment:11 Changed 9 years ago by bill

Milestone: 1.51.4
Resolution: fixed
Status: newclosed

Actually, I filed individual tickets for the remaining editor automated tests. Jared has written most of them already.

comment:12 Changed 8 years ago by bill

(In [23486]) Fix test on Safari. In the "toolbar state" test the initial test (in "setup") was accidentally testing when all the editor text was selected, rather than when no text was selected and the caret was at the beginning of the editor.

Refs #9460.

comment:13 Changed 5 years ago by Bill Keese <bill@…>

In 513200647599abb14740c5faa912737cc3192fc4/dijit:

Error: Processor CommitTicketReference failed
Unsupported version control system "git": Can't find an appropriate component, maybe the corresponding plugin was not enabled? 

comment:14 Changed 5 years ago by Bill Keese <bill@…>

In f130c59e937bf9e71e4fe10f161972d9c1bb3dfd/dijit:

Error: Processor CommitTicketReference failed
Unsupported version control system "git": Can't find an appropriate component, maybe the corresponding plugin was not enabled? 

comment:15 Changed 5 years ago by Bill Keese <bill@…>

In 1383f109e5a26f35c5b318f6c3ef14119676ee4b/dijit:

Error: Processor CommitTicketReference failed
Unsupported version control system "git": Can't find an appropriate component, maybe the corresponding plugin was not enabled? 
Note: See TracTickets for help on using tickets.