Based on our team Academic Search WP7 mobile client conference assistant alpha version has ended. In the team, the team limited scale, everyone will do something dev thing, but my main role is the most tester, tester never done before, a month down the development of alpha version, I also have a lot on the job tester feelings, I think they've got it, want it to witness our growth, of course, hoping to get everyone's advice, we can get lessons and knowledge from cognitive crowd.
Theoretically What have we learned?
I think people for the most basic test of understanding, than try to use the software to find bug. In fact, the real test of time to have done very standard process. I briefly pick a few concepts to share with you.
1) Test Plan: Test Plan describes the main aspects of the testing activity, why? what? who? when? . Said to contain details about aspects:
Strategies and methods of test, the test schedule, quality objectives, resources, test variable matrix.
2) What is the test variable matrix:
Simply put, the test matrix is variable by considering various factors user type, the system OS, language, browser type, network conditions, etc., to determine a number listed in the table after the test variables, test variables matrix testers for testing blueprint.
3) method of software testing:
First, to clarify the methods described herein, we often say that the black-box testing and white box testing is not really referring to some kind of software testing, they are two types of software test design method. Software testing methods we OMG team in the alpha version is mainly focused on functional testing and non-functional testing.
Software testing, functional testing by classification, unit test (the test to verify the correctness of each unit procedure), the test module function (function test of each module), integration testing (module functions of several interdependent test) , scenario testing (verification can complete a specific user scenarios), system test and alpha test (alpha release of software testing in the actual user environment). Rather than functional testing, including load testing, performance testing, localization / globalization testing, compatibility testing, configuration testing, usability testing and software security testing.
Of course, there are many methods of software testing, including code coverage test (PS: For the novice me, I really do not know how to design code coverage testing methods ... seek expert advice), acceptance testing, regression testing, "exploratory" test and so on.
What thoughts work as a tester?
First of all, I want to say, the main character is a tester, despite the relatively small dev work I do, but I do not think less of their own contribution than others.
Many people will kind of obsession, developing software, not dev seems to be no power. In fact, through the practice of a month, I think, this is the height of the social division of labor. tester played in a software development role can not be ignored. Quite simply, if not all kinds of testing, software performance evaluation of how to go? How to ensure that the final release of the product can well meet the needs of users?
Secondly, test and did not work quite that easy.
At first, he took over the role of tester, and thought their work pressure should be relatively small. It turns out that the real intention to make a tester, or takes a lot of effort. In the planning stage of the product, tester test plan to be discussed, the effectiveness of research and collection of user non-functional requirements of the software, such as software, information, ease of use, determining our non-functional testing standards; the development phase, tester the need for BVT (Build verification test) timely, timely submission of the bug to the dev, in addition, as a tester, need to think of many examples of "exploratory testing", random verification software stability and robustness; and when entered a stable stage later, especially after the alpha release, tester needs to collect user feedback alpha trial to determine the beta version of the test criteria.
Finally, and most importantly, tester should be how kind of quality.
Do the tester, just know, tester is not so good to do, of course, their level is so so limited, knowledge and grasp of the contact is relatively small. Combine my work experience, I found the following points:
1. careful enough patience and confidence.
First you have to believe they have enough creativity and curiosity, to believe they can pick out the bug in the software. Then you have the power to try every possible case, if there is no curiosity, perhaps a bug on playing the soy sauce inadvertently slipped away. And patience and careful is to do any work of the foundation. tester job, even more so, imagine a certain function or a certain user scenarios, you need as many imagine all kinds of test case to find fault with it, in fact, sometimes not so interesting.
2. A well-informed, better foundation.
I, as a non-CS professional tester, this is a little more experience of Kerry. In the design of tester black-box testing methods further rely more creative curiosity like. However, do white-box testing, the structure of the code is actually transparent to you, can professional analysis code structure, can not be keen aware of the possible risks or code flaws, this is a time to test the skills of a professional tester. In addition, well-informed is very important, tester if the IT understand all directions, more and more of the background, for him, design better and more creative test case is quite favorable.
3. Learning and inquiring mind.
Take people long to make up our own weaknesses, stone hills, can learn. Our ancestors say rotten. However, my experience once again examined it. From the beginning I did not even know how to write test plan, and today writing this journal, I think this is the accumulation of the learning process down, even though I just touch it, these words seemed at my tender and there are simple and obvious, but let me learn to grow, I believe, or are learning to make every success, or growth. And the king of mutual encouragement.
Dongliang He humble pen
MSRA—USTC Class.
Reproduced in: https: //www.cnblogs.com/OMG-Team/archive/2011/11/06/2237875.html