What kind of games the Brazilian market is used to play?

Hello, my dear friends!

We all know that games are all around the world and each company has an interesting on a specific market. Americas, Europe, Asia over mobiles, consoles, PCs. Even more, some companies has being focused on a single style as action, FPS, RPG, platform, etc and trying to get on the market.

But there is one market that has being growing since a few years ago. The Brazilian Market. Most of companies that spare sometime to hire someone that speaks Portuguese to translate/localize their games, are way ahead of other. And its not me that is saying that. The Brazilians are. Ask anyone from Brazil why they are playing that specific game or the other one. Also, we can rely on number.

According to the Sao Paulo Times,  (sorry the website is not in English) only 5% of the population speaks English and only 8% of the Classes A and B speak English. The rest of the news is about getting yourself into the market about the lack of English language. But my point is, back in Brazil, only this class A and B and a little of C have access to the games that are produced in North America, Europe and Asia. Let talk real here: Games are so expensive that most of the Gamers there download it from the internet – illegally. Due to that, they sometimes, do not have access to the updates and translations games – or they do?

Games that are not translated/localized we have forums and groups of these Brazilian Gamers that get together to translate it. I did it myself helping them. That is where I want to get. Brazilian Gamers tend to play more games if they are translated. Of course most of people play them in English and they also say “I have no problem with that” or “I can understand/speak English” but if you put a plot in front of them, they would just press all the buttons to skip that ASAP.

Now, what this all has to do with the Post Title?

Well, a lot of companies are trying to get into the Brazilian market – and a lot of them did it really well – but what kind of game do you have to introduce to reach success in Brazil? That’s where the answer of the questions comes in handy – and the news – (Sorry again, this news is in Portuguese, but I’ll translate below, in a short). So, if you want to know more about the Brazilian market and how translation/localization is important, you can check this post.
18/12/2014

Simple Games are the ones with more downloads for cell phones in Brazil on 2014.

The news page (G1) had access to the TOP 5 games from Google Play. Store is the one that attend the largest quantity of smartphones and tables of the country
TOP 5 downloaded games has being compiled according to the number of downloads of this kind of games at Google Play. Unfortunately, Google didn’t release how much downloads each game had.
Still, here are the games:

POU

Yes. POU. Simple as a Tamagochi, the objective of the game is to take care of this weird thing, feeding it, cleaning it and putting it to sleep. And when you get boring of it, you can add you POU to some competitions, simple ones, but at least they are competitions.

The app has also an option to print a 3D version of it. Before that, you could buy your POU as a toy.

MY TALKING TOM

 
 

My Talking TOM is can also being printed and, if you like cats, this one is for you. You can tap the cat, watching him stretch, hug him, play with him, wash him…. almost like a POU but with legs and arms and a real face. Another interesting thing is that he can record what you tell him and repeat with a thin and annoying voice (believe me, I have some nephews that played with all day long). Also, according to Outfit7, the game has been downloaded more than 230 million times around the world.

SUBWAY SURFERS

 
 

Alright. Another one that I didn’t even imagine that would have on the TOP 5, but that’s okay. We have this one, Subway Surfers. On this game you have to avoid trains (really) and collect coins on the way. Nothing special about it, but the simple fact that is simple.

DESPICABLE ME

Alongside Subway Surfers we have Despicable Me where you have to control the Minions and collect bananas, fight bosses and more. I haven’t play this one, but I’d just because of the Minions. I like that: There, I said it.

Created by Gameloft, one of the specialized game companies over licensed games, they are one of the icons at the mobile generation. Since 2000, they have more than 500 apps published, which has been downloaded more than 1,7 Billion times. (Note: I did play some games from Gameloft and I’d made some changes in a few of them, maybe adding something… anyway). The company is here and is keeps growing like there’s no tomorrow.

TRIVIA CRACK

 
 

Some of the companies above may scare some other due to the large number of downloads. But the market still have space for other and small companies that are looking for a place to grow. The Argentinian company Etermax has less than 10 games published. The game is a real exception at this list because is asks more than just doing tickles at your smarphone.

CONCLUSION
 

So, what do you think about it? Did you know that this simple games could be the ones with more downloads in Brazil? More, I cannot say if people kept playing them, because it only says the downloads and I could have downloaded it and, after 5 minutes deleted it.

However, is important to underline that, all of this games has its own Portuguese version and this, you can believe, is one of the reasons that it reached those positions there.

So, what about getting someone to translate your games and get into the Brazilian market? What are you waiting for?

Advertisements

Worst Translations on the Game History

We all like to play a game on our own language. It helps with quests, understanding the game, the plot, the story behind everything, etc. But what happened when the developers/publishers hires poor translators? Or maybe, they are in such a rush to release the game that “a few” mistakes follow it until the release?

Well, games mostly came from Asia, Europe and North America and I’ve started seeing some games in Portuguese-Brazil, which is pretty amazing! I have no problems reading and understanding English (yet my blog may have a lot of misspellings and grammar error… sorry) I can play an English video game with no problems. Not Japanese. No. This one is out of the questions. All those little sticks around the screen…. naaa).

Now, let me tell you a good example of localization and translation. WORLD OF WARCRAFT, from Blizzard. I’ve always been a lover of that game and, when that started 10 years ago I was one of the firsts to play and created a character. That time the game had just a few places to explore and it was all in English. Choosing a class, race, weapons, quests, talking to people. I also have to thanks Blizzard because they kind of helped me with my English. 🙂

However, for other reasons, I had to stop playing. No more. Moved from my city, got a job, had to by a better computer, no money, lots of work – in a short – had to grow up. Recently, about 3 or 4 months ago I decided that I could go back and play again. Some of my friends were in there, talking about all the updates, news enemies, places, quests and biggest of all THE GAME WAS IN PORTUGUESE. First thing that came to me. That’s impossible. Translated to Portuguese? That’s probably a mess. No way they are going to be able to translate it. I was wrong.

For the first hours playing I found a little weird, after all I was used to English. After playing for a few days, I was convinced that they did a pretty good translation and not just that. They did localized amazingly well. There are somethings that deals directly with the Brazilian culture and I thought that was considering interesting. Not only caught my attention, but my feeling to keep playing and discover more things about it. Explore it more and more.

In a nut shell, you guys understand what a great translation and localization does with the player when it is well done? If I felt that way, imagine the millions of players in Brazil.

NOW, what would happen if the opposite? A bad translation/localization? Or a rush one? Even with great games that you loved in Japanese, but the English version went down the sink. You can check below.

10. FATAL FURY SPECIAL

Fatal Fury may be one of the games with most translations problems. I found a lot of them over the internet and its a huge example of rush release.

“Your fists of evil are about meet my steel wall of niceness”

Okay. What is wrong with this one? As far as I can understand, the grammar is missing a “to” so far. But, wait “wall of niceness”? Is that really a word that we use? Even if you won a battle and want to put the enemy down. Beware of my WALL OF NICENESS. Come on…..

9. GHOST N’ GOBLINS

“This story is happy end”

Beside this game be EXTREMELY difficult and you have to play it with no power bar and two lifes (but unlimited continues) and also have to beat it two times for the “real” ending, it is a really nice one. Now, This Story is a Happy End really made me think… a lot…. and after that you may also find “being the wise and courageour knight that you are you feel strongth welling in your body. Return to starting point challenge again.” Not my mistakes, just copy…..

8. GHOSTBUSTERS

Hey, it is really a great game (besides I’ve to hear the same song THE HOLE GAME) and I am glad I’ve completed (FINALLY). I also proved (NOT PROOVED) the justice of our culture and lets go and rest our heroes. This is fin….. OH WAIT. WHAT? Conglaturation? Really? What was that? Guess someone is missing the R feeling….

7. METAL GEAR

