Difference between revisions of "IS480 Team wiki: 2012T2 Team Tenacity Project Management Testing"
Jump to navigation
Jump to search
Line 93: | Line 93: | ||
* Emphasis is on finding User Interface e.g. navigation, error messages issues | * Emphasis is on finding User Interface e.g. navigation, error messages issues | ||
* We attempt to measure ourselves against the 10 heuristic standards | * We attempt to measure ourselves against the 10 heuristic standards | ||
− | + | <ol> | |
− | + | <li>Visibility of system status</li> | |
− | + | The system should always keep users informed about what is going on, through appropriate feedback within reasonable time. | |
− | + | <li>Match between system and the real world</li> | |
+ | The system should speak the users' language, with words, phrases and concepts familiar to the user, rather than system-oriented terms. Follow real-world conventions, making information appear in a natural and logical order. | ||
<li>User control and freedom</li> | <li>User control and freedom</li> | ||
<li>Consistency and standards</li> | <li>Consistency and standards</li> |
Revision as of 19:27, 16 February 2013
Home | The Team | Project Overview | Project Management | Project Documentation | Learning Outcomes |
Project Schedule | Methodology | Risk | Bug & Testing | Meetings | Progress Reports |
Contents
Bug
Bug Metric
*Bug Points = No. of Bugs X Bug Level
Bug Graph
Bug Points Graph
*Bug Points = No. of Bugs X Bug Level
Testing
Unit testing
- Done in every sprint
- Every functionality that is developed during the sprint is tested
- Emphasis is on quality of functionality developed
Integration Testing
- Done in each every after different functionalities are integrated
- Emphasis is on identifying issues which surface during integration
Regression Testing
- Testing everything completed in earlier sprints to ensure quality of the application developed
Usability Testing
- Emphasis is on finding User Interface e.g. navigation, error messages issues
- We attempt to measure ourselves against the 10 heuristic standards
- Visibility of system status The system should always keep users informed about what is going on, through appropriate feedback within reasonable time.
- Match between system and the real world The system should speak the users' language, with words, phrases and concepts familiar to the user, rather than system-oriented terms. Follow real-world conventions, making information appear in a natural and logical order.
- User control and freedom
- Consistency and standards
- Error prevention
- Recognition rather than recall
- Flexibility and efficiency of use
- Aesthetic and minimalist design
- Help users recognize, diagnose, and recover from errors
- Help and documentation
User Acceptance Test
- Emphasis is on testing whether the final product is ready to be shipped