1 / 16

Developing Computer Games

Developing Computer Games. Testing & Documentation. What you will learn. By the end of the lesson you should have the skills to: Task 6D Compile a data dictionary for the objects in your program Create flow charts for major functional elements of the game including ifs/case/loop

israel
Télécharger la présentation

Developing Computer Games

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Developing Computer Games Testing & Documentation

  2. What you will learn • By the end of the lesson you should have the skills to: • Task 6D • Compile a data dictionary for the objects in your program • Create flow charts for major functional elements of the game including ifs/case/loop • Document your code with full annotations • Record the variable & constants used in your program • Task 6B • Create a test strategy • Create a test plan for your program DCG 080

  3. Activity 1 – Identifying what a object data dictionary is! 5 mins • Open DCG 083 Data Dictionary Objects Example and tell me what you think it is used for! • Designers use it to instruct developer as to what properties must be set per object DCG 080

  4. Activity 2 – Try creating an Object Data Dictionary – 5 mins • Open DCG 081 DDO template and put some entries in for your game objects. DCG 080

  5. System Flowchart Symbols • Terminator – Start or End • Flow indicator – to show the movement of a packet of data • Process – to show a data process such as ‘create invoice’ • Input or Output • Decision- (if) DCG 080

  6. Activity 3 - Task 6D flowcharts – 20 mins • Get into groups of 4 (someone you don’t normally work with) • Member 1 – Open DCG 090 P2 and create a flowchart for Process MoveCars • Member 2 – Open DCG 090 p4 and create a flow chart for Process WhoWins • Member 3 – Open DCG 090 p4 and create flowchart for Process OverallWinner • Member 4 – Open DCG 100 p3 and do a flowchart for process WinningStakes/Bankrupt DCG 080

  7. Task 6 d Code Annotation • It is essential to annotate your code as you build your program • Annotation is used so that anyone having to maintain or repair your code in the future known the rational behind your code design • Use the ‘ symbol at the start of each piece of annotation • Use the annotation on the handouts as a guide to the type of information you need to include DCG 080

  8. Task 6 d Variables & Constants • Each time you create a new variable or constant you need to add it to the following table found in your assignments task 6d. DCG 080

  9. Why do we test? • Identifies flaws in the programming code • Easier to de-bug little & often • Errors in the early build stages can cause greater problems later that are harder to detect • Identifies flaws in the design • Doesn’t do what you think the code should make it do! • Might need additional objects or processes added to ensure correct working DCG 080

  10. When do we test? • CONSTANTLY!!! • From the outset – as soon as you start to build • Leaving testing till the end makes de-bugging very difficult • Testing each module of the build ensures you are OK to progress to the next stage DCG 080

  11. How do we test? • Planning • Test plans to identify what needs to be tested at each stage • Testing • Modular testing – identifies problems at each stage • Completed testing – ensures the completed project works when put together • Error correcting • Mainly completed as you go • Remedial action & retest needs to be recorded on the test plan DCG 080

  12. How to Write a Test Strategy for Task 6 b • I am going to use test data which is valid and invalid • I will use test data to test all formulae • I will work out what the answers should be and test against this. • I will try to test the whole of the system including design testing, input testing, process testing and output testing. • I will work through the tests in the following order: DCG 080

  13. Task 6 b Test Strategy • I will include: • Design Testing – I will get the user to check they are happy with the designs • Unit/Integration testing - • I will Test each object • Integration Testing – I will test those functions which feed into other parts of a sequence • System testing I will test items linked objects or forms DCG 080

  14. Activity 4 - Test Plan - 20 mins • Identify tests for each stage of the build (split by module if multi form) • Say: • what you need to do to perform the test • Data to be used • what you expect to happen • what actually happens using DCG 082 do test plan DCG 080

  15. Failed tests • State in the failed test (actual result) what happened & what you plan to do to correct the error • Add a new test to the test plan to re-test after remedial action DCG 080

  16. What you have learned • You should now be able to: • Compile a data dictionary for the objects in your program • Create flowcharts for all major functional elements case/ifs/loops • Record the variable & constants used in your program • Annotate your programming code. • Create a test strategy and plan for your program • Create testing screenshots DCG 080

More Related