157
edits
QA/DevTools Go Faster: Difference between revisions
Jump to navigation
Jump to search
→Test Objectives
| Line 110: | Line 110: | ||
{| class="wikitable" | {| class="wikitable" | ||
|- | |- | ||
! Ref !! Function !! Test Objective !! Evaluation Criteria !! Test Type | ! Ref !! Function !! Test Objective !! Evaluation Criteria !! Test Type !! Owners | ||
|- | |- | ||
| 1 || | | 1 || Previous usage detection || Verify if DevTools previous usage state is properly detected on Beta and Release builds and if the corresponding install process is initiated || If DevTools was previously used, the addon is automatically downloaded and installed. If the user never tried DevTools, it will go through the install process || Manual || Release QA | ||
|- | |- | ||
| 2 || | | 2 || Install entry points || Verify if the entry points for users to install DevTools are captured || The corresponding install work flow is initiated when DevTools are launched, depending on the previous usage status || Manual || Release QA | ||
|- | |- | ||
| 3 || || || || || || | | 3 || Install work flow || Verify if the installation process is properly executed || Depending on the captured entry point, the corresponding install page is opened in a new tab and the installation process is successfully completed || Manual || Release QA | ||
|- | |||
| 4 || DevTools functionality and usability || Verify if all DevTools functionalities are working || Toolbox, Inspector, Console, Debugger, Netmonitor and all the related tools are fully functional and no regressions are triggered by the new install work flow || Manual || Release QA | |||
|} | |} | ||