The day to do QA--ios Test Primer (iv)

Frankly, do QA this half of the year I did not grow, even if there is little growth, I am very sad, and people around the fact that there is no one who can really understand their sad, in fact, they are not hard enough to themselves, once felt lucky enough to have a better point of passers-by, in fact, such an idea is wrong, which has so many refers to passers-by, met is you lucky, did not meet yourself to do your own finger passers-by, with their driving force to drive their growth, even if slower and how, when there is such a means of passers-by to help you, perhaps you will cherish now have.

Do QA testing, often stand in the rear to support the entire team, it is likely that many times will be looked down on by others, others will say, TA is not a test, actually do not need to control what others say, you are you, do what you should do, this is the most important, do what you think is the right thing, Those gossip is actually a breath, it is not instantaneous, even if the dead will not take things. When you are done, no matter in what position will be recognized by others, at least you will be worthy of their own time, the time to take the meaningless comparison that is wasting their lives, is not to give themselves the opportunity to grow, while young why not learn a little more, do a little more, tired point? In the work, feel not to despise others, everyone has a life state, as long as the TA want, it is worth to respect. Don't be too concerned about the eyes of others, do test but do not limit yourself to functional testing, have the opportunity to understand the code, so that your technology will be able to grow, so that you more comprehensive.

Want to summarize the iOS test primer and hopefully give some help to those who want to get started with mobile iOS testing:

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 comparison evernote--used to remember something.
5) Install cornerstone or Smartsvn--checkout code and see the change point

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

3. If the project you are testing requires access to the code, you should know the address of the Code SVN

4. You want to test of course to record the address of Bug,bug, of course, there is the address of the installation package download

5. How to get started, you 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 intention is to write detailed steps to reproduce, so even if you do not research and development next to the research can also reproduce the bug, if you can tell the development of the problem where the bug, then congratulate you on a level

6. What matters at work can improve your productivity

1) It is recommended that each release of the offline pack of their own Apple account download, so that the next installation or test overlay installation will not have to repeat the download, will save a lot of time.

2) Also recommend that you save each test delivery package, so that if a version has a problem can quickly find the installation package, do not have to find, so virtually save 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 go to the address every time you enter the addresses. Of course, not necessarily the label can be put so much, then you can like the computer cache is not so common, but the usual address in a txt or remember the Evernote, convenient for each time you find.

4) must pay attention to communication, do not be afraid, I eat for a long time loss, even if others feel that they do not, and how to solve the problem is the key, if their own more than half an hour has not solved the problem, strongly recommend to the people around to help, to clarify their own before the solution and the current problems encountered.

5) Work should be good at summing up, can be summarized in the form of documents, write to not only their own to understand that others must understand, do not understand the things must strive to understand.

First write this, next time I want to summarize the troubleshooting method of common problems, refueling, together refueling, people because of the dream and great, after some things, just know what they want.

The day to do QA--ios Test Primer (iv)