Confirmed users
2,959
edits
Web Apps integration/TestPlan: Difference between revisions
Jump to navigation
Jump to search
→Testing Strategy
| Line 62: | Line 62: | ||
The following testing approaches shall be used to assess the scope of testing stated above: | The following testing approaches shall be used to assess the scope of testing stated above: | ||
'''Development of Manual Test Cases:''' Manual test cases shall be created to test the major portions of features in the testing scope. Each test case shall specify | '''Development of Manual Test Cases:''' Manual test cases shall be created to test the major portions of features in the testing scope. Each test case shall specify a quality requirement (smoke or feature signoff). Applicable sets of these test cases (smoke and feature signoff) should be ran each beta release that are value-added to run to capture bugs. | ||
'''Exploratory Testing of | '''Exploratory Testing of Marketplace Top Apps:''' Exploratory testing of using top native applications shall be conducted to ensure that our highest priority applications are supported on our platform. When exploratory testing these applications, a checklist below will help guide the direction of exploratory testing: | ||
* Does the application avoid using engine specific content? | |||
* Does the application show out of origin content? | |||
* Does clicking out of origin links that are not authentication go to the browser? | |||
* Does application pop-ups and platform integration work as expected? | |||
* Does flash and experimental features work as expected? | |||
For problems discovered that involves a top app, a whiteboard marker of '[topapps]' shall be specified. Any problems with the app itself shall have evangelism bugs logged if the app is a top app. | |||
'''Development of Value-Added Automation:''' Automation shall be developed for manual test cases that carry the highest value add in comparison to the overhead to the build the automation. To determine the value added versus the overhead, an approach for automation shall be documented next to each manual test case to determine if the payoff to build the automation exceeds the overhead cost. Technologies that shall be used will likely be either Mochitest or Mozmill, but this could change based on what manual test cases exist for this feature. | '''Development of Value-Added Automation:''' Automation shall be developed for manual test cases that carry the highest value add in comparison to the overhead to the build the automation. To determine the value added versus the overhead, an approach for automation shall be documented next to each manual test case to determine if the payoff to build the automation exceeds the overhead cost. Technologies that shall be used will likely be either Mochitest or Mozmill, but this could change based on what manual test cases exist for this feature. | ||