SE306:Group 3:Subgroup 1a

From Marks Wiki
Jump to navigation Jump to search

Subgroup 1

  • Shruthi
  • Geoffrey
  • Danver

Our test-bed for the G5 engine is hosted at ....

Game building checklist

Non functional issues identified

Acceptance Testing

Our testing plan was as follows:

  • Mix of white-box and black box testing
  • Two testers involved at all times
  • Testing the requirements
  • implementing game and verifying good behaviour
  • code inspection

Next line

  • fulfils requirements
  • user interface works?


  • performance is within constraints?
  • loading requirements
  • compatible modules
  • error handling?
  • database rollback and committing?

Functional AND non-functional

  • C-B A. Mention budgeting time to bug fixes. All the bugs we didn't fix are because they would take too long.

Work hours

Name Date Start time End time Notes
All 16-10-08 1:00 pm 4:00 pm Reading Documentation and sorting out logistics issues
All 23-10-08 2:00 pm 4:00 pm Tested and walkthrough their code
All 24-10-08 1:00 pm 5:00 pm Started writting the report

Notes

BugId Allocated To Name Description Module Discovered Time Status Fixed Time
0 Danver junit.jar was not on build path Fixed
1 Geoffrey The archive: D:/Eclipse-workspace/mysql-connector-java-5.1.6-bin.jar which is referenced by the classpath, does not exist Discovered the ant script is the only way to run it 13:47 16-10-08 fixed 13:57 25-9-08 3:06 23-10-08
3 Shruthi asdasdasd asdadasdasd 14:09 25-9-08 Unfixed

Usability Evaluation

Heuristics

Study