Apps/QA/OWA Extension: Difference between revisions

Jump to navigation Jump to search
Line 25: Line 25:
=== ''Testing Initiative''  ===
=== ''Testing Initiative''  ===


==== Focus ====
==== Scope ====
 
The following list summarizes the major areas of testing for OWA extension:
 
* Extension Installation Processes (e.g. Install, Uninstall, Update)
* MozApps API
* Apps Lifecycle (e.g. Installation, Launching, Using, Deleting)
* Dashboard
* App Sync
* Other Areas
 
Future areas of concern include the following:
 
* Web Activities/Intents
 
Process requirements:
 
# Determine extension requirements and specifications
# Create manual test cases for basic sanity coverage
# Developing automated test cases for manual test cases
# Exploratory testing of each major part of OWA Extension
# Creation of complex manual scenario testing
 
Note: Requirements are highly volatile, so manual and automated test cases need to be constantly kept up to date.
 
List of top apps to be tested are listed [https://docs.google.com/spreadsheet/ccc?key=0AiGNxoNUJbvzdG9LRU9uWnJNVElnQVVnMnVfd1hXNHc&hl=en_US#gid=0 here]


*Extension (installing, deleting and launching apps)
*Dashboard
*App Sync
*Web Activities/Intents (not Q4)<br>


The testing of the OWA extension will focus on the extension itself (for example, installation/deletion/compatibility and the mozApps.* api), on the dashboard (for example, adding/removing apps), on App Sync and on web activities. The idea is to determine the requirements/specifications of the extension and create manual test cases that will test the basics. Initially, the test cases will be subject to a great deal of changes depending on the requirements and will need to be kept up to date. This applies to the automation as well where keeping the automated test cases in sync with their corresponding manual test cases is essential. Further testing can be done using exploratory methods or a more advanced set of test cases. A proper way of getting apps that can be used for testing will be needed.


The basic iteration of the testing process will hopefully be as follows:  
The basic iteration of the testing process will hopefully be as follows:  
Confirmed users
2,959

edits

Navigation menu