Another great game with some great sequels, but some problems with the English language. What do you feel asleep? Legs? Arms? hands? Its an old game and good to see that they learned their lesson (not on this one). You can also find things like “The truck have started to move” and “Attempt to contact missing our Grey fox”. Nowadays, the problem is just the explanations are hard to understand. Simple.

6. THE LEGEND OF ZELDA II

All right. You may be the first one of many errors. One of the programmers errors or just a misspelling ? Some people would say that this character was supposed to be called Ellor or Elrol or Errol or whatever but, as some oriental are pretty good in English, some how it just came as Error. Hi, my name is Error. Pretty weird….

5. DOUBLE DRAGON III

Another amazing game that I’ve played for hours when I was young. Had to buy for my consoles and play with my friends. However I am not quite sure about Jimmys partner. BIMMY. Weird enough, do you know anyone named Bimmy? Unless you know some Jimmy and may call him a little bit sick…. Bimmy? Maybe? naaa…..

4. FINAL FANTASY IV

Spoony bard? Really? You want to threat me with that? Oh, my! I am sorry to come into your humble house. Anyway, this is know wrong, talking about spelling, its just weird…

3. X-MEN: THE ARCADE GAME

“WELCOME TO DIE”

This is not actually on the text, but he says that. Really. I had to go after the video to check it myself. Couldn’t they think on anything more interesting to say? What the hell, spell doesn’t apply for the master of magnet.

2. PRO WRESTLING

Oh, thank you. a Winner is me! I feel like being taught by Yoda or something….

1. ZERO WING

After watching a few videos, I have to admit, almost every line is a pearl. He is about to kill and destroy everyone and has time to say “how are you gentlemen?” really? and “all your base are belong to us.” and “someone set us the bomb” and that goes on and on. Please…..

CONCLUSION

I could go over and over talking about it. I found so many information over bad English translations on video games that I’ll probably do more posts about it.

However, the reason of this post is to show how important is the spelling on a game. It doesn’t matter if the game is good (yes it does) but a bad spelling can ruin everything. Imagine it World of Warcraft had such problems like that? It would turn into a joke instead of a great and amazing game. I know that also my blog and the way I speak are not free or error (besides English be my second language) but even in Portuguese, where I studied for my whole life and went to two universities, I still make mistakes.

The point is, back at that time, they didn’t have what we have today. Ways to communicate. Tools to search, correct and fix. We have the internet for it. Is there, you just have to click it. Unfortunately, eve with that, we found some problems on the recent games. Not quite as before, but they are there. Do not believe me? Check this out that I found.

BONUS ROUND

People in Brazil tent to translate a few games that they like, just for fun or to help another to understand the game and spread their work. However, they tend to use the internet the wrong way. Not searching like it should or just using Google Translator to do the job. You can’t rely on a machine to do your job and translation and localization deals directly with the way a culture works and how you will introduce that to them. A machine can’t do that (as far as I know…).

So, lets check it out and I’ll try to translate from Portuguese to English so you can “see” what I “see”.

This one is simple asking is she is weak on sex, like, “And me? Am I weak in sex?” Guess they try to if she is the week sex…
I was trying to understand what the heck my comrades were trying to do here. For you guys to understand, it says “Why don’t you let me take care of your butt so I can leave the environment more…” you get the idea. Using your imagination, I believe he tried to translated from the English:  “Why don’t you let me watch your back…”

And this is little bit porn, so please, do not sue me for that. Simple, its says “Stop cumming on my face, Mai”. I guess it was stop mocking me or stop making fun of me, but we (Brazilians translators) did a really good work and that’s the result. Google Translator is the one.

So, that’s it. I hope I have time to work on other posts like that.

Can a game really change History?

Hi. How are you?
Have you ever had questions about the history of your country? What did really happen back there, why, who died, who were traitors and who where allies?

Well, some people take that really serious and, specially, politicians. Why? Because everything regarding to politics history they have to talk about it. I myself see this as an opportunity to teach children and players what history was really like and to bring them to know better that. Also, that would be a really difficult post to do, because I may fell like stepping on eggs, but, anyway, let’s give it a try.

I came to a New York Times news from Nov. 20, 2014 talking about a interesting situation that happened with the French company Ubisoft. We all know that their games are awesome and sell a lot of copies around the world. But, what happened when you build a game based on a specific history of a specific country? A lot of people may say, “nah, that’s okay, because the game used the history to create a Fantasy world and I know that is not for real”. Other would say, “if you create something based on history, you have to study it. No just consulting books and the internet, but really study. Otherwise, it will be a pour game.”
I’ve played some amazing games regarding to history, specially FPS War ones. Call of Duty, Medal of Honor,Battlefield, etc, and I actually liked most of them because was a way for me to learn about history while playing. I’d also enjoy playing a game based on Brazilian history, where I am from. I know my history, what happened, I know who were traitors and who were “good” people. Why? Because I went to school, I studied. And every time there were something that I didn’t get it, I went after it or even read the manual of the game as the historian who advised Ubisoft, Jean-Clément Martin. As he said, the game was not intended to as a French-bashing or historical revisionism, but to create a fantasy world where players could have a different view of history.
Still, that’s my opinion and I’d probably keep talking about over and over again, but I prefer to leave up to you. Read below the news and let me know what you think.
Again, to check the full text, check here!
Video Game Meets History, and France Rebels Again
By DAN BILEFSKYNOV. 20, 2014
PARIS — Perhaps only in France could a video game provoke an earnest philosophical debate over the decadence of the monarchy, the moral costs of democracy, the rise of the far right and the meaning of the state.

The French are fulminating over the game, Assassin’s Creed Unity, not because of excessive violence as Americans might, but over its historical inaccuracy and political slant. Critics on the left say the game undercuts a cherished narrative of the French Revolution — the miserable masses rising up against an indulged nobility.

Set in a meticulously rendered three-dimensional Paris during the French Revolution in 1789, the game is part of a popular series whose previous versions have been set during events like the Crusades and the American Revolution. The series, made by the French company Ubisoft, has sold nearly 80 million copies since it was introduced in 2007.
In the game’s latest incarnation, released last week, the hooded hero is Arno Victor Dorian. A young Frenchman whose father was assassinated at Versailles, he takes no small measure of glee as he jumps across the rooftops of Paris, including the Cathedral of Notre-Dame, mercilessly killing members of the nobility and other rivals with his “phantom blade” or pistol.
Critics of the game, led by Jean-Luc Mélenchon, the firebrand left-wing politician and onetime presidential contender, have lambasted it as dangerous “propaganda” that portrays the French masses as bloodthirsty murderers, while the high-living Queen Marie Antoinette and King Louis XVI are shown sympathetically.
At a time of economic and political doldrums, when the far right National Front is on the ascent and the Socialist president, François Hollande, is deeply unpopular, Mr. Mélenchon warned, on France Info radio, that the game threatened to fan “hatred of the Republic,” which he said was widespread among the far right today.
The video game reflected a current strain of self-hatred in France, he said, suggesting that it was perilous for national identity.
“Smearing the great revolution is dirty work that aims to instill the French with even more self-loathing and talk of decline,” Mr. Mélenchon told Le Figaro, a French newspaper. “If we continue like this, no common identity will remain possible for the French besides religion and skin color.”
Mr. Mélenchon fumed that the game did not repudiate Louis, a “traitor” who, according to historical documents, he said, had tried to get foreign armies to rescue him before he was executed.
He said “that cretin” Marie Antoinette, who was queen of France from 1774 to 1792 before meeting her end at the guillotine, was erroneously represented as a “poor little rich girl” even though, Mr. Mélenchon said, she tried to conspire to have France invaded.
Perhaps the greatest target of his ire is the game’s depiction of Robespierre, whose reign of terror against the perceived enemies of the revolution has made him a villain to some critics who view him as a tyrant.

