QA/DateTimeInputTypes
Revision History
This section describes the modifications that have been made to this wiki page. A new row has been completed each time the content of this document is updated (small corrections for typographical errors do not need to be recorded). The description of the modification contains the differences from the prior version, in terms of what sections were updated and to what extent.
| Date | Version | Author | Description |
|---|---|---|---|
| 14/09/2016 | 1.0 | Brindusa Tot | Created first draft |
| 13/11/2017 | 1.1 | Emil Ghitta | Updates |
Contents
Overview
Purpose
Detail the purpose of this document. For example:
- The test scope, focus areas and objectives
- The test responsibilities
- The test strategy for the levels and types of test for this release
- The entry and exit criteria
- The basis of the test estimates
- Any risks, issues, assumptions and test dependencies
- The test schedule and major milestones
- The test deliverables
Scope
This wiki details the testing that will be performed by the project team for the Date Time Input Types project. It defines the overall testing requirements and provides an integrated view of the project test activities. Its purpose is to document:
- What will be tested
- How testing will be performed
Ownership
Development
Manager: Wesley Huang (irc: wesley_huang)
Engineering Contacts: Jessica Jong (irc: jessica), Scott Wu(irc: scottwu)
UX Designers: Morpheus Chen (irc: Morpheus), Tina Hsieh (irc: Tina_Hsieh)
Visual Designer: Helen Huang (irc: hhuang)
TDC QA Contact: Cynthia Tang (irc: cynthiatang)
Engineering Team - Nightly Testing:
Rares Bologa (irc: RaresB) - PM for QA team
Brindusa Tot (irc: brindusat) - leading QA efforts
Roxana Leitan (irc: RoxanaLeitan) - QA
Testing summary
Scope of Testing
In Scope
Date/Time Picker project enables the feature on Desktop where HTML input fields should contain a date or time or allow users to select a week in a year.
The Date/Time Picker project:
- aims to provide 5 basic input/pickers: date, month, time, date time, and week
- it's designed to meet the following HTML standard criteria including "Preset Value", "Preset List", "Step", and "Max/Min"
- takes care of localization and accessibility (Cursor Only, Cursor+Keyboard, or Keyboard only).
Out of Scope
RTL currently is not in the scope.
At the time being - only the Gregorian calendar is considered.
Requirements for testing
Environments
Full testing will be performed on the following OSes:
- Windows
- Mac OS X
- Ubuntu
Test Strategy
Test Objectives
This section details the progression test objectives that will be covered. Please note that this is at a high level. For large projects, a suite of test cases would be created which would reference directly back to this master. This could be documented in bullet form or in a table similar to the one below.
| Ref | Function | Test Objective | Evaluation Criteria | Test Type | Owners |
|---|---|---|---|---|---|
| 1 | Date picker | The date picker is properly displayed | Default input field displays yyyy-mm-dd (varies based on locale) | Manual | Eng Team |
| 2 | Date picker functionality | The date can be properly selected | User can properly pick between years/months/days | Manual | Eng Team |
| 3 | Month/year picker | The month/year picker is properly displayed | Default input field displays yyyy-mm (varies based on locale) | Manual | Eng Team |
| 4 | Month/year picker functionality | The month/year picker is properly selected | User can pick month first then year, vice versa | Manual | Eng Team |
| 5 | Time picker | The time picker is properly displayed | Default input field displays --:-- -- (varies based on locale) | Manual | Eng Team |
| 6 | Time picker functionality | The time picker is properly displayed | User can pick 3 columns in any order: hour, minute, AM/PM | Manual | Eng Team |
| 7 | Week picker | The week picker is properly displayed | Default input field displays Week --, yyyy (varies based on locale) | Manual | Eng Team |
| 8 | Week picker functionality | The week can be properly selected | User can pick months/years and the highlight in input box will move to picked segment and change value simultaneously | Manual | Eng Team |
| 9 | DateTime-local picker | DateTime local picker is properly displayed | Default input field displays yyyy-mm-dd, -- : -- -- (varies according to date and time picker) | Manual | Eng Team |
| 10 | DateTime-local picker functionality | DateTime local picker can be properly selected | User can pick the date that will automatically trigger the time picker and vice versa | Manual | Eng Team |
| 11 | Localization | Date/Time pickers are properly displayed on locale builds | User can pick between pickers on locale builds | Manual | Eng Team |
| 12 | Accessibility | Date/Time pickers are visible and usable from accessibility point of view | Testing for accessibility includes: - Cursor only |
Manual | Eng Team |
Builds
This section should contain links for builds with the feature -
- Links for Nightly builds - available since 10.26.2016 - link
- Links for Beta builds
Test Execution Schedule
Eng team will follow up the milestone given by the developers team: Milestone link
The following table identifies the anticipated testing period available for test execution.
| Project phase | Start Date | End Date |
|---|---|---|
| Start project | 2016.09.12 | |
| Study documentation/specs received from developers | 2016.09.12 | 2016.09.15 |
| QA - Test plan creation | 2016.09.12 | 2016.09.15 |
| QA - Test cases/Env preparation | 2016.09.12 | 2016.10.01 |
| QA - Nightly Testing | 2016.11.10 | 2017.09.13 |
| QA - Beta Testing | 2017.09.14 | 2017.10.27 |
| Release Date | 2017.11.14 |
Testing Tools
Detail the tools to be used for testing, for example see the following table:
| Process | Tool |
|---|---|
| Test plan creation | Mozilla wiki |
| Test case creation | TestRail |
| Test case execution | TestRail |
| Bugs management | Bugzilla |
Status
Overview
Time
| Basic input field | [LANDED] | Nightly 52: first landed, disabled by default |
| Pop-up picker | [LANDED] | Nightly 52: first landed, de-scoped |
| Input field with STEP (displaying warning message when out of range) | [LANDED] | Nightly 53: first landed,disabled by default |
| Input field with Min/Max (displaying warning message when out of range) | [LANDED] | Nightly 53: first landed, disabled by default |
| Input field with keyboard navigation | [LANDED] | Nightly 52: first landed, disabled by default |
Date
| Basic input field | [LANDED] | Nightly 53: first landed, disabled by default |
| Pop-up picker | [LANDED] | Nightly 52: first landed, disabled by default |
| Input field with STEP (displaying warning message when out of range) | [LANDED] | Nightly 53: first landed,disabled by default |
| Input field with Min/Max (displaying warning message when out of range) | [LANDED] | Nightly 53: first landed, disabled by default |
| Input field with keyboard navigation | [LANDED] | Nightly 53: first landed, disabled by default |
Risk Assessment and Coverage
| ID | Description / Threat Description | Magnitude | Probability | Priority | Impact Score |
|---|---|---|---|---|---|
| RAC-1 | User Experience | 3-High | 3-High | 3-High | 27 |
| RAC-2 | High contrast | 3-High | 3-High | 3-High | 27 |
| RAC-3 | Localization | 3-High | 2-Possible | 3-High | 18 |
| RAC-4 | Screen reader for picker and input box | 3-High | 2-Possible | 3-High | 18 |
| RAC-5 | Input box in multiple frames | 3-High | 2-Possible | 2-Medium | 12 |
| RAC-6 | RTL | 1- Low | 2-Possible | 2-Medium | 4 |
Values:
- Magnitude: 1- Low , 2-Moderate, 3-High
- Probability: 1-Unlikely, 2-Possible, 3-Almost Certain
- Priority: 1 - Low, 2-Medium, 3-High
Impact Score Breakdown:
- An impact value of 1, 2, 3, 4 would describe an area which although should be covered there aren't expected any discoveries of critical issues.
- An impact value of 6, 8, 9, 12 would describe an area in which we expect to find issues but those issues are not expected to be critical.
- An impact value of 18 or 27 would describe an area on which it is likely to find issues and those issues to be critical or blockers.
References
- Meta Bug - Bug 888320 (datetime) meta Implement all time and date related input types
- UX specs bug - Bug 1069609
- List and links for specs
- UX specifications - link - Roadmap wiki page - link - demo presentation - link - webpage sample - link - QA Kick-off etherpad link
Testcases
Test Areas
| Test Areas | Covered | Details |
|---|---|---|
| Private Window | yes | |
| Multi-Process Enabled | yes | |
| Multi-process Disabled | No | |
| Theme (high contrast) | yes | |
| UI | ||
| Mouse-only operation | yes | |
| Keyboard-only operation | yes | |
| Display (HiDPI) | yes | |
| Interraction (scroll, zoom) | yes | |
| Usable with a screen reader | yes | e.g. with NVDA |
| Usability and/or discoverability testing | yes | Is this feature user friendly |
| RTL build testing | yes | |
| Help/Support | ||
| Help/support interface required | No | Make sure link to support/help page exist and is easy reachable. |
| Support documents planned(written) | Make sure support documents are written and are correct. | |
| Install/Upgrade | ||
| Feature upgrades/downgrades data as expected | No | |
| Does sync work across upgrades | No | |
| Requires install testing | No | separate feature/application installation needed (not only Firefox) |
| Affects first-run or onboarding | NA | Florin/Lawrence are investigating if there is a dedicated QA for this, or we should test? Should be an yes/no and if is yes should add in detail column the team/person assigned. |
| Does this affect partner builds? Partner build testing | yes/no options, add comment with details about who will lead testing | |
| Enterprise | Raise up the topic to developers to see if they are expecting to work different on ESR builds | |
| Enterprise administration | No | |
| Network proxies/autoconfig | No | |
| ESR behavior changes | No | |
| Locked preferences | No | |
| Data Monitoring | ||
| Temporary or permanent telemetry monitoring | No | List of error conditions to monitor |
| Telemetry correctness testing | No | |
| Server integration testing | No | |
| Offline and server failure testing | No | |
| Load testing | No | |
| Add-ons | If add-ons are available for testing feature, or is current feature will affect some add-ons, then API testing should be done for the add-on. | |
| Addon API required? | No | |
| Comprehensive API testing | No | |
| Permissions | No | |
| Testing with existing/popular addons | No | |
| Security | Security is in charge of Matt Wobensmith. We should contact his team to see if security testing is necessary for current feature. | |
| 3rd-party security review | No | |
| Privilege escalation testing | No | |
| Fuzzing | No | |
| Web Compatibility | depends on the feature | |
| Testing against target sites | ||
| Survey of many sites for compatibility | No | |
| Interoperability | depends on the feature | |
| Common protocol/data format with other software: specification available. Interop testing with other common clients or servers. | No | |
| Coordinated testing/interop across the Firefoxes: Desktop, Android, iOS | No | |
| Interaction of this feature with other browser features | No |
Test suite
Full Test suite - can be found on TestRails at link or in the PDF doc
Bug Work
Meta: Bug 888320 - [meta] (datetime) implement all time and date related input types
Logged bugs ( blocking 888320 )
51 Total; 12 Open (23.53%); 37 Resolved (72.55%); 2 Verified (3.92%);
Meta: Bug 1323674 -[meta] defects in date time input types
Logged bugs ( blocking 1323674 )
124 Total; 28 Open (22.58%); 63 Resolved (50.81%); 33 Verified (26.61%);
Bug Verification (blocking 888320 )
29 Total; 0 Open (0%); 27 Resolved (93.1%); 2 Verified (6.9%);
Bug Verification (blocking 1323674 )
65 Total; 0 Open (0%); 32 Resolved (49.23%); 33 Verified (50.77%);
Sign off
Criteria
Check list
- All test cases should be executed
- All blockers, criticals must be fixed and verified or have an agreed-upon timeline for being fixed (as determined by engineering/RelMan/QA)
Results
Nightly testing
Time Input Box
List of OSes that will be covered by testing
Date Input Box and Date Picker
List of OSes that will be covered by testing
Beta Testing
Checklist
| Exit Criteria | Status | Notes/Details |
|---|---|---|
| Testing Prerequisites (specs, use cases) | [DONE] | |
| Testing Infrastructure setup | N/A | |
| Test Plan Creation | 09.12.2016 | 09.14.2016 |
| Test Cases Creation | [DONE] | |
| Full Functional Tests Execution | [DONE] | |
| Time Input Box Functional Tests Execution | [DONE] | |
| Date Input Box/Picker Functional Tests Execution | [DONE] | |
| Automation Coverage | ||
| Performance Testing | ||
| All Defects Logged | [DONE] | |
| Critical/Blockers Fixed and Verified | [DONE] | |
| Metrics/Telemetry | ||
| QA Signoff - Nightly Release | [DONE] | Email sent on 2017.09.13 |
| QA Aurora - Full Testing | n/a | n/a |
| QA Signoff - Aurora Release | n/a | n/a |
| QA Signoff - Beta Release | [DONE] | Email sent on 2017.10.17 |
