Debugging and testing

Transcription

1 Debugging and testing Level 3 Extended Diploma Unit 22 Developing Computer Games Ref:

2 Developer Tools Notepad++ Syntax highlighting Syntax folding hiding blocks of code Google Chrome debugger Interactive inspection of elements Set breakpoints in scripts Reveal values of variables

3 Notepad++ Syntax highlighting Automatic determined by file type Highlight keywords Highlight names (swipe one, all shown)

4 Notepad++ Highlight opening/closing braces

5 Notepad++ Syntax folding hiding blocks of code Click on + or to fold or unfold

6 Turn on Google debugger Select the Wrench menu at the top-right of your browser window, then select Tools - > Developer tools. Or press F12 The developer window opens

7 Finding the element Right-click on any page element (eg some text) and select Inspect element. This will open the HTML file and highlight the selected element

8 Elements The Elements panel allows you to see the web page as the browser sees it.

9 Resources The Resources panel shows all the resurces that are loaded

10 Scripts The scripts panel shows the JavaScript files that have been loaded

11 Breakpoints in scripts Click on the line number to set a breakpoint Hover over the variables to show their values

12 Using the tools If a page doesn t load Check for the script being loaded If it is blank go to the elements page double click on the file the resources page opens and error messages will be displayed

13 Check variable values Set a breakpoint near the suspected problem Hover over the variables In the example efficient is NaN (not a number) Hover over the variables to see why

14 Testing Black box: System test Assume you know nothing about the internals Test to the described functions in the design specification, the onscreen instructions and the user expectations White box Unit test Tests the internals Trace paths through code Check variables initialised Check error conditions detected and handled

15 Documenting tests Black box Test plan Test scripts Problem logs Release to customer when complete White box Programmer s notes or progress log Release to component or system test when complete

16 Testing P5 Test plans, here is a sample of a test plan. Date Test Number What is being tested Expected outcome Actual outcome Evidence screen Shots?

17 Assignment 3 Task 1 (P5) 1. Use the following methods to produce a test plan for your game a) Black box b) White box 2. Develop test cases for each method (at least 4 for each) 3. Run the test cases and document any problems in a problem log. 4. Apply fixes to the problems you found then rerun the test cases to prove the fix worked

18 Assignment 3 Task 2 (P6) Write a user guide for the game. Make sure you explain: The controls. The levels. The scoring. Use screen shots to support your text.

19 Assignment 3 Task 3 (P7) Produce technical documentation for the game. This can either be a written document or be the fully commented code. Make sure you explain: the purpose and data type of each variable. algorithm design (such as brick initialisation, brick/ball collision detection, paddle bounce). all the controls. Scoring. Your comments in the code could provide the explanation.

20 Assignment 3 Task 4 (M3) Use annotated screen shots to explain how you have used test tools to assist in debugging the program. Make sure you cover: Use of context highlighting in Notepad++ (highlighting variables with same name, linking brackets etc) Error messages in the Chrome browser debugger Examination of the variable contents in the Chrome browser debugger Setting of break points in the Chrome browser debugger

21 Assignment 3 Task 5 (M4) Create a feedback form for a user to complete while testing and playing your game. Ask a colleague to test your game and complete the form. Analyse the feedback you receive and document the improvements you would make. Outline how the code would be added to or modified to implement the improvements.

22 Assignment 3 Over to you. Please read the task criteria carefully.