The day of QA--ios test Introduction (iv)

Frankly, do the QA of this half year I did not grow, even if there is very little growth, I am very sad. And the people around to tell the fact that no one can really understand their own sad, in fact, they are not hard enough. To oneself is not ruthless, previously thought oneself is not fortunate, wants to have a better refers to passers-by, in fact this idea is not correct, which has so many refers passers-by, met is you lucky. Do your own finger-walkers without meeting yourself. Drive yourself to grow with your own driving force. Even if you are slow, you may cherish what you have now, when you have this kind of finger-pointing help.

QA testing, very often standing behind the back of the entire team, it is very likely to be looked down upon by others very often. Others will say, TA is not a test, in fact, do not need to control what others say, you are you. Do what you should do, this is the most important thing, do what you think is right, those gossip is actually a breath, that is not instantaneous, even if the dead can not take things.

When you are done, no matter what position you will be recognized by others, at least you will be worthy of their own time. Take the time to the meaningless comparison that is wasting their lives. Is that they do not give themselves the opportunity to grow, while young why not learn a little more. Do a little more, what about being tired? At work. Think not to discriminate against others, each person has each person's life state, only if TA wants, that is worth to respect. Do not be too concerned about the eyes of others, do test but do not limit themselves in the functional test, have the opportunity to understand the code, so that your technology will be able to grow, so that they are more comprehensive.

Want to summarize the iOS test primer. Hopefully, some help for those who want to get started with a mobile iOS test:

1. Recommended Software for installation
1) xcode--to see the code
2) Install charles--to grab the bag
3) Install mindmanager--Mind Mapping to write some test ideas
4) Installation impression is more evernote--used to remember things memo
5) Install cornerstone or Smartsvn--checkout code and see the change point

6) Installing ifunbox--to install the app, see the relevant files inside the app

2. Access to some means of communication. such as the relevant department of QQ Group, discussion group, a regular use of the e-mail address

3. Assume that the project you are measuring requires contact with the code. Then you need to know the address of the code SVN.

4. You have to test the bug, of course. The address of the bug and, of course, the address where the installation package was downloaded

5. How to get started, can do some god horse?

1) 1 times or n times full use case to understand the function of the product to be measured

2) See how others on the TRAC record TRAC, to learn how to mention trac the product exists God horse-like problem? Remember that all of TRAC's original intent is to write specific steps to reproduce. This way, you can reproduce the bug even if you are not developing next to it. Assuming you can tell the problem of developing this bug out there, congratulations, you're on a level.

6. What matters at work can improve your productivity

1) It is recommended that each release of the online packet of their own Apple account download, so that the next installation or test coverage installation will not be repeated download, will save a lot of time.

2) It is also recommended that you save each test delivery package. This assumes that a version number has a problem and can find the installation package very quickly, do not need to find one. This virtually saves a lot of time.

3) Add important frequently visited URLs (such as mailboxes, TRAC addresses, technical sites, etc.) to the browser's tabs so that you don't have to look for them every time you enter an address.

Of course not all tags can be put so much, then you can be like the computer cache is not so often used. But often use the address in a txt or remember the Evernote, convenient for each time you find.

4) Be sure to pay attention to communication. Do not be afraid, I just because of this eat for a long time, even if others think they can not, how to solve this problem is the key, assuming that they have not solved the problem for more than half an hour, strongly recommend to the people around to help, to clarify their own before the solution and the problems encountered at the moment.

5) Be good at summing up the work. Can be summarized in the form of a document, write to not only their own to clear the others should also be clear, want to not clear things must strive to clear.

First write this, next time I want to summarize the troubleshooting methods of common problems. Come on, cheer up together. Man is great because of his dreams, and after some things, he knows what he wants more.

The day of QA--ios test Introduction (iv)