-
Notifications
You must be signed in to change notification settings - Fork 49
QA Test Strategy & Plan
Vincent Herilier edited this page Feb 3, 2014
·
8 revisions
Validation of Ares IDE.
This test plan covers the regression tests that the delivered package must pass to validate its delivery
- Update current Ares IDE with the last version of Ares IDE
- Validate Ares IDE with a test set
- Uninstall Ares IDE
- Install ARES IDE from scratch
- Validate Ares IDE with the same test set
Due to target requirements, the test effort is focused on the Grade "A" platforms and related browsers:
OS | Chrome | Chrome Canary | FireFox | Opera | Safari | MSIE | Priority |
---|---|---|---|---|---|---|---|
Windows7 | last version (32) | - | last version (26) | - | - | 10 | Chrome, MSIE, FireFox |
MacOS X | - | - | - | - | 6 | NA | - |
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 | - |
- Pass #1 or Pass #2 can be lightened if the other Pass is totally covered.
NB: Features, UI are described in User Documentation
- Ares IDE deployment scenarios
- Ares IDE management scenarios
- Ares project management scenarios
- Ares Enyo Editor management scenarios
- Newly implemented features
- UI modifications provided (cross browser portability)
- Test enyo kinds and libraries on Ares IDE.