Change Details

Background: - Visual editor tests are notoriously difficult to write, requiring several separate, but coordinated, complex data structures to be filled out by hand. Although we've documented the crude process, it's still a chore. - Visual editor already includes a powerful debug toolbar which includes many tools for introspecting the document being edited and VE internal data structures. If it were possible to automate the creation of test cases given a real document and any in-progress edits (called "transactions" in VE), this would be helpful to developers. The debug tooling within VE could be a great fit for this exact task.

Background: - Visual editor converter tests working on the border between VE and Parsoid are notoriously difficult to write, requiring several separate, but coordinated, complex data structures to be filled out by hand. Although we've documented the crude process, it's still a chore. - Visual editor already includes a powerful debug toolbar which includes many tools for introspecting the document being edited and VE internal data structures. If it were possible to automate the creation of test cases given a real document and any in-progress edits (called "transactions" in VE), this would be helpful to developers. The debug tooling within VE could be a great fit for this exact task.

Background: - Visual editor testsconverter tests working on the border between VE and Parsoid are notoriously difficult to write, requiring several separate, but coordinated, complex data structures to be filled out by hand. Although we've documented the crude process, it's still a chore. - Visual editor already includes a powerful debug toolbar which includes many tools for introspecting the document being edited and VE internal data structures. If it were possible to automate the creation of test cases given a real document and any in-progress edits (called "transactions" in VE), this would be helpful to developers. The debug tooling within VE could be a great fit for this exact task.