-
-
Notifications
You must be signed in to change notification settings - Fork 41
Protocol for Testing the GUI
John Pellman edited this page Nov 18, 2016
·
5 revisions
- Aggregate all fields/menus from the GUI and their corresponding tabs/windows.
- Determine expected behaviors that should occur for these fields/menus.
- Create a spreadsheet with all of these fields/menus and expected behaviors.
- Mark whether or not the behaviors occur as expected in a "Pass/Fail?" column.
- Note when issues are fixed in a "Fixed?" column.
- Write notes that don't fit neatly into any of the columns in a 'Notes' column.
For 1.0.1:
https://docs.google.com/spreadsheets/d/1X1JbvLzJBdL5qwR9O3WQr7NlixBAj1XUR5i0GeZI9ng/edit?usp=sharing
For 1.0.0:
https://docs.google.com/spreadsheets/d/1BpgGr-wtOxtjnstez66xIvjdsgigLhVuCrHc9IAvIz0/edit?usp=sharing
2023+ Additions
- Developer Info
- Developers' Logbook
Legacy Posts
- Specifications
- Group Analysis Datagrabber
- Multisite and Multiscan Support
- Documentation
- Documentation Standards
- Generating Webpage Documentation with Sphinx
- How to Document Code
- Testing
- Overall Protocol for Testing
- Protocol for Testing the GUI
- Protocol for Writing Test Scripts
- Pre-Release
- Updates Checklist
- New Dependencies to Installation Instruction