Mr. Mélenchon told France Info radio that the game’s denigration of Robespierre as a “monster” did not consider his role as a “liberator” and the leader of a movement that gave Jews the right to vote and tried to do the same for women.

Ubisoft has defended the game, and one of its producers, Antoine Vimal du Monteil, told the newspaper Le Monde that Assassin’s Creed was, after all, a game and “not a history lesson.”
Emmanuel Carré, a spokesman for Ubisoft, said by phone that 1,000 people had created the game over three years and that thrills for the player had taken precedence over historical accuracy.
“This is France, where everything becomes politicized, including video games,” he said. He said the game sought to capture the complexity of characters like Robespierre and Marie Antoinette.
On a blog hosted by Mediapart, a news website, Jean-Clément Martin, a historian who advised Ubisoft on the game, wrote that Assassin’s Creed Unity was not intended as French-bashing or historical revisionism, but rather was meant to create a “fantasy.”
“Let adolescents, young and old, play,” he wrote. “Perhaps they will get the idea to go read a manual or a history book, and everyone will have won.”
So, what do you think?  Really believe that is something to care about or just let the game be?

The dark side of being a Game Tester

Good morning, everyone.
In one of my searches through the internet, I found myself, 12:06am on a Saturday night reading about the bad things of being a Game Tester. I’ll tell you the truth, I’ve seeing a lot of texts and complains from a bunch of people that work(ed) with Game Testing. But these guys are definitely throwing everything out of the window. Its an old text and, probably, a lot of things change on this 2 years (I hope…).
However, do not understand me wrong. I do believe that a Game Tester job is pretty hard and tough. Hours and hours testing the same part of a game that you didn’t have the opportunity to choose, working overtime more often then you may think…. we could keep talking about it forever, but I will let the people from ca.ing.com do the trick.
You can check the full text and everything in here, source of the text.

The text is also good for the bosses and managers to see how the market is treating those people. We are Game Tester, but we DO have feelings. 🙂

Thanks to Jimmy Thang for it.
THE TOUGH LIFE OF A GAMES TESTER
 
QA testers break NDAs to tell IGN about challenging working conditions, poor compensation, and lack of morale.
 
BY JIMMY THANG

What gamer hasn’t dreamed about playing games for a living? While this may seem like a great career, and a cool way to get a first job in the games business, the truth is less appealing.
 
IGN reached out to quality assurance (QA) testers from all over the world to hear their sides of the story. We received dozens of emails from contributors across numerous game companies. They told us stories of demanding working conditions, low pay and shaky worker morale.
 
They have been employed by a broad range of publishers, including traditional games publishers and newer outfits operating in the mobile games business.
 
QA testers sign non-disclosure agreements (NDAs) with their employers and can be fired or even sued for divulging information. All the testers we contacted spoke to us on condition of anonymity. We have given them pseudonyms to protect their identities. We have checked each of their credentials. We asked for comments from a variety of games publishers, but have received zero responses.
 
 
Tedious Tasks
 

While the job may sound like a dream come true, Reuben says it’s really not about getting paid to play games all day. “Imagine your favorite movie. Now take your favorite 30-second clip from that movie. Now watch that 30-second clip over and over again, 12 hours a day, every day for two months. When you’ve done that, tell me if what you’ve been doing is watching movies all day. I’m willing to bet you’ll find that it’s not quite the same thing…You get an area of the game, that’s your area, and you test everything about that one area for months on end.”

Furthermore, testers don’t get the luxury of choosing the titles they’d like to play. “It’s very boring playing a kid’s game over and over,” says Rich.

Frank adds, “I have seen people quit gaming because of the frustration of the process plus the repetitive nature of playing a game that you may hate or not recognize as something you would play. You get jaded.”
Poor Compensation

 
Though some boring and repetitive jobs can pay decently, game testers do not get compensated nearly as well. Because the industry is made up almost entirely of contractors with zero union protection, they receive no benefits or negotiating power.

Companies often pay contractors a higher base pay in lieu of benefits, but Danny only made $10 an hour. Extrapolating this data, means the average salary for a full-time position is roughly a meager $20,800. The federal minimum wage is $7.25, but game-testers are information workers, not burger flippers. It takes skill and knowledge to test and judge a game.

Though the industry doesn’t pay well for entry-level positions, what about more seasoned QA testers? Danny says, “I work with a guy who has spent the last eight years keeping his nose clean, never in fights with leadership, does whatever is asked of him, and is a freaking QA Ninja when it comes to PC testing. After eight years, he is still paid $14 an hour. I just think we’re worth a whole heck of a lot more than $10 an hour.” He believes that game developers/publishers should “offer some benefits like they do the rest of the company”.
 
 
Lack of Respect

 
Keith tells a story about how his employer was too cheap to give him a promised copy of the game he’d worked on. He wrote, that “after two months and forty hours a week of playing this game, there was no way in hell I was going to buy it.”

While financial benefits are one form of compensation, Danny believes that respect is also severely lacking. “We deserve to be treated like regular employees, instead of someone you don’t invite to your Christmas party but then tell them to have their own last minute [party] in another building through the back entrance…True story.”

“I am absolutely not alone in these feelings,” he adds. “Most probably won’t voice their opinion for fear of getting fired; others who might are already out of the industry because of the very conditions I’m talking about.”
 
 
Harsh Working Conditions

 
Unlike typical nine-to-five jobs, the final months leading up to the release of a videogame company’s product have been come to known as “crunch time.”

According to tester Pete, there were numerous occasions in which he was neglected pay. “They had us stay overtime on the studio for a particular game release, but they never paid those extra hours worked.”

For Frank, this meant mandatory overtime every day. “It got borderline illegal. It got to that point when I was so tired at three or four in the morning that I passed out a couple of times. Others did too and not anyone of us disturbed that person. We just let it go for a bit and brought each other back to life when we needed to.”

Sleep deprivation wasn’t the only way these harsh hours physically affected Frank and company. “Our nutrition habits were horrible. The only thing near us that was open at those hours: a McDonalds attached to a Chevron station that we quaintly called ‘Chevronalds.’ I was feeling like s*** and I just wanted to get it over with.”

Reuben says that maintaining a healthy family life extremely difficult. “Once the overtime starts, the hours seem to be nearly endless…My longest period of straight overtime lasted just over seven months where my shortest work week was 65 hours and my longest was 92. This was stretched out over two projects that just bled straight into each other.”

 
Poor Job Security

 
Compounding the physical and mental stresses that QA testers endure was the complete lack of job security. “During training, they told us it’s not a matter of ‘if’ you’ll be laid-off but ‘when’,” says Keith. “They flat-out tell you that what makes a good employee is the number of bugs you find and it is this number that will determine if you are kept on or not.” This methodology, however, did not accurately take into account the quality of dedication that went into a project. “Here I was recreating and logging how to get stuck in the tail of a helicopter. I would have other testers comment on how much they liked my bugs, because I was one of those guys who would be able to reproduce those bugs that stumped everyone else, but when it came to the end of the project, the guy next to me had more bugs, so I was laid-off and he was not.”

If being laid off isn’t bad enough, finding continued employment is also difficult. “Everyone tries to advance to positions that aren’t available and won’t get,” says Phil. While this may also be true for other careers within the games industry, he believes this problem is compounded because testers are often hired through a staffing company and not internally. Many publishers won’t offer a reference because of contractor policies. Most testers are not, technically, employees.

Reuben explains, “The majority of people will come in, give up their outside lives for six months to a year, and then be let go. It’s disheartening to see so many people you’ve spent so much time with be laid off like that.”

While being laid off can be a part of any career, he adds that the process is cold. “The way [my employer] used to handle these things was to send out meeting notices. You would go to a meeting, and someone would walk into the QA area where everyone who didn’t have the meeting request were still sitting and simply say, ‘If you’re here, you’ve been let go, pack up your stuff, we’re escorting you out’…you always hoped that you would be one of the few that would be kept on.”

