Introduction

November 20, 2011

Hello world.

I am 21yr old student, with a passion for games. I have loved games and gaming since an early age of three. My dad always had me playing games on his computer, such as simple puzzle games and matching card games. Although I didn’t properly start gaming until I was about 8yrs old; the first real game I played was Final Fantasy VII. Since then I have become obsessed with Japanese-styled games, even though they are rare to find and play whilst living in the United Kingdom. My favourite genres of games are RPG, RTS, Puzzle, Adventure and Platformer games.

My main goal in life is to be successful, whilst having fun and being happy. Now I realise the games industry isn’t always an easy place to be, but I imagine the reward after working hard on various projects is worth it. I am passionate about level design, however after having the opportunity to do some QA testing, I discovered that I really enjoy doing it! I am extremely organised and analytical with everything that I do, so I believe that these qualities I have, help push me towards the QA role within the industry.

This is my personal website, however if you would like to go to my professional portfolio, click here.

If you would like to contact me, please email me at:
ShauniMaple@gmail.com

CVLinkedIn Profile

 

—————————————————————————————-

 

Games I have tested:

1. DiRT Showdown (CodeMasters) Tested on the 3rd February 2012 – VOLUNTARY QA TESTER.
2. Motorstorm RC (Evolution studios) Tested on the 6th November 2011 – VOLUNTARY QA TESTER.
3. Unannounced game (Codemasters) Tested on the 25th November 2011 – VOLUNTARY QA TESTER.

—————————————————————————————————

4. Vesuvia (iPlay) tested from Jan – Feb 2011 – QA ENGINEER.
5. Dahlia: Dying for Daylight (iPlay) Tested from Jan – Feb 2011 – QA ENGINEER.

From these QA engineer roles I was responsible for:
• Bug identification using the JIRA system.
• E-mail/Skype communication with development/testing team
• Gameplay testing
• Written reports

I worked for Oberon Media/iPlay for a three week period (of paid work), working as a QA Engineer. I worked from home via Skype, and filling out word documents, and spreadsheets. I gained a lot of experience from working with Oberon Media/iPlay for three weeks, and I would love to work with them again.

—————————————————————————————————

6. Dream Day True Love (iPlay) Tested on Nov 20th 2010 – VOLUNTARY QA TESTER.

—————————————————————————————————

7. Bubble Town: Party Planet (iPlay) Tested from Nov 2010 to March 2011 – VOLUNTARY QA TESTER.
8. Bloom Town (iPlay) Tested from Nov 2010 to March 2011 – VOLUNTARY QA TESTER. –

This testing was done over a long period of time, and I lead the group doing this testing.
We were responsible for:

• Bug identification using the JIRA system.
• E-mail communication with development/testing team
• Gameplay testing
• Identifying balancing Issues
• Omniture testing using Fiddler2 program
• Written reports

——————————————————————————

9. Hydrophobia (Dark Energy Digital) Tested on Nov 3rd 2010 – VOLUNTARY QA TESTER.
10. Downtown secrets (iPlay) Tested on Oct 24th 2010 – VOLUNTARY QA TESTER.
11. Spectrum Shock (Boxfrog games) Tested throughout June to Sept 2010 – VOLUNTARY QA TESTER.
12. The Women’s murder club (iPlay) Tested August 2010 – VOLUNTARY QA TESTER.
13. The Great Gatsby (iPlay) Tested June 2010 – VOLUNTARY QA TESTER.
14. Agatha Christie (iPlay) Tested May 2010 – VOLUNTARY QA TESTER.
15. Buried in Time (iPlay) Tested March 2010 – VOLUNTARY QA TESTER.
16. Deadtime stories (iPlay) Tested Jan 2010 – VOLUNTARY QA TESTER.

From these games I have been involved in, I have gained a huge amount of experience and I really enjoy doing QA testing. Through doing voluntary testing for iPlay, paid work emerged from this and I was contracted for three weeks to work as a QA Engineer.
Tools I have been using throughout the testing is JIRA for logging bugs I have found with a description of the bug and re-creation steps, and I also have used Fiddler2 which logs everything you do on a browser based game, and if a crash happens Fiddler2 can let you know where and how the crash happened, e.g memory related crashing.

CV – LinkedIn Profile

If you would like to contact me, please email me at:
ShauniMaple@gmail.com


Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: