HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2012T2 Team Tenacity Project Management Testing"

From IS480
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
#:Visibility of system status
+
    <ol>
** The system should always keep users informed about what is going on, through appropriate feedback within reasonable time.
+
        <li>Visibility of system status</li>
  #:Match between system and the real world
+
The system should always keep users informed about what is going on, through appropriate feedback within reasonable time.
** 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>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

Team Tenacity Logo 3.png
Home The Team Project Overview Project Management Project Documentation Learning Outcomes
Project Schedule Methodology Risk Bug & Testing Meetings Progress Reports


Bug

Bug Metric

Team Tenacity Bug Index Midterm.PNG

*Bug Points = No. of Bugs X Bug Level

Team Tenacity Bug Points Index Midterm.PNG

Bug Graph

Team Tenacity Bug Graph Midterm.PNG

Bug Points Graph

Team Tenacity Bug Points Graph Midterm.PNG

*Bug Points = No. of Bugs X Bug Level

Testing


TestingMethodology.png


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
  1. Visibility of system status
  2. The system should always keep users informed about what is going on, through appropriate feedback within reasonable time.
  3. Match between system and the real world
  4. 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.
  5. User control and freedom
  6. Consistency and standards
  7. Error prevention
  8. Recognition rather than recall
  9. Flexibility and efficiency of use
  10. Aesthetic and minimalist design
  11. Help users recognize, diagnose, and recover from errors
  12. Help and documentation

User Acceptance Test

  • Emphasis is on testing whether the final product is ready to be shipped