Skip to content

QA Test Strategy & Plan

Vincent Herilier edited this page Feb 3, 2014 · 8 revisions

Home


Validation of Ares IDE.

Table of content

Strategy

TOP | TOC

This test plan covers the regression tests that the delivered package must pass to validate its delivery

Validation process

TOP | TOC

Pass #1

  • Update current Ares IDE with the last version of Ares IDE
  • Validate Ares IDE with a test set

Pass #2

  • Uninstall Ares IDE
  • Install ARES IDE from scratch
  • Validate Ares IDE with the same test set

Testing target matrix

TOP | TOC

Due to target requirements, the test effort is focused on the Grade "A" platforms and related browsers:

Grade "A"

OS Chrome Chrome Canary FireFox Opera Safari MSIE Priority
Windows7 last version (32) - last version (26) - - 10 Chrome, MSIE, FireFox
MacOS X - - - - 6 NA -

Grade "B"

OS Chrome Chrome Canary FireFox Opera Safari MSIE Priority
Windows7 last version (32) last version (34) last version (26) 19 5.1.7 10 -
MacOS X last version (32) last version (34) last version (26) 19 6 NA -
Linux last version (32) last version (34) last version (26) 19 NA NA -

Shortcuts

TOP | TOC

  • Pass #1 or Pass #2 can be lightened if the other Pass is totally covered.

Testing plan in Ares IDE

TOP | TOC

Non regression coverage (feature/UI/usability)

Top

NB: Features, UI are described in User Documentation

  1. Ares IDE deployment scenarios
  2. Ares IDE management scenarios
  3. Ares project management scenarios
  4. Ares Enyo Editor management scenarios

Integration testing coverage

TOP | TOC

  • Newly implemented features
  • UI modifications provided (cross browser portability)

Enyo Experience

TOP | TOC

  • Test enyo kinds and libraries on Ares IDE.

Test scenarios

TOP | TOC

See QA Documentation Non Regression Test scenarios page:

Clone this wiki locally