Getting Started necessary, in the history of the most complete source software testing basics age share!

Software testing in software development occupies more than half of the workload, great job demand, talent gap is too great, in the field of IT training, software testing entry is not difficult, as long as you are willing to work hard to learn, no matter what your professional can enter the software testing industry.
This article is for software testing novice, offers several little knowledge of software testing, software testing knowledge of these newcomers have to keep in mind:
01. software testing (software testing for the presence of meaning)
and execution of the program 1. discover errors in the program
2 - test the software meets the needs of users
3. improve the user experience
principles 02. software testing (common sense)
1, early intervention (intervention during requirements analysis)
2, dates back to the user's needs (not behind closed doors)
3, the programmer should avoid checking their own program, in addition to the test unit. Test positive + negative 28 principles test, 80% of 20% concentrated in the error module (aggregation effects)
4, an incorrect result of a confirmation process (test a few more times, recording the testing process, sporadic type BUG )
5, the development of rigorous testing program (start time, responsible for the module .....)
6, can not be fully tested, the test needs to be terminated (there will be some reasonable BUG, does not affect the user experience and use, these might BUG the next version will be changed)
03. software testing classification
First, according to the testing phase points:
unit testing, integration testing (developers and testers can do, interface testing division in integration testing inside), system testing (complete overall a test and not Android, Apple systems), acceptance test (formal acceptance testing, Alpha, Beta, the game closed beta, pre-release version, beta)
Note: Alpha test: preliminary user tests under simulated actual operating environment for acceptance testing (beta) belongs to the development environment, development and testing can not participate in Beta testing: Late user testing (beta), the development and testing of real-world environment We can not participate in the same point: can not participate in the development and testing different points: pre, post, development environment and the real environment
Second, according to test technology division:
white-box testing (code level), black box (external operations and surface reactions to discover), gray box testing
Third, divided by the contents of the test included:
function test (little point), test interface (UI interface), security testing, compatibility testing, usability testing (if easy to use), performance testing, stress testing, load testing, recovery testing (disaster recovery, self-healing)
 four other tests:
smoke test (main test prior to release, before the real test), regression testing (validation testing BUG good repair and related functions are normal), exploratory testing (test thinking) random testing
04. software testing life Period (six stages)
First, the main problem definition and planning phase to determine the feasibility of software development purposes and to develop plans to develop
Note: boss, product managers, R & D, project managers, requirements analysts do
Second, the needs analysis / assessment phase analysis sources (prototype map / software requirements specification), participants (presided over - product manager, other participants, research and development, design, testing), focus on one issue - what is the purpose of this test involved a needs analysis? (Know thyself, easy question)
Third, the software design phase (attributes: job belongs to the developer's) (stuff framework of database tables, etc.) preliminary design detailed design (pseudo-code level)
Fourth, the coding phase of software developer tasks, programmers coding
Fifth, the task of software test engineers testing phase of development or development tasks to do: unit testing, development or testing: integration testing --- tester interface testing: system testing, customer or product manager: acceptance testing --- Alpha test, Beta test
Sixth, the stage version of the software operation and maintenance, repair product line (version upgrades) BUG of
05. software testing workflow
a contact to which post personnel
development, product managers, customer service, implementation / technical support / on-site implementation, designer
Second, the test workflow:
1, testing requirements analysis phase:
reading demand / understanding of the requirements, needs finishing point, there are questions about where to catch, to discuss, to find out so far.
2, test planning stage:
a document: Test Leader / team leader plan
contents included:
① OBJECTIVE: We want to complete the test, probably when it was performed, what kind of goals to achieve. ② staff: What are people involved, become the test team.
③ division of tasks: who is responsible for which function module test / write use cases.
④ time to plan: When did you start writing use cases, when to begin the test, the test is when, what time on-line.
⑤ issued a document: cases, bug list, with a test report.
⑥ resources application / preparation: apply for a server? I do what kind of test? What You Need?
3, the test design phase:
write test cases:
① Review: OK mutually review the use case is complete and whether the correct
② Review: misunderstanding: Correct, demand changes: Modify the
test execution phase
will be smoke testing prior to testing (through continued, by not playing back),
based on test cases to perform the test:
① found bug-- submit bug management system to go
after ② develop fixes, go to verify, and then regression testing
4, testing and evaluation phase:
the test is completed, issue a test report,
Through the on-line test, the test is not passed to fight back, modify and re-test.
(This article was written by teacher-source era, writing this article is designed to help software testing software testing novice better grasp the knowledge points.)