-
Notifications
You must be signed in to change notification settings - Fork 10
Analytics and Testing
Unit tests should be implemented for all components of the commotion client. This includes extensions, which have a system for loading unit-tests. The test suite for each module and extension should also contain "User Diagnostic" data that will include tests that output diagnostic data to the commotion bug-reporter.
RESOURCES:
- Test PyQt GUIs with QTest and unittest
- QTest Class Reference
- QTest Example
- Test Driven Development and PyQt using Maya
- Code Samples using PyQt.QTest
We aspires to make the Commotion client a platform that can be thoroughly tested for usability and training purposes. To this end we are debating the implementation of and optional analytics build option to create a Commotion Platform that will be used to monitor a user behavior on the tool. This will keep basic analytics about length of time on a page and number of visits, track a users mouse movements within the bounds of the application, usability task instructions, and basic controls for allowing a user to mark the page with a comment and track individual usability tasks.
Adding an easily built-on "analytics mode" will require a great deal of thought to the security of the platform. As such, before an analytics mode is put into place certain precations will be taken.
- Field's that can be used to identify or build a extendable profile of a user will be forbidden from tracking values. ( password, user_name, e-mail, etc.)
- Special alerts, flags, and warnings will be inserted that look for the use of analytics packages that are installed. (New menu_bar icon, warning on start-up, warning in settings, prompt for password for saving analytics data on start up, prompt to save analytics on application close.)