Now that we have our test plan, we’re ready to test our game! You’ll need friends or family who are willing to test your game design plan. Find AT LEAST THREE people to test your game. Then, send each person a copy of the test plan you created in Activity 1.

Question

Step 1: Test the Scenarios
Have each tester, yourself included, complete the test plan scenarios and enter the actual results of each test in the test plan table. If anything comes up that wasn’t anticipated in the Expected Results column, be sure to describe it in detail in the Actual Results column. Then, the tester can assign each scenario a pass or fail.

Step 2: Discuss Comments and Suggestions
Once all scenarios are complete, have each tester write any comments, suggestions, or ideas they have for the game/application below the table. You may be surprised at the results! Often, ideas will come up that can easily be implemented in just a few lines of code.

Don’t just read the testers’ results—discuss the testers’ experiences, too. This will help you practice your soft skills and demonstrate communication skills, respect, and professionalism that will help you moving forward. Being able to accept and receive criticism and critiques is a very important aspect of this stage as you want your testers to feel comfortable discussing the game freely and openly so that you can get accurate feedback.

Step 3: Actionable Results
Review your feedback and compile a summary in a new document. If any test scenarios failed, come up with a plan to fix and retest them. Identify any programming errors encountered along the way or that were previously encountered in the testing stages. Classify these errors (bugs, crashes, specific programming/logic errors, etc.), and order them by priority.

You may need to use online documentation and forums to help with your plan. Research online to find forums and resources for Python programming and/or PythonAnywhere, and list them in your document if they are helpful. Remember that when interacting with an online community, always read the site’s specific rules (for forums, they are usually in the topic pinned at the top), terms, and acceptable use policies so that you will know the proper digital etiquette.

Beyond that, if you need to post a question or comment, be sure to give as much information as possible, be polite and professional, and explain your question thoroughly. Time is valuable, especially to professionals in the technology field, so ensure you’re making it as smooth of a support process as possible by compiling any potentially needed information before posting questions or threads online.

In a new document, describe your results and the actions taken to find solutions to potential problems. Then, respond to each of the tester’s comments and suggestions with a potential solution or addition you could make to your project.

Answer 1

Certainly! Below is a structured way to carry out Steps 1 through 3 of your game testing process, including templates and guidelines for documenting the results.

Step 1: Test the Scenarios

Testing Template

You can use a table like the one below to organize the information:

| Scenario | Expected Results | Actual Results | Pass/Fail | |-----------------------|--------------------------------------|--------------------------------------|-------------| | Scenario 1 Description| Description of what you expect | What actually happened | Pass/Fail | | Scenario 2 Description| Description of what you expect | What actually happened | Pass/Fail | | Scenario 3 Description| Description of what you expect | What actually happened | Pass/Fail | | ... | ... | ... | ... |

Steps for Testers:

1. Fill in the "Actual Results" column based on the game behavior observed during the test.
2. Mark each scenario as "Pass" if the actual results meet the expected results, or "Fail" if they do not.

Step 2: Discuss Comments and Suggestions

Feedback Collection Template

After testing, gather comments and suggestions in a document or sheet:

• Tester Name:
  • Comments:
  • Suggestions:
  • Ideas:

Discussion Guidelines:

• Encourage open dialogue about their experiences.
• Be receptive and demonstrate active listening.
• Take notes on key points they raise or suggestions they make.

Step 3: Actionable Results

1. Compile Feedback Summary
   • List out failures, comments, and suggestions in a clear and concise manner.

Sample Summary Template

| Issue | Description | Severity (High/Medium/Low) | Suggested Fix | |-----------------------|--------------------------------------|----------------------------|-------------------------| | Scenario 1 Failure | Detailed description of issue | High | Action plan for fix | | ... | ... | ... | ... |

2. Plan to Fix and Retest
   • Based on the failures identified, create a step-by-step plan to address each issue and reassess after changes are made.

Example Action Plan:

• Identify programming error in Scenario 1.
  • Bug Type: Logic error.
  • Fix: Adjust game state logic to properly reflect player actions.
  • Retest Date: [Next Testing Date]

3. Online Resources
   • Compile links to relevant online documentation, forums, or communities for Python and game development support.

Sample Resource List:

• Python Official Documentation
• Stack Overflow
• PythonAnywhere Community Forum

4. Respond to Tester Suggestions
   • Create a document containing each suggestion and your planned response.

Response Template

| Tester | Suggestion | Response | |----------|----------------------------------------------|--------------------------------------------------| | Tester 1 | Suggests adding more levels | Plan to add 3 additional levels post-testing. | | Tester 2 | Suggests improving graphics for clarity | Research options for better graphics tools. | | Tester 3 | Suggests adding sound effects | Plan to implement sound effects in Phase 2. |

Final Document Compilation

Collate all the sections above into a final document that covers:

• Test Plan Results
• Tester Feedback
• Summary of Issues and Prioritization
• Action Plan for Fixes
• List of Helpful Online Resources
• Responses to Suggestions

Conclusion

This structured approach will help ensure that you effectively gather, analyze, and act on feedback from your testers. By responding thoughtfully to their suggestions and documenting your findings and action plans, you'll be setting a solid foundation for improving your game.