JE7 Task 2

Compatibility Testing: 

This type of testing is done nearing the end of a game, it ensures that the game runs on different configurations of hardware or software. As hardware the compatibility is made for brands of different manufacturers and input peripherals such as gamepads or joysticks.   

It is normally required for PC Titles nearing the end of development as much of the compatibility depends on the final build of the game.

Compliance Testing:

It is a nonfunctional testing technique which is done to validate, weather a game (System developed) meets the organizations prescribed standards or not.

A compliance tester example could be PEGI.

Functionality Testing:

It entails playing the game in some form. Functionality testing does not require extensive technical knowledge, doing this type of testing testers look for general problems such as stability issues, user interface, game mechanic issues and game assets integrity. 

Localisation Testing: 

Localisation testing checks the quality of a product's localisation for a particular target culture/locale. 
This test is based on the results of globalization testing, which verifies the functional support for that particular culture/locale 

It also focuses on any testing done within languages it is not only based in cultures. 

Regression Testing: 

Regression testing is a type of software testing that verifies the software previously developed and tested still performs correctly after it was changed or interfaced with other software. Changed may include software enhancements, patches, configuration changes etc.

Soak Testing:

In the context of video games, involves leaving the game running fro prolonged periods of time in various mode of operation such as idling, paused, or at the title screen. This testing requires no user interaction beyond initial setup and is usually managed by lead testers, automated tools may be used for simulating repetitive actions such as mouse clicks. 
Soaking can detect memory leaks or rounding errors that manifest only over time. 

JE8 Task 2

Bug Report

The following picture is the Bug Report for Kael'Thas bug: 

Use of Living bombs with no mana cost and no cooldown, this bug is done by glitching the abilities of Kael'thas.

 The Bug Report it was made by me and it will be submitted for the creators of Heroes Of The Storm which are Blizzard Entertainment. Sending the bug to Blizzard will make them to know more about the bug so it can be fixed as soon as possible.
Also, the usage this bug report and the bug itself will help to develop the fixing of other similar bugs/glitches.

The report itself explains the specifications of the game and steps to reconstruct the bug in every game. After the report what is expected is the fixing of the bug.

This is the video that shows the bug in an actual gameplay:

https://www.youtube.com/watch?v=PuOPV6XAQKA&feature=youtu.be

The following picture also shows the bug, even though the bug cannot be used in the same target the whole time the advantage that the Kael'thas player will get is unfair.

The red circles and abilities are the spamming of Kael'thas ability.

JE8 Task 1

Bug



This bug allows the player to cast an ability without Mana spending and CD (Cooldown Reduction), basically meaning that the player can use an infinite amount of Living Bombs (W Ability). 

The video demonstrates how the bug is used.  




Type Of Bug

This Bug is an A Type. 

The bug does imply serious fixing because it brings a really unfair advantage to Kael'thas players. 

Even though the game its a MOBA, that means it doesn't have a final, the bug stops the player from completing the game objective which is win. 




Resolving the Bug

Heroes of the Storm is an online MOBA, this is not letting player to complete the games because the Bug is giving supremacy to a champion, using abilities with no Cooldown and Mana cost is a really big advantage to the player that have Kael'thas in their team. 

To resolve Kael'thas bug the correct thing to do its patch Heroes and resolving the problem, and also disable Kael'thas from ranked games so any one can use the bug as an advantage in any game because it would be unfair if is not disabled from the game. 

JE7 Task 3

Classification of Bugs: 

Class A:

The severity of this bug its really high, Class A bugs are the most "dangerous" bugs that can threaten any game.  

They are any bug that causes the game to crash or hang, anything that will stop the player from completing the game.
These are the worst bugs that can be find.

Example: In this example the player can't interact with anything only being able to move around.





Class B: 

Any bug that can hinder the game but it doesn't stop the player from completing the level or product.
They are not as bad as Type A but they are difficult to work with. 

Class C: 

Class C are any type of bug that can cause a problem but not hinder the player or cause any major issue within Gameplay

The majority of C class bugs are graphical, implies character or environment texture. 

An example could be, No Faces Bug - Assassin's Creed

This bug shows the game is affected but it does not hinder the player, the gameplay is just corrupted by the lack of textures within the character development.


Legal Bugs:

Any bug that could create a legal and major issue wit any other company or break copyright or digital laws.

To have any other logo from a Business/Brand or Brand/Business information in the game you will have to get the permission if it is classified as Legal bug it has to be fixed or it will create problems within both entities. 

Performance Bugs: 

These bugs make the performance of the game to drop, examples will be bugs that for example make the game to lag even though the game is optimized and you can run, in these case the bug is affecting the frame rate which causes the lag.

An example would be the Performance bug of Assassin's Creed Unity: The frame rates were lower than what was expected in crowd size in within the game, this is a big problem while playing the game.

Example: If the player is trying to escape through crows and has problem with the frame rate and the performance starts going lower and lower it could affect the gameplay.   


Collision Bugs: 

Any bug that is related to the collision within the game, an example would be a character clipping through an object.

JE7 Task 1

Pre-Production: 

In Pre-Production what is tested is the the engine, the engine is tested to see how much can handle, the testing is based on ow the graphics are gonna be, so or example the graphical art can be 2D or 3D, if we are testing the engine for 3D Games what is tested is ow much resources will consume, so which PC's or Consoles will run the game. 

Depending the engine the graphics could be more surreal or real which makes the developer choose the engine that fits better the game idea.

In the Pre-Production process you should consider the specifications of an average computer or the specifications of a console. This is made to ensure the performance of the game 

Alpha Phase: 

In Alpha Phase early game graphics and controls are tested, it is a really "primitive" form of an actual game in which nothing its really finished. 

Being a primitive form of what the consider is really small, that means graphics tested are basic textures and the overall look and controls is basic movements and actions within the player/enemy/NPC.

Production:

The Production phase is when the assets and coding are done, its the main stage of video game development. 

In the production phase everything is created from control to characters or textures, if it has been created before in previous phases what is done is improvement.

Production is mainly divided in: 

Design, Programming, Level Production, Art Production, Audio Production and the Testing. 

Beta Phase:

Beta phase is an early finished phase in which you can try the game in a short period of time.

In the past was used as just testing phase for creators, but now it is used to promote games.

Betas have a characteristic, they can be either Open or Closed, when is a Closed Beta, the period of testing is restricted to an amount of users.

The difference of Open Beta is that is like a next step after Closed Beta which implies the fixing of bugs/glitches in the Closed Beta, a Open Beta is available to many users if not all general public.    

Some characteristics of a Beta Phase could be: Any % o the actual Quests, Material that could be added or removed in the final product. 

Post-Production: 
Post-production is the stage in where the game is finished and it has to be distributed and it only be tested to introduce new content such as DLC's or any type of "Bug" fixing.

Post-Production in gaming is basically maintenance of the game by patching in a fixed period of time (Example: Monthly patches)

Urgent patches are not included in the example of monthly or weekly patches.