How to become a tester software: from the interview to find the first bug

My journey began with a curiosity tester. Since childhood, I was engaged in assembling computers and installing the software, in the course of a regular question arises: "Why is not installed? Why does not it work?". At that moment I thought that I wanted to become a tester, to engage in the production of quality software and find answers to all these questions.

Below I want to tell the future QA-experts about what they can expect in the beginning of his career, and give a few tips from my own experience.

interview

Junior-tester is not very difficult to pass an interview. From it do not expect a deep knowledge of the theory and tools for testing. When the interview such candidates, we pay attention to the speed and vivacity of thinking, fresh and creative approach to problem solving.

For example, unusual Asking questions to see how the man thinks:

• The aircraft flies from point A at 17:00, and arrives at the point B at 19:00. When this is in flight for three hours. Why could this be?
• How to make sure that by getting an updated application, competitors are not able to find him a new function?

Be prepared, and to the most common tasks - to test a simple object: a piece of paper, a pencil, a line filter and the like.

Also, for an interview will be helpful:

1. Examine the types of testing: functional and exploratory testing, automated testing (including tools for it), load and stress testing, smoke-testing.
2. In addition, read about the acceptance testing and criteria.
3. If we are talking about testing web applications, it is a browser console and its work, and the number of versions of browsers, monitor resolution, testing layout tools (pixel perfect).
4. If we talk about mobile apps, this kinds of platforms, emulators, monkey testing. Do not forget about the plates.
5. Examine the types of bug-trackers. Most popular: Jira, BugZilla, RedMine, Mantis. See how they work, what their features.
6. In the long term - Jmeter tools, Postman, Charles. They are not very difficult to learn at a basic level.

First work day

The first working day goes as standard: give the computer that you want to configure, install work programs. The system administrator prepares access to email and corporate internal programs.

It is not necessary to ask where to install a Skype, use it a nickname from school times gangsta_666 or funny picture. Use in combination nick name, eg or ivansmirnov smirnovivan, put his usual photo.

An important step in preparing for the working day - meeting with bug trekrom, which uses the company. This is to ask in advance: study articles look at the training video. You will save time colleagues and yourself will feel more confident.

The first task

You will be the first project for dipping. I advise you to get acquainted with the history of the bug tracker to see which defects have already met or are the most common. You are able to articulate themselves and Statistics will understand at what points you should pay more attention.

Take the initiative. If you have not given a check list app, do not wait and ask him to have a mentor. If the organization does not have a check-list, you can make it yourself. Our company often make a check-list in the "Google Spreadsheets». Below, we have an example of such a check-list - you'll be on your suit.

Colleagues may be surprised if formulations checklist as mind maps, for example, in Xmind.net.

Checklist for testing Pokémon GO

One of the primary forms of testing for a beginner QA-specialists may become the passage of checklists, test cases, older professionals. This step is necessary for a quick dip in the project. To build up the test database novice can he expand this checklist. Junior-testers as part of learning writing checklists prepared sheet Pokémon GO for application testing. Here are described only positive cases.

The first bug tracker

Description of bugs in different companies can vary, but in general there are the principles of good taste.

Subject

It describes the problem in a few words. Better if it will start with a negation: "not working", "it does not happen", "wrong" and so on. For example: "There is a synchronization server on the iPhone 6," "does not work in video playback Nexus 5."

Scenario

Step by step description of the bug play. Pay attention to the precondition and the signs that precede the bug (for example, lighted red button on the left).

Additionally, you can make screenshots showing the locations to which you should pay attention (you can use the application Joxi, LightShot and others), for more slozhnovosproizvodimyh bugs - to record a video. When you type the experience can capture and apply logs.

At the end of the script indicates the environment in which testing: product version, the device firmware (Android 6.0.1, iOS 9.3.2). If a web application, in addition, specify the version of the browser.

appointment bug

Next you need to assign someone a bug. Ask the project manager or a mentor, someone to hang on this bug, someone from the developers for what area of ​​the project is responsible. So you will meet with the team in the future to assign bugs.

Putting criticality

Types of critical bugs in most trackers are represented by the following list:

Immediate (Blocker)

A blocking error. An application inoperable, resulting in further interaction with the system under test or its key functions is impossible.

Crit - Urgent

A critical error, a violation of key business logic. The problem leads to a temporary drop in the server or application without the possibility of its solution. Remedy needed for testing.

High

Significant error, a violation of the basic business logic. Error is not critical, it is possible to work with the test function using other entry points.

Normal

Minor error. Does not violate the business logic of the application under test, the obvious problem of the user interface and localization.

Low

Trivial issue that concerns the application business logic. The problem of third-party libraries or services played badly, hardly noticeable due to the user interface.

Self-learning

About the importance of learning all know very well - my instructions are commonplace. So get to the point.

Below - a few books that I personally recommend to my trainees:

• "Testing DOT COM», Roman Savin - a very useful handbook, practically reading the book begins tester. It contains the lion's share of knowledge in order to start the test and successfully respond to the interview questions related to technical and theoretical part.
• "How are tested Google» - a deep book, which describes the organization of the process, a variety of strategies and approaches to testing. The book helps to understand what quality is and at what stages it can be influenced.
• «A Practitioner's Guide to Software Test Design», Lee Copeland - painted in the book kind of testing as "white" and "black" box. Lists the various testing equipment, as well as how to use them and when to apply. In the book you can find an interesting article about the research testing, which is very useful for novice testers.

Colleagues write in comments the name of interesting books for testers. I am sure all will be helpful.

conclusion

In conclusion I would like to add that the issue of a quality product - not an easy process and not a quick. You must be able to defend their views in the negotiations, to convince developers to do it right, rather than "crutches" to understand how to make the functionality more user friendly.

This is only part of the necessary information for the novice tester. Everything else will have in combat conditions to search the Internet, and then ask colleagues. Do not be shy to ask questions and hours of googling, often the answer to one question will save you a lot of time in the future.