Testing Notes for QDP

TestPlan.md

Test Plan: QDP

Functional Testing

Drag and drop images to the RTE Field

Given I have the quick detail panel open
When I drag an image to a RTE field
Then the image should be added to the "artifact 
And displayed inline in the RTE field

Copy and paste content from a word document

Given the quick detail panel is open
When I copy content from a word document
Then the content should be pasted
And and the formatting maintained

Content pasted from QDP should look the same in the EDP

Verify large files are not excepted

Once implemented in Sombrero

• Verify that it is added to the demo page
• Visual tests are in place where it makes sense
• Unit tests are written
• Component usage in sombrero is documented
• It can it be used on other pages?

URL’s

• I should be able to add a url
• I can paste a url
• I can copy a url
• I should be able to update a url
• The link should be formatted in an easy to read fashion i.e. named link
  • Can include a link in any RTE Field
  • Can be displayed as text
• When I click on the link It should be opened in my default browser Should it open in a new tab or should it open in a new window?
• If the link is a Agile Central link
  • Should open in rally in a manner that does not lose my work? (editing a QDP page)
  • Should it be any different?

Templates

• Verify existing templates are displayed correctly
• Verify that current template functionality is maintained
• Create a new template

Backend Testing

• Verify that data pasted or constructed in the editor arrives intact to the database
• Validate that metrics are captured and can be found

Performance Testing

• Adding multiple RTE fields to a page does not decrease performance
• Test how much time it adds to page load

Load Testing

• Loading large amounts of formatted text from an existing story should be performant
• Swapping between items in a grid type view should be performant
• Paste 32 page’s of word document in to the Panel
  • Does the performance degrade

Security Testing

• Block and sandboxing of script tags
• I am assuming that CK editor is heavily tested
• How ever testing our use of it for security flaws will be neccessary
• Verify permission of data
• Should follow all existing rules. for current RTE

Automation

• Automated smoke test for the feature

Infrastructure

• Should easily flow into the build system
• Current GUI tests should be fixed and pass

Open Questions

• Are replacing the RTE everywhere ?

  • Isn't this really a field type as well?
  • Should it work as such for custom fields

• Are we testing Accessibility?

  • Verify a user can perform formatting functions using only keyboard nav
  • Verify using Safari with Voice over is reasonable

• Undo? are we implementing it ?

  • Undo would add another level of functional testing

• Where is the editor going to show up in the application?

• What about existing functionality of the link clicking?

• When is UX planning to review styling?

  • Will there be cycle and testing for that

• Should we have a global button to toggle the QDPanel

• Maintenance how do we update and what is the schedule?

  • How can we make sure the editor doesn't rot.