Compounding the physical and mental stresses that QA testers endure was the complete lack of job security. “During training, they told us it’s not a matter of ‘if’ you’ll be laid-off but ‘when’,” says Keith. “They flat-out tell you that what makes a good employee is the number of bugs you find and it is this number that will determine if you are kept on or not.” This methodology, however, did not accurately take into account the quality of dedication that went into a project. “Here I was recreating and logging how to get stuck in the tail of a helicopter. I would have other testers comment on how much they liked my bugs, because I was one of those guys who would be able to reproduce those bugs that stumped everyone else, but when it came to the end of the project, the guy next to me had more bugs, so I was laid-off and he was not.”

If being laid off isn’t bad enough, finding continued employment is also difficult. “Everyone tries to advance to positions that aren’t available and won’t get,” says Phil. While this may also be true for other careers within the games industry, he believes this problem is compounded because testers are often hired through a staffing company and not internally. Many publishers won’t offer a reference because of contractor policies. Most testers are not, technically, employees.

Reuben explains, “The majority of people will come in, give up their outside lives for six months to a year, and then be let go. It’s disheartening to see so many people you’ve spent so much time with be laid off like that.”

While being laid off can be a part of any career, he adds that the process is cold. “The way [my employer] used to handle these things was to send out meeting notices. You would go to a meeting, and someone would walk into the QA area where everyone who didn’t have the meeting request were still sitting and simply say, ‘If you’re here, you’ve been let go, pack up your stuff, we’re escorting you out’…you always hoped that you would be one of the few that would be kept on.”

Frank says, “Once the product ships, you’re out of a job. There are no benefits, no perks and definitely no promise of being hired full time. There have been so many talented people I have worked with and it’s a shame to see that talent getting wasted.” While some organizations offer job protection, “there is no union for QA contractors” he adds.

Could testers form a union? While it is theoretically possible, Reuben believes it isn’t realistic. “Forming a union at the tester level is next to impossible due to how contracts are handled. If you try, you’ll find your contract not being extended. The part that really hurts is that the industry is so small that if for some reason you are let go, most companies in your area know about it and won’t hire you.”

 
Facing the Blame

 
Even after passing through QA, it’s still commonplace for today’s videogames to have bugs both small and game-breaking. Take the PlayStation 3 version of Bethesda’s Skyrim. If QA testers work as fervently as they claim, how can such technical travesties slip through the cracks?

The truth, according to Phil, is that “many reported bugs don’t get fixed.” Furthermore, developers often ignore the advice of QA testers. Frank says, “They shot our opinions down without even a slight bit of consideration. They waste money and resources” before faulty projects are canned.

“Sometimes game companies have to pick and choose their battles and decide what bugs must be fixed,” says Trent. “The thing about QA testing is that not everyone games the same. There are millions of combinations of things a gamer could do that a team of 100 or less won’t find and it ends up in the final product.” This, combined with some bugs not being repeatable, explains why catastrophic glitches are able to seep through. “There were plenty of times you would find a bug, but if you can’t write up a detailed way to reproduce the bug, you can’t count it, even if it’s game breaking…You must be able to make it always happen or happen often enough for it to be reported.”

Even when developers listen to the QA team, issues can still arise. Trent adds, “Sometimes the developers swear they fixed something, but the next build of the game breaks something else that wasn’t an issue or sometimes their fix doesn’t solve the problem.”

Though many of these glitches may not be the fault of QA testers, Saul, who declined to name the company he worked for, stated. “The company blames us for all the bugs that make it into the final product.” Pete notes that “Producers don’t listen to QA anymore….but if a bug shows up when the game goes live or gold, that’s QA’s fault, even if QA previously reported it as an issue.”

To avoid delays, Sam says publishers “bully” their QA testers to “get projects to retail on expected time tables, meaning excessively long hours.” He described one employer as “very totalitarian” in the way it treated QA staff. Among the testers who contacted IGN, this was a common complaint about a variety of publishers.

Conclusion (from the author of the text)

While the popular view of the game tester living an easy life is a misconception, there are alternatives to the over-worked, mistake-prone model that testers have reached out to talk about. Companies like Valve and Blizzard are famed for taking their time finishing games and eradicating bugs although, for different reasons, this is not always a luxury available to companies squeezed by stock-holder expectations. Other companies are opening up their games to the public via crowd-sourced beta programs, which creates a whole new set of issues.

History has demonstrated that when QA testers are a more integral part of the development cycle, game companies end up with a better product, greater sales, and most importantly, perhaps create more humane working conditions as a result.

IGN would like to thank all the QA testers who spoke to us. Let us know your thoughts in the Comments section.
 
 
Conclusion (from the author of the Blog! ME!)
 
 
I always wanted to get inside the game industry. I studied about it, watched videos on the internet, read books. But texts like this just makes me feel like “I am going on the wrong way” or “DO NOT get into the game industry”.
 
If you don’t have any experience, this is, maybe, the fast way to get inside the market. People need to know what you are capable of. Imagine that you want to start your own supermarket, will you start as a manager or as a cashier? I am not saying that you cannot open from nothing your own supermarket, if you have money, but what if you don’t, like me? I would take a job as a Game Tester, but would never stay like that forever.
 
The market is full of opportunities but you have to be ready for it. Being a game tester for 7/8 years and never moved on (studying or taking some courses, college, degrees) I sure don’t agree with it. If you want to move up, go after it. I’ve seen many people open their own game company.
 
Now, I’d also say not to believe in everything you read on the internet. People tend to talk extremes about everything. You may find some hard time being a game tester. I worked on jobs that was asked to stay late working, do overtime, do more that I should do, etc, but you sure will find some light on the path. Friends that you will make, games that you will love to work with, companies that you will like to work, things that you will learn, etc.
 
If getting inside the game industry is what you want, again, then go after it.
 
Still don’t get the idea how is to be a Game Tester? try this game.
 
 
 
 
Well, that’s it for now. Hope you guys liked the text.
 
See you next time.

QA interview questions and answers – Part III

Oh, Yeah. We are here at the final part of:
 
QA INTERVIEW QUESTIONS AND ANSWERS – PART III
 
Don’t worry, it won’t be like Star Wars or Star Trek with so many sequels. We just go to the last part and you can learn (almost) everything that you need to know to keep study about QA and turn yourself into a GURU of the Game Industry and everybody will love you and want to hire you and and …. ok, back to Earth, lets read it!
 
SOURCE: carrierride.com 
 
QA interview questions and answers – Part III
QA interview questions and answers – contributed by Rohit Srivastava

 

Q51. What is the role of Bug Tracking System?

The Bug Tracking System role is discussed below:
  • Testers and developers can know the status of the bug at every stage.
  • Changes to the Status will be available to all team members.
  • Developers and Testers can easily interact with bugs.
  • Repetition of bugs will be avoided.
  • Easy to distribute the bug among the developer.
  • It will act as a centralized one for defects.

 

Q52. How do you prioritize testing tasks within a project?

Test Process are execute in step by step. We cannot skip any of the process defined. 

Following is the Test Process which are in terms of their priority:

1. Preparation of Test Plan.
2. Preparation of Test Cases.
3. Execution of the Test Cases.
4. Defect report and tracking.
5. Test Report Summary.

 

Q54 Describe Bottom-Up and Top-Down approach in Testing.

Bottom Up Approach:
  • The bottom up approach testing approach is carried out with the help of the test driver. The test driver calls a component to be tested.
  • The modules in the lower level of call hierarchy are tested independently. Then the next level modules are tested that call previously tested modules. This is done repeatedly until all the modules are included in the testing.
  • Bottom up testing stops when the top module in the call hierarchy is tested with all lower call hierarchy modules.
    Top Down Approach:
  • the top down approach is carried out with the help of the test stub. Test stub are the dummy programs. The Stub is called from the software component to be tested.
  • Tests top layer of controlling subsystem first. Then combine modules that are called by the tested modules and test resulted collection of modules.
  • Do this until all the modules are combined and tested.

 

