Release Package QA Test Plan
|Chrome||Latest Stable Release|
|Firefox||Latest Stable Release|
|Internet Explorer||Latest Stable Release|
|MS Edge||Latest Stable Release|
|Safari [fluid:1]||Latest Stable Release|
[fluid:1] keyboard a11y can be slightly improved if you select the "all controls" option from "Keyboard Shortcuts" under the "Keyboard & Mouse" settings. May also need to use "option + tab" for tab navigation.
General QA Guidelines
Distribution configurations to test
- NPM Module
- Individual files
Test each of the distribution configurations.
Navigate to the following html file and execute all of the unit tests.
Run all unit tests by launching the html files from the following location
Improvised tests for quickly discovering critical issues, and uncovering ones that may be outside of formalized testing.
Attempt to use the tool in various situations, using your imagination and freedom to explore the interface and interactions. Can use the other test types as a guide.
All test plans:
Testing Fluid Components
Ideas for future Testing of the Release Package
|Manually change all dependencies to InfusionAll.js
- Manually ensure that all files have dependencies changed
- Doesn't require any additional files or new samples be developed
- Error prone
- Time consuming (40 files * 2 packages = 80 places to change)
|Minimal set of sample pages that we manually change (e.g. mock-ups)
- Will reduce the time and error
- Will provide examples of fluid components working together on a single page
- May clutter the example page
- Still have the risk of error wehn manually change the dependencies
|Automated process to modify the dependencies on each page
- Will eliminate most of the risk of error
- Will have to be executed on the test system instead of the final bundle being posted
- Introduces another layer, which may be a source of errors
|The build process builds 4 different bundles, 2 using InfusionAll.js and 2 that don't
- Part of the bundling process
- Should elminate the risk of most errors
- Will build additional bundles that will likely only be used for testing.
- InfusionAll.js in the bundles posted, haven't really been tested
|Minimal set of test files that actually link to InfusionAll.js in the repository
- Can test InfusionAll.js from the build site if needed
- No risk of error
- Overhead to maintain and update
- Developers would require InfusionAll.js on their system in order for these examples to work