Class hours: 9:40 – 2:05
Mr. Bohmann
wbohmann@ewsd.org
Week Thirty Six (36)
Today’s Notes
- Today is an EHS A Day
- Equipment Returns – if you have equipment, it is now due
- Afternoon Breaks This Week – changing to 15 min (if you go outside) to maximize the nice weather
- Cawd Games – Playtesting this week – the plan is to begin playtesting Thursday & Friday
- 11:40 -12:15 both days
9:40 Attendance
9:45 Monday Mail on a Tuesday
9:50 CAWD Game Studio
This week you are going to take your Game Design Document and your Trello planner and begin the Testing & Integration Phase. We are working towards game play and testing this week
The testing & implementation phase is an essential part of the game development cycle. Testing or Quality Assurance includes careful planning, documentation of bugs and errors and follow up on the fixes that need to be made. Check out this job listing for a QA.
Before you start testing, it is a good idea to develop a test plan. The test plan details exactly what kind of performance tasks/tests need to be made. Basically, what are you testing? This might be the ease of use of the GUI, the core game mechanic, the story, user inputs and or the user experience.
Rather than ask a person to play your game and tell you what you think, consider creating some specific questions that you want feedback on. Remember when we did web testing? Same idea. We are testing not only gameplay, but how the user interacts with the game.
Larger projects may involve dozens of tests, especially when a new version or release is created.
Alpha testing is usually done by dedicated testers (the people who assembled the program)
Beta testing allows external people (outside the project) a chance to find problems the internal testers might have missed.
What kinds of questions can we ask our users feedback on? Can you think of some?
Assignment: Using the list of suggested questions, review the list and make some modifications on your own to be geared towards your specific game.
Create Questionnaire using Google Forms. You’ll share a copy of your Google Form by posting the link on Google Classroom.
Google forms can be customized so you can use your game colors and image as header.
When your form is completed, you’ll move into your game development work to get reading for testing tomorrow and Thursday.
5 Minute Scrum Meetings / Update Trello Boards
Remember a good meeting is quick and on target. What am I working on today, What help do I need. Those are the questions you should be responding to in your group or individually.
10:35 Break
10:45 English with Mx. Yopp
11:30 CAWD Game Studio
| Date | Week | Deliverable | Software Development Cycle |
|---|---|---|---|
Game idea generation, pre-planning | Planning | ||
| Analysis / Design | |||
Goal: (your player should be moving in your world, You have a start screen and credits screen and your core mechanic is working. | Design / Implementation | ||
| May 30th – Jun 2nd | Four | Prototype with game play | Testing/Maintenance / Publishing/Evaluation |
| June 7th -8th | Game Jam | Evaluation |
You are working towards a playable prototype. To make testing more authentic, create a build (an .exe) file of your game. You can call this first version your Alpha.
So if my game was being published it would be BohmannBrickBreaker_Alpha.exe.
Alphas will need to be published by Thursday of this week for testing. I’ll review publishing process again tomorrow.
12:15 Lunch
12:45 Independent Reading
1:10 Break
1:20 Independent Project Work Time of Individual Support
- Incomplete Work
- Game Dev time
- Playtesting Questions