Q55. What methodologies do you used to develop test cases?

For developing the test cases we use following strategies:
  • Error Guessing: The tester has to guess what fault might occur and to design the tests to represent them.
  • Equivalence Class Partitioning: The input domain data is divided into different equivalence data classes; take few valid values with 2 invalid values. This is used to reduce the total number of test cases to a finite set of testable test cases.
  • Boundary value analysis: Boundary value analysis testing technique is used to identify errors at boundaries rather than finding those exist in center of input domain. Boundary value analysis is a next part of Equivalence.

 

Q56. What are the differences between test strategy and test plan?

The differences between these two are described below:
  • Test plan is dynamic where as test strategy is static.
  • Test plan is prepared by the Test Lead where as Test Strategy is prepared by the company management.
  • Test strategy defines: methods and coverage criteria to be covered test completion criteria, prioritization of the test where as Test plan is a document describing the scope, approach, resources and schedule of intended test activities.
  • Test Strategy is a high level description of the test levels to be performed where as Test plan is written record of the test strategy and resource planning.

 

Q57. What is the need of Test Plan document?

Test Plan tells the tester that what needs to be tested and how testing is going to be performed. Test plan also tells that what resources are needed for the execution of the test cases, timelines and risk associated with the test plan. We can also perform the testing without test plan document, but first we have to select test Approach for the testing and go with testing. Many test plans are being created just for the sake of processes. Many tester use test plan documents when test plan document contains the some useful information.

 

Q58. Why we do load and performance testing?

Load Testing: The reason to perform the load testing is to determine response times of application processes and transactions to establish whether they are within acceptable time limit or not, as per user requirement. It also measures the capability of an application to function correctly under load by measuring the systems key performance indicators.
Performance Testing: Performance Testing is performed to determine response time of the some components of the system perform under a particular workload. It is generally measured in terms of response time for the user activity. It is designed to test the overall performance of the system at high load and stress condition

 

Q59.What is difference between test effectiveness and test efficiency?

 

  • Test Efficiency is the ratio of number of test cases executed by unit of time (generally per hour).
  • It is the amount of code and testing resources required by a program to perform a particular function. Test Effectiveness evaluates the effect of the test environment on the application.
  • Test Effectiveness is a measure by the customer response on meeting product requirements where as Test Efficiency is a measure of optimum utilization of resources to create the Software product.

 

Q60.What is data driven testing?

Data Driven is an automation testing part in which test input or output values, these values are read from data files. It is performed when the values are changing by the time. The different data files may include data pools, csv files, Excel files. The data is then loaded into variables in recorded or manually coded scripts. For data driven testing we use Parameterzing and Regular expression Technique.
Ex. Let we want to sign up to create an account in Gmail for 100 users. For this we pet all the user detail in a single excel sheet or use a single script.

 

Q61. Can Manual Testing be completely replaced by Automation Testing?

Automated testing cannot replace manual testing because of following reason:
  • Automated testing cannot replace the analytical skills required to conduct testing. It can only enhance or supplement manual testing,
  • Through manual testing, information can be gathered about the application, and real-time decisions can be made about how to enhance a test that would be too difficult to program into an automated script.
  • We need a manual tester to analyze and maintain the automated scripts after they can run.

 

Q62 Why regression testing is important?

Regression Testing: When changes in the code of the software are made to fix the previous bug. Then testing needs to be perform to ensure that it will not generate a new bug in the application and it works as specified and that it has not negatively impacted any functionality that it offered previously. Regression Testing is important because of following reason:
  • That the application works even after the alteration in the code were made.
  • The original functionality continues to work as specified even after doing changes in the software application.
  • The alteration to the software application has not introduced any new bugs.

 

Q63. What is Exploratory Testing and Specification-Driven testing?

Exploratory testing: means testing an application without a test plan and test script. In exploring testing test explore the application on the basis on his knowledge. The tester has no knowledge about the application previously. He explores the application like an end user and try to use it. While using the application his main motive is to find the bugs which are in the application.
Specification-driven testing: means to test the functionality of software according to the user requirements. In this, tester inputs multiple data and monitors the outputs from, the test object. In this testing tester evaluate the showstopper bugs which break the major functionality of the application. This type of testing requires test plan and test.

 

Q64. Explain CMM.

Capability Maturity Model (CMM) is divided in five levels:
1. Initial: The organization is characterized by an adhoc set of activities. The processes aren’t defined and success depends on individual effort and heroics.
2. Repeatable: In this level some processes are repeatable, possibly with consistent results.
3. Defined: In this level, we define all processes are documented for both management and engineering activities, and standards.
4. Managed: Detailed measures of each process are defined and product quality data is routinely collected. Both process and products are quantitatively understood and controlled.
5. Optimizing: In this we optimize the application by following improvement process.

 

Q65. How do you decide you have tested enough?

The principle of testing says that exhaustive testing is impossible. i.e. testing everything is not feasible. We cannot test till all the defects are debugged and removed, it is simply impossible. We have to stop testing and ship the software. We can decide when to stop is testing based on following points:
  • When there is no time and budget.
  • When maximum number of test cases are executed.
  • All the Requirements are mapped that is RTM is filled completely.
  • When Test coverage is more than 80%.
  • When bug rate falls below certain level.

 

Q66. What the purpose of testing?

Software Testing: is the process of assuring that product which is developed by the manufactured by developer is meeting the user requirement. The motive to perform testing is to find the bugs and make sure that they get fixed. The purposes of testing are following:
  • Quality assurance, Verification and Validation,
  • To find the bugs before the product is released to customer.
  • To improve the quality of the product
  • The Purpose of Testing is to evaluate that the product is according to requirements
 
 
So, that’s it. I hope you guys found this so amazing as I did and, probably, I will read everything again because there is so much information that I have to write it down and search for it, piece by piece.
 
See you guys around in Ottawa and don’t forget to turn out the lights on the way out! 🙂

66 Software Quality Assurance, QA interview questions and answers – Part II

Hello! Good Morning! How are you guys today?
 
So, as said before, note the Part II of the 66 Questions of Quality Assurance, from careerrider.com and thank you to Rohit Srivastava.
 
If you want to check the SOURCE of the text, just click here. But if you do want to help me and access the blog and reading my comments and everything, stay tune for the next episodes. 🙂 I try to break on small posts so it would be one huge post – I really don’t like big posts because sometimes people feel like “Oh, my, I do have to read ALL of it?” or maybe you only have a few minutes from lunch to read it and don’t want to start all over…. whatever.
 
It is also pretty interesting that most of the questions are related to a products than to Softwares, but I do believe that this is also important to know. Knowledge is never enough!
 
So, here we go! Enjoy!



66 Software Quality Assurance, QA interview questions and answers – Part II
QA interview questions and answers – contributed by Rohit Srivastava
 

Q21. What are test driver and test stub and why we need them?

 

  • The Stub is called from the software component to be tested. It is used in top down approach.
  • The driver calls a component to be tested. It is used in bottom up approach.
  • Both test stub and test driver are dummy software components.
We need test stub and test driver because of following reason:
  • Suppose we want to test the interface between modules A and B and we have developed only module A. So we cannot test module A but if a dummy module is prepare, using that we can test module A.
  • Now module B cannot send or receive data from module A directly so, in these cases we have to transfer data from one module to another module by some external features. This external feature used is called Driver.

 

Q22. What is Monkey testing?

