Confirmed users
2,959
edits
Apps/QA/Top Apps Analysis Strategy: Difference between revisions
→Scenario Testing
| (One intermediate revision by the same user not shown) | |||
| Line 50: | Line 50: | ||
== Scenario Testing == | == Scenario Testing == | ||
Scenario tests will be used with the top apps during testing on the desktop and mobile to simulate real-use of the application. Examples being considered for scenario tests follow the model shown at the bottom of the MWC Pod Demo Script. To create a scenario off a top app, follow the following process: | Scenario tests will be used with the top apps during testing on the desktop and mobile 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]. To create a scenario off a top app, follow the following process: | ||
# Install the latest build of Soup and ensure you have a build of Firefox allowing for desktop apps testing | |||
# Install the app for desktop and mobile respectively you wish to generate a scenario for | |||
## If the app does not exist on any avenue, such as being hosted on an app directory [https://apps.mozillalabs.com/appdir/?db=db/apps-preview.json here], then contact Ron to find out if the app developer has a manifest hosted for the app | |||
## If there is no app manifest hosted, contact Ron about working with the developer to get a manifest. In the future, there is consideration for faking websites as apps as a long-term solution | |||
# Exploratory test the application to determine use cases for the application that different stakeholders use | |||
## Note: Collaborate with Jen Arguello on this to determine these use cases | |||
# For use cases captured, add these use cases as test cases to a list of scenario test cases | |||
Upon completing development of the scenario, then the scenario will be added to list of scenario test cases for top apps. These test cases will be used in conjunction with manual test cases on the system to determine quality state of the desktop and mobile apps experience when a test run is required. If any of these scenarios fail, then an investigation must take place to determine if this is problem with our system or the app itself. If the problem exists our system, bugs should be logged accordingly using the topapps whiteboard keyword. If the problem exists with the app, then writeup detailed feedback about the underlying app issues and send that feedback to Ron. Ron will then follow-up with the developer with the feedback. As questions come back from the developers on the feedback, more feedback may need to be provided. | Upon completing development of the scenario, then the scenario will be added to list of scenario test cases for top apps. These test cases will be used in conjunction with manual test cases on the system to determine quality state of the desktop and mobile apps experience when a test run is required. If any of these scenarios fail, then an investigation must take place to determine if this is problem with our system or the app itself. If the problem exists our system, bugs should be logged accordingly using the topapps whiteboard keyword. If the problem exists with the app, then writeup detailed feedback about the underlying app issues and send that feedback to Ron. Ron will then follow-up with the developer with the feedback. As questions come back from the developers on the feedback, more feedback may need to be provided. | ||