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:50, 9 November 2011
, 9 November 2011→Overall Approach
| Line 123: | Line 123: | ||
** '''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. | ** '''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... | ...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: | In addition to functionality, each api may have the following quality targets: | ||
| Line 135: | Line 135: | ||
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. | 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= | ||