EpicEditor QA Guide

First - Browser Test Suite

First, run the browser test suite on IE9, Chrome, and Firefox minimum. Any failures in IE9, Chrome, or Firefox mean the release cannot go out and you can stop testing and just report the failures.

Second - Functional and Regression testing

Some things you just cant test with a spec. For these things, you will want to run through all of these in IE9, Chrome, and Firefox. Any failures here doesn't mean the release can't go out, but need to be marked as a bug. If something is bad enough (i.e. you can't type in the editor, or there's a JS error), we'll stop the release.

• Type in the editor
• Preview what you typed
• Paste the EpicEditor README.md file and make sure it previews correctly
• Fullscreen from the editor and close. Make sure it closes into edit mode.
• Fullscreen from the previewer and close. Make sure it closes into the preview mode.
• Type <h2>test</h2>, preview, go back to edit and make sure it still says <h2>test</h2>. Reload the page and make sure it's still the same too.