Monkey testing is a type of Black Box Testing used mostly at the Unit Level. In this tester enter the data in any format and check the software is not crashing. In this testing we use Smart monkey and Dumb monkey.
  • Smart monkeys are used for load and stress testing, they will help in finding the bugs. They are very expensive to develop.
  • Dumb monkey, they are important for basic testing. They help in finding those bugs which are having high severity. Dumb monkey are less expensive as compare to Smart monkeys.
Example: In phone number filed Symbols are entered.

 

Q23. What is Bug Triage?

Bug triage is a process to:
  • Ensure bug report completeness.
  • Analyze and assign bug to proper component.
  • Assign bug to proper bug owner.
  • Set appropriate bug priority.
  • Adjust bug severity properly.

 

Q24. What is Traceability Matrix?

Traceability Matrix is a method used to validate the compliance of product with requirements for that product. The requirement is written in a row of the matrix and the columns of the matrix. Now they are used to identify how and where each requirement has been addressed.
 
It is in the form of table that correlates two base lined documents that require a many-to-many relationship. It is used with high level requirement and detailed requirement of the software product to the matching parts of high level design, detailed design, test plan, and test cases. The relationship to the source documents is required for both backward traceability and forward traceability.

 

Q26. Explain paradigms for interfacing module.

The paradigms for interfacing modules:
  • Procedure Call Interface: A procedure from one module calls to procedure of another module. The caller can pass data to the called procedure while calling and also the called procedure can pass data to the caller while returning control back to the caller procedure.
  • Shared Memory: When a block of memory is shared between two modules. The memory block may be allocated by one of the two modules or third module of the same application.
  • Message Passing Interface: One module generates a message and sends the message to another module. It helps in building up the communication between different process or modules.

 

Q27. What are the factors responsible for the estimation of system integration test cycle and total integration time?

The number of system integration test cycle and total integration time are determined by the following parameters:
  • Number of modules in the system.
  • Relative complexity of the modules.
  • Relative complexity of the interface between the modules.
  • Number of modules needed to be clustered together in each test cycle.
  • Whether the modules to be integrated have been adequately tested before.
  • Turnaround time for each test-debug-fix cycle.

 

Q28. What are the things the tests ensure?

Test must ensure that:
  • The number of parameters sent in a message agrees with the number of parameters expected to receive.
  • The parameter order in the message match the order expected.
  • The field sizes and data type match.
  • When a message is generated from stored data prior to being sent, the message truly reflects the stored data.
  • When a received message is stored, data copying is consistent with the received message.

 

Q29. What is random testing?

When test inputs are selected randomly from the input domain of the system, this is Random Testing. Random testing involve following procedure:
  • The input domain is selected.
  • Test inputs are selected independently from the domain.
  • The system under test is executed on these inputs. The inputs constitute a random test set.
  • The results are compared to the system specification. The test is a failure if any input leads to incorrect results, otherwise it is a success.

 

Q30. What are the benefits of Automated Testing?

The benefits of Automation Testing are below:
  • Test engineer productivity.
  • Coverage of regression testing.
  • Reusability of test cases.
  • Consistency in testing.
  • Test interval reduction
  • Reduced software maintenance cost
  • Increased test effectiveness

 

Q31. What is Agile Testing?

Agile Testing means to quickly validation of the client requirements and make the application of good quality user interface. When the build is released to the testing team, testing of the application is started to find the bugs. As a Tester, we need to focus on the customer or end user requirements. We put the efforts to deliver the quality product in spite of short time frame which will further help in reducing the cost of development and test feedbacks will be implemented in the code which will avoid the defects coming from the end user.
 

Q32. Describe Use Case Testing.

Use Case: A use case is a description of the process which is performed by the end user for a particular task. Use case contains a sequence of step which is performed by the end user to complete a specific task or a step by step process that describe how the application and end user interact with each other. Use case is written by the user point of view.
Use case Testing: the use case testing uses this use case to evaluate the application. So that, the tester can examines all the functionalities of the application. Use case testing cover whole application, tester performs this testing in step by step process to complete one task.

 

Q33. What type of tests you perform on the web based application?

For web application we perform following time of test:
1. Functionality Testing.
2. Usability Testing.
3. Navigation Testing.
4. Configuration and Compatibility testing.
5. Reliability and Availability Testing.
6. Performance Testing.
7. Load and Stress Testing.
8. Security Testing

 

Q34. What is Gantt Chart?

A Gantt Chart is used to represent a project schedule that includes duration of individual tasks or phases, their dependencies and ordering.
  • It displays the start and end points of each task and the percentage of completion of each task
  • It allows the planner to assess the duration of a project, identify the resources needed, and lay out the order in which tasks need to be performed.
  • It is useful in managing the dependencies between tasks.
  • Using Gantt chart each team member can view the product development schedule.

 

Q35 How to find all the Bugs during first round of Testing?

There could be several reasons for not debugging the entire bug in the first round of testing process. Debugging the showstopper in the first or second build is almost impossible. A found defect can cover up the other defects in the application. The thread which leads to on defect could be redirected to another defect, as the tester find the bug and lock that bug in report and after fixing of those bugs new bugs may also arises. It is difficult to keep testing on a known defective application. That is the reason we cannot find all the bug in first run and also we cannot perform Exhaustive testing.

 

Q36 How can u prepares the Test Plan without SRS?

We can prepare a test plan directly without having SRS, When the Requirements and URD(User Requirement Document )are available to us. URD is very helpful to determine the requirement of the user. The SRS document only contains the requirement of the user, but tester can also determine the requirement form the product. Without having SRS document we cannot estimate the Testing effort and cost of testing if we do not have SRS. SRS tell us on which platform our software is going to be used and on basis of this we perform the test on the application. Some time end user want to know what type of testing we are going to execute on the application for this we can send our test plan to the client.

 

Q37. What is the purpose of test strategy?

We need Test Strategy for the following reason:
1. To have a signed, sealed, and delivered document, where the document contains details about the testing methodology, test plan, and test cases.
2. Test strategy document tells us how the software product will be tested.
3. Test strategy document helps to review the test plan with the project team members.
4. It describes the roles, responsibilities and the resources required for the test and schedule. 
5. When we create a test strategy document, we have to put into writing any testing issues requiring resolution.
6. The test strategy is decided first, before lower level decisions are made on the test plan, test design, and other testing issues.

 

Q38. What are the dimensions of the Risks?

The dimensions of the risk are described below:
 
Schedule: Unrealistic schedules. to develop a huge software in a single day..

 

Client: Ambiguous requirements definition, requirement and not clear, changes in the requirement etc. 
Human Resources: Non-availability of sufficient resources with the skill level expected in the project.
System Resources: Non-availability of procuring all critical computer resources either hardware and software tools or licenses for software will have an adverse impact.
Quality: Compound factors like lack of resources along with a tight delivery schedule and frequent changes to requirements will have an impact on the quality of the product tested.

 

Q39. How to Estimate Testing effort ?

Time Estimation method for Testing Process:

