IS480 Team wiki: 2012T2 Team Tenacity Project Management Testing
Jump to navigation Jump to search
|Home||The Team||Project Overview||Project Management||Project Documentation||Learning Outcomes|
|Project Schedule||Methodology||Risk||Bug & Testing||Meetings||Progress Reports|
- Done in every sprint
- Every functionality that is developed during the sprint is tested
- Emphasis is on quality of functionality developed
- Done in each every after different functionalities are integrated
- Emphasis is on identifying issues which surface during integration
- Testing everything completed in earlier sprints to ensure quality of the application is maintained
- Emphasis is on finding User Interface related issues e.g. confusing navigation, non-descriptive error messages
- We attempt to measure ourselves Jakob Nielsen's 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 Users often choose system functions by mistake and will need a clearly marked "emergency exit" to leave the unwanted state without having to go through an extended dialogue. Support undo and redo.
- Consistency and standards Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform conventions.
- Error prevention Even better than good error messages is a careful design which prevents a problem from occurring in the first place. Either eliminate error-prone conditions or check for them and present users with a confirmation option before they commit to the action.
- Recognition rather than recall Minimize the user's memory load by making objects, actions, and options visible. The user should not have to remember information from one part of the dialogue to another. Instructions for use of the system should be visible or easily retrievable whenever appropriate.
- Flexibility and efficiency of use Accelerators -- unseen by the novice user -- may often speed up the interaction for the expert user such that the system can cater to both inexperienced and experienced users. Allow users to tailor frequent actions.
- Aesthetic and minimalist design Dialogues should not contain information which is irrelevant or rarely needed. Every extra unit of information in a dialogue competes with the relevant units of information and diminishes their relative visibility.
- Help users recognize, diagnose, and recover from errors Error messages should be expressed in plain language (no codes), precisely indicate the problem, and constructively suggest a solution.
- Help and documentation Even though it is better if the system can be used without documentation, it may be necessary to provide help and documentation. Any such information should be easy to search, focused on the user's task, list concrete steps to be carried out, and not be too large.
User Acceptance Test
- Emphasis is on testing whether the final product is ready to be shipped
Please refer to Jakob Nielsen's 10 heuristic standards here: Jakob Nielsen's Heuristic Standards