Confirmed users
151
edits
QA/Browser Technologies/WebAPI: Difference between revisions
Jump to navigation
Jump to search
QA/Browser Technologies/WebAPI (view source)
Revision as of 00:48, 9 November 2011
, 9 November 2011→Environments
| Line 110: | Line 110: | ||
|} | |} | ||
</onlyinclude> | </onlyinclude> | ||
=Overall Approach= | |||
Each API must be assured of its robustness and fitness for purpose. APIs must work at ''Integration''levels with each other and with external testapps, ''Application'' level supporting entire applications, and as part of an end-to-end ''system''. | |||
To that end, the testplan for each API could consist of the following deliverables in each case: | |||
*'''Integration Tests''' - Tests for JS interfaces at integration level. These are usually automated and might deploy a framework like Jasmine, Marionette and/or something like Robotium with custom classes, TBD. | |||
*'''Application Tests''' - These would most likely consist of | |||
** '''test pages''' - Test HTML pages implementing the WebAPI(s) in question | |||
** '''native test apps''' - in the case of Android, it should be possible to get api values directly from OS as a basis of comparison | |||
** '''manual test cases''' - stored in Case Conductor. Note that we will be running parallel manual and automated testing efforts so that test coverage is not lost while automation is being built up. Also, it is not generally possible to automate everything. | |||
...and ultimately... | |||
**automated functional testing - most likely in a combination of tools like e.g. Robotium and Marionette. The plan is to try to leverage the test pages and test apps/code developed (and manually tested against) earlier. | |||
In addition to functionality, each api may have the following quality targets: | |||
*Usability | |||
*Reliability | |||
*Performance | |||
*Scalability | |||
*Security | |||
So TBD, there may be additional tests or test strategies deployed iteratively as the project evolves. | |||
It should be noted Some APIs (and areas of support) however only work in conjunction with other APIs, so these must be combined when writing test apps. | |||
=Environments= | =Environments= | ||
List what's needed for test environments here. links to test cases, test servers, unit tests, etc.. | List what's needed for test environments here. links to test cases, test servers, unit tests, etc.. | ||
The following '''matrix''' which is a WIP will be used as a template for determining device and version support for each api: | |||
https://docs.google.com/spreadsheet/ccc?key=0AhE7m4JB2j6tdEJFZ3NoZkRoRTM3TTRpQll3UjZLYnc#gid=4 | |||
Environment matrices for each API or area will ultimately list: | |||
*all supported devices and hardware types | |||
*all supported browser versions | |||
*b2g | |||
=Resources= | =Resources= | ||