Step 1 : count number of use cases (NUC) of system 
Step 2 : Set Avg. Time Test Cases(ATTC) as per test plan 
Step 3 : Estimate total number of test cases (NTC) 
Total number of test cases = Number of Use Cases X Avg. Test Cases per a use case 
Step 4 : Set Avg. Execution Time (AET) per a test case 
Step 5 : Calculate Total Execution Time (TET) 
TET = Total number of test cases * AET 
Step 6 : Calculate Test Case Creation Time (TCCT)
usually we will take 1.5 times of TET as TCCT
TCCT = 1.5 * TET
Step 7 : Time for Re-Test Case Execution (RTCE) this is for retesting
usually we take 0.5 times of TET
RTCE = 0.5 * TET
Step 8 : Set Report generation Time (RGT
usually we take 0.2 times of TET
RGT = 0.2 * TET
Step 9 : Set Test Environment Setup Time (TEST)
it also depends on test plan
Step 10 : Total Estimation time = TET + TCCT+ RTCE + RGT + TEST + some buffer.

 

Q40. How to create requirements test matrix template?

For a requirements test matrix template we perform following step:
Step 1: Find out number of requirements.
Step 2: Find out number of test cases.
Step 3: Create a table based on these. Let we have 10 requirements and 40 test cases, then we create a table of 11 rows and 41 columns.
Step 4: On the first column of table copy all your 10 requirement numbers, and paste them into rows 2 through 11 of the table.
Step 5: Now copy all 40 test case numbers, and paste them into columns 2 through 41 of the table.
Step 6: Examine each of your 40 test cases, determine which of the 10 requirements they satisfy.

 

Q41. Can you perform regression testing performed manually?

Yes we can perform regression testing manually, but it requires lots of effort. To choose the way of doing the regression testing is totally depends on the initial testing approach. If the initial testing approach was manual testing, then the regression testing is usually performed manually. In case, if the initial testing approach was automated testing, then the regression testing is usually performed by automated testing. Automated regression testing is very easy task.

 

Q42. You are a tester. Now How will you choose which defect to remove in 1000000 defects?

First thing testers are not responsible for fixing the bug they are only responsible for debugging the bug and prioritizing those bugs. These bugs are now reported in bug report template with the severity and priority of the bug. Tester assigns severity level to the defects depending upon their impact on other parts of application. Every bug has its severity and priority values assign by tester. If a defect does not allow you to go ahead and test the product, it is critical one so it has to be fixed as soon as possible. We have 5 levels as:
  • Critical
  • High
  • Medium
  • Low
  • Cosmetic

 

Q43.How do you perform integration testing?

Integration testing is black box testing. Integration testing focuses on the interfaces between units, to make sure the units work together. For integration testing we ensure that all units testing of the each component is performed earlier. Integration testing begins only after the unit testing. The purpose of integration testing is to ensure different components of the application interact with each other. So that, components work as per the customer requirements. Test cases are developed with the purpose of exercising the interfaces between the components. Integration testing is considered complete, when actual results and expected results are same.

 

Q44. What is the testing lifecycle?

There is no standard testing life cycle, but it is consist of following phases:
  • Test Planning (Test Strategy, Test Plan, Test Bed Creation)
  • Test Development (Test Procedures, Test Scenarios, Test Cases)
  • Test Execution
  • Result Analysis (compare Expected to Actual results)
  • Defect Tracking
  • Reporting

Q45.What is good code?

A good code is code that works. The good code must not contain the defect or bug and is readable by other developers and easily maintainable. Organizations have coding standards all developers should follow, and also every programmer and software engineer has different ideas about what is best and what are too many or too few rules. We need to keep in mind that excessive use of rules can decrease both productivity and creativity. Peer reviews and code analysis tools can be used to check for problems and enforce standards.

Q46. What are the main attributes of test automation?

The main attributes are discussed below:
Maintainability: For each new release need to update the test automation suites.


Reliability: Accuracy and repeatability of the test automation.
Flexibility: Ease of working with all the different kinds of automation test ware. 
Efficiency: Total cost related to the effort needed for the automation.
Portability: Ability of the automated test to run on different environments.
Robustness: Effectiveness of automation on an unstable or rapidly changing system.
Usability: Extent to which automation can be used by different types of user.

Q47. What could go wrong with test automation?

Followings things may be go wrong in test automation:
  • Ignoring automation, while planning the development phases.
  • In design Phase not choosing the right technology.
  • In coding Phase not automating the right test cases.
  • Tool selection might go wrong.
  • Test script not be updated when application is continuously changing.
  • Test data should be unique, if the same data is available on the application then the application will not accept the data that we are going to add via automation.

Q48. What tools are available to support testing during development of application?

Following tools can be used to support testing during development of application:
  • Test management tools example: Quality Center, JIRA.
  • Defect management tool example: Bugzilla, Test Director.
  • Project management: Sharepoint.
  • Automation tools: QTP, RFT, WinRunner.

Q49. What are the tests activities that you want to automate in a project?

The following testing activities can be automated:
  • Functional tests: Identify some P1 and P2 cases which are most critical for project success and operations and automate them. After every new build, these scripts will assure the fixes does not broke any of the critical functionality.
  • Regression test suites: Test the need to be run after each build.
  • Performance tests: Identical test the need to be run on different browser.
  • Stress tests
  • Load tests

Q50. What is the difference in responsibilities of Programmers and QA analyst?

The differences in responsibilities are listed below:
  • QA is concern for Process Quality and Programmers are concern for Product Quality.
  • QA ensure that the processes used for developing the product of high quality where as programmers used these processes so that end product is of good quality.
  • Processes are decided by QA. Programmers are supposed to follow the processes so that they can produce a good quality product.
  • Any issue found during execution of process by the programmers is communicated to the QA so that they can improve the process.

66 QA interview questions and answers – quality Assurance – Part I

Hello, my fellow readers! How are you guys tonight?
 
I am sorry to take that long to be back and right again, but I just moved to Canada. That’s right! I was in Brazil a few days ago and now I am in Canada searching for dream inside the game industry. Right now I’m looking for a job, but if I have time, I’ll write something about my research and stuff. I know that, back in Brazil, many people want to move to Canada to chase their dreams, study, work and more.
 
Alrightttt! Let move on and talk about, what. GAMES and QA. This is why you are here, right?
 
I found out this really interested info at careerride.com (didn’t know the website until now) and it talks about 66 QA interview questions and answers (Dã, right! its on the title! Come one!). So I hope you enjoy the reading as always just like I did and leave a comment with your opinion.
 
 
SOURCE: http://careerride.com/software-quality-assurance-QA-interview-questions.aspx
QA interview questions and answers – contributed by Rohit Srivastava
 
Q1. What is difference between QA, QC and Software Testing?
 
Quality Assurance (QA): QA refers to the planned and systematic way of monitoring the quality of process which is followed to produce a quality product. QA tracks the outcomes and adjusts the process to meet the expectation.
 
Quality Control (QC): Concern with the quality of the product. QC finds the defects and suggests improvements. The process set by QA is implemented by QC. The QC is the responsibility of the tester.
Software Testing: is the process of ensuring that product which is developed by the developer meets the user requirement. The motive to perform testing is to find the bugs and make sure that they get fixed.

 

 
Q2. When to start QA in a project?
 
A good time to start the QA is from the beginning of the project startup. This will lead to plan the process which will make sure that product coming out meets the customer quality expectation. QA also plays a major role in the communication between teams. It gives time to step up the testing environment. The testing phase starts after the test plans are written, reviewed and approved.

 

 
Q3. What are verification and validation and difference between these two?
 
Verification: process of evaluating steps which is followed up to development phase to determine whether they meet the specified requirements for that stage.
 
Validation: process of evaluating product during or at the end of the development process to determine whether product meets specified requirements.
Difference between Verification and Validation:
  • Verification is Static Testing where as Validations is Dynamic Testing.
  • Verification takes place before validation.
  • Verification evaluates plans, documents, requirements and specifications, where as Validation evaluates product.
  • Verification inputs are checklist, issues list, walkthroughs and inspection, where as in Validation testing of actual product.
  • Verification output is set of documents, plans, specifications and requirement documents where as in Validation actual product is output.

 

 
Q4. What is difference between Smoke testing and Sanity Testing?

The difference between smoke and sanity testing is described below:
  • Sanity testing is performed when new build is released after fixing bugs where as smoke testing is performed to check the major functionalities of the application.
  • Sanity is performed by the tester or the developer but smoke testing can be performed by the tester or developer.
  • Smoke testing is performed earlier where as sanity is performed after the smoke testing.
  • Sanity testing is narrow and deep approach of testing and smoke testing is focused testing based on major functionalities.

 

 
Q5. What is destructive testing, and what are its benefits?

Destructive testing includes methods where material is broken down to evaluate the mechanical properties, such as strength, toughness and hardness.
For example, finding the quality of a weld is good enough to withstand extreme pressure and also to verify the properties of a material.
 
Benefits of Destructive Testing (DT)
  • Verifies properties of a material
  • Determines quality of welds
  • Helps you to reduce failures, accidents and costs
  • Ensures compliance with regulations

 

 
Q6. What is Testware?

The testware is:
  • The subset of software which helps in performing the testing of application.
  • Testware are required to plan, design, and execute tests. It contains documents, scripts, inputs, expected results, set-up and additional software or utilities used in testing.
  • Testware is term given to combination of all utilities and application software that required for testing a software package.

Testware is special because it has:
 
1. Different purpose
2. Different metrics for quality and
3. Different users

 

 
Q7. What is difference between Retesting and Regression testing?

The difference between Retesting and Regression testing are below:
  • Retesting is done to verify defects fixes where as regression is perform to check if the defect fix have not impacted other functionality that was working fine before doing changes in the code.
  • Retesting is planned testing based on the defect fixes listed where as regression is not be always specific to any defect fix. Also regression can be executed for some modules or all modules.
  • Retesting concern with executing those test cases that are failed earlier whereas regression concern with executing test cases that was passed in earlier builds.
  • Retesting has higher priority over regression, but in some case retesting and regression testing are carried out in parallel.

 

 
Q8. Explain bug life cycle.

Bug Life Cycle:
  • When a tester finds a bug .The bug is assigned with NEW or OPEN status.
  • The bug is assigned to development project manager who will analyze the bug. He will check whether it is a valid defect. If it is not valid bug is rejected, now status is REJECTED.
  • If not, next the defect is checked whether it is in scope. When bug is not part of the current release .Such defects are POSTPONED.
  • Now, Tester checks whether similar defect was raised earlier. If yes defect is assigned a status DUPLICATE.
  • When bug is assigned to developer. During this stage bug is assigned a status IN-PROGRESS.
  • Once code is fixed. Defect is assigned with FIXED status.
  • Next the tester will re-test the code. In case the test case passes the defect is CLOSED.
  • If the test case fails again the bug is RE-OPENED and assigned to the developer. That’s all to Bug Life Cycle.
 
 
CHARTER Provided by the Author of the blog (I tried!)
 
 

 

Q9. What is severity and priority of bug? Give some example.

Priority: concern with application from the business point of view.
It answers: How quickly we need to fix the bug? Or How soon the bug should get fixed?
Severity: concern with functionality of application. It deals with the impact of the bug on the application.

 

How much the bug is affecting the functionality of the application?
Ex.
  • High Priority and Low Severity:
    Company logo is not properly displayed on their website.
  • High Priority and High Severity:
    Suppose you are doing online shopping and filled payment information, but after submitting the form, you get a message like “Order has been cancelled.”
  • Low Priority and High Severity:
    If we have a typical scenario in which the application get crashed, but that scenario exists rarely.
  • Low Priority and Low Severity:
    There is a mistake like “You have registered success” instead of successfully, success is written.

 

 
Q10. What are the common problems with software automation?

Software problem are listed below:

1. Purchasing the license of tool (QTP, selenium, QC, LR) 
2. Lack of skilled Tester to run the tool
3. Expectation that automated tests will find a lot of new defects
4. Maintenance of automated tests
5. Technical problems of tools

 

 
Q11. What is the role of QA in a project development?

QA stands for QUALITY ASSURANCE. QA team assures the quality by monitor the whole development process. QA tracks the outcomes and adjusting process to meet the expectation.
 
The role of Quality Assurance is discussed below:
  • QA team is responsible for monitoring the process to be carried out for development.
  • Responsibilities of QA team are planning testing execution process.
  • QA Lead creates the time tables and agrees on a Quality Assurance plan for the product.
  • QA team communicated QA process to the team members.
  • QA team ensures traceability of test cases to requirements.

 

 
Q13. What is the difference between build and release?

BUILD: is a number given to installable software that is given to testing team for testing by the development team. Build number assigned are incremental and sequential.

 

RELEASE: is a number given to installable software that is handed over to customer by the developer or tester.

 

The information of build, release and version are displayed in software help page. Using this build and release customer can let the customer team know which release version build thet are using.

 

eg “9.4.123.2” (Release Number.Version Number.Build Number.Patch Number)

 

 
Q14. What are the key challenges of software testing?

Following are some challenges of software testing.
 
1. Application should be stable enough to be tested. 

 

2. Testing always under time constraint. 

 

3. Understanding requirements, Domain knowledge and business user perspective understanding.

 

4. Which tests to execute first? 

 

5. Testing the Complete application. 

 

6. Regression testing. 

 

7. Lack of skilled testers.

 

8. Changing requirements.

 

9. Lack of resources, tools and training.
  
Q15. Why you choose automated testing over manual testing?

The reasons for choosing automation testing over manual testing are following:
 
1. Frequency of use of test case

 

2. Time Comparison (automated script run much faster than manual execution.)

 

3. Reusability of Automation Script

 

4. Adaptability of test case for automation.

 

5. Exploitation of automation tool.

 

 
Q16. What is the basis for choosing the SDLC model for development of software?

The choice of SDLC depends on the various factors, how stable are the requirements:
  • When the requirements are very clearly know, documented and not subject to change then we can follow the waterfall model.
  • Most of the companies follow the V mode for the development because this model includes both verification and validation activities and testing is involved in earlier phase.
  • Iterative model can be used to build application where requirement changes after a period of times or application features or added on with smaller release. When the client is ready for the delivery of the product in parts or phases.

 

 
Q17. Explain bug leakage and bug release.

Bug Leakage: When customer or end user discovered a bug which can be detected by the testing team. Or when a bug is detected which can be detected in pervious build then this is called as Bug Leakage.
Bug release: is when a build is handed to testing team with knowing that defect is present in the release. The priority and severity of bug is low. It is done when customer want the application on the time. Customer can tolerate the bug in the released then the delay in getting the application and the cost involved in removing that bug. These bugs are mentioned in the Release Notes handed to client for the future improvement chances.

 

 
Q18. What is regression testing?

Regression Testing: When changes in the code of the software are made to fix the previous bug. Then testing needs to be perform to ensure that it will not generate a new bug in the application and it works as specified and that it has not negatively impacted any functionality that it offered previously. Regression Testing is important because of following reason:
  • That the application works even after the alteration in the code were made.
  • The original functionality continues to work as specified even after doing changes in the software application.
  • The alteration to the software application has not introduced any new bugs.

 

 
Q19.What is data driven testing?

Data Driven is an automation testing part in which test input or output values, these values are read from data files. It is performed when the values are changing by the time. The different data files may include data pools, csv files, Excel files. The data is then loaded into variables in recorded or manually coded scripts. For data driven testing we use Parameterzing and Regular expression Technique.
Ex: To evaluate login functionality, we use different user name and password combinations, variables are used to access different username and password. The list of username and password are stored in a data table or excel sheet.

 

 
Q20. What is alpha and beta testing?

Alpha testing: is performed by the IN-House developers. After alpha testing the software is handed over to software QA team, for additional testing in an environment that is similar to the client environment.
Beta testing: It is performed by end user. So that they can make sure that the product is bug free or working as per the requirement. IN-house developers and software QA team perform alpha testing. The public, a few select prospective customers or the general public performs beta testing.
 
 
Yeah! I know I promised you 66 QA questions – and I will posted – is just because I need to read them first, understand and them post it. Somethings I can add something (like the charter on this one) and can help newcomers.
 
Thank you for reading so far and hope you can come back for part II.
 
Drive Safe!