Slides below are made by me to use for a study session at my current work (each member is supposed to talk about a topic related to the work). I didn't use these slides after all because more related theme was found. However, I feel regret to make the material which I spent a certain time shelved right away, so I decided to put on here as a supplement. (Do not use it somewhere else without permission. I guess it won't happen, though.)
使用ソフト(software used): Microsoft PowerPoint 2003
How to Make a Good Bug Report:
Thinking from a case of Koei Tecmo Games
Ciel nosurge:
Ode to a Lost Star
PS Vita
Released on April 2012
Developed by GUST
Objective of the game:
To have a communication with and get back the lost memory of a girl named Ion who lives alone in the place you don't know where it is.
How to restore her memory:
A fairy-like creature living in Ion's mind (Let me assume so.)
Take a picture of a barcode by Vita, then a Sharl will be automatically generated.
Order Sharls to repair Ion's ruined landscapes in her mind.
When the memory is restored, you can see story hidden in the part, and Ion's past will be revealed.
This video game is very interesting for the unique world view...but
There were a lot of bugs.
Gust was thought that they were not technically familiar with because it was their first Vita online game; bugs often occurred and caused troubles to play.
Case Study of the Bug Reported in Oct. 2014
※この不具合の詳細はBugsページを参照
*Refer to Bugs page for details of this bug.
This bug was serious since it reoccurred by 100% and caused an application crash.
I specified the condition and reported to the user support.
The patch was released within a week.
Incredibly fast!
What was good?
1. There was a environment to reproduce the bug.
The game was originally designed as online with auto save only, but OFFLINE could make multiple save data. Therefore, it could be tested repeatedly to check.
--Keeping the environment to reproduce the bug is important!
--Practical use of virtual environments which is easy to handle.
2. Operation at that time was remembered
The condition to reproduce the bug was smoothly determined since the operation was remembered.
--It is necessary to always be aware of what operation you are doing although you tend to be careless when you are testing similar items.
--Irregular exploratory testing is needed.
By making good bug reports, work load of development team is lightened.
It leads to reduce man-hours and higher the quality of the product.
However, letting users do it is a problem...
Official Site:
Surge Concerto Social
