Web Apps integration/TestPlan: Difference between revisions

Jump to navigation Jump to search
Line 74: Line 74:
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.
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 smoke test cases that carry the highest value add in comparison to the overhead to the build the automation. See the automation section for more details.
 
'''Tier 1 App Scenario Tests:''' Scenario tests shall be used on this desktop feature to simulate real-use of the application. Examples being considered for scenario tests follow the model shown at the bottom of the [https://docs.google.com/document/d/1tQnFGl7cKNtG3JgAR7MkOm8X4anwPT6lk_SPlRknCtY/edit MWC Pod Demo Script]. Similar to the manual test cases, each test case shall specify a release quality requirement (e.g. Aurora, Beta, Release). Scenario test cases that are applicable to changes made in mozilla central shall be re-tested on each minor release in the Firefox release cycle (e.g. Beta 1, Beta 2). Upon finishing scenario testing, bugs shall be logged for functional issues with the whiteboard marker of '[topapps].'


TODO: Add test strategies to address software quality requirements.
TODO: Add test strategies to address software quality requirements.
Confirmed users
2,959

edits

Navigation menu