1. Principles of Software Testing
Should be "as soon as possible and continue to test" as the developer's motto
Programmers should avoid checking their own procedures, testing should be done by an independent professional software testing organizations
When designing test cases should be considered legal and illegal input and input various boundary conditions, special circumstances to manufacture and unexpected state of extreme states, such as network anomaly interrupt, power outage, etc.
Must pay attention to testing errors concentrated phenomenon, this level of programming and programmers and habits have a great relationship. There is the phenomenon of cluster test, errors like the discovery procedure in the same module and the associated developers to write
The results of the test error must have a confirmation process, usually tests out there A mistake must have a B to confirm that serious errors can be held to discuss the assessment and analysis
Develop rigorous testing program and the testing schedule is as relaxed as possible, do not wish to complete a high-level test in a very short period of time
Relevance of regression testing must be given sufficient attention, to modify an error caused more errors phenomenon is not uncommon
Proper preservation of all test documents, the meaning is self-evident, test often depends on the reproducibility of the test document
2. experience in software testing
Test Good Enough
Good-enough principle: Do not do adequate testing, do not do too much testing; testing to find a balance between the cost and the amount of testing is the best choice
Develop test content and test the minimum be measured (to analyze specific issues if necessary) by the standard.
Law bucket theory test and principles 80-20
Testers do not ever guarantee anything
Testers prepared the document on behalf of their own
Testers must learn to reverse thinking
The preparation of defect must ensure reproducibility
Testing must be based on demand
"Specification requirements specification"
Focus on the user adverse defects
From the user's point of view
The introduction of appropriate testing tools to improve testing efficiency
Testers are service personnel
3. Effective develop software test plan?
3.1. The concept
A description of the range of the predetermined test activities, documentation approach, resources and schedule arrangements. It confirmed the test items, test features, test mission, staffing, and any risk of accidental events
3.2 Develop benefits
Project managers, senior managers and other relevant leaders can do macro-control test plan, the corresponding resource allocation;
Testers can understand the work of the various stages of the project test cases and test project to be carried out;
To facilitate the development, marketing personnel, quality personnel understand the work content of the test personnel carry out the work together;
3.3. Who is responsible for
Project test leader with extensive experience in the development of test plans, responsible for the entire testing process
3.4 write time.
The sooner the better software test plan written in order to have an overall test plan for the entire project
3.5. Element
Why why-- to conduct these tests, what is the purpose of the test;
what- what test to determine the content of the test;
when- test start and end times at different stages of the test to determine the time of each activity;
where- appropriate documentation, storage location of the defect, the test environment;
who- who is responsible for corresponding work;
How- how to do it, which test tools and test methods used to test strategies for testing
3.6 Templates
Testing purposes
Test Project
Test Reference Document
Test Submit Documentation
Terms and Definitions
Test strategy
Determine the test content
Resources
Test progress
Assignments testers
Risks and issues
3.7. Maintenance and Review
With the changes to the project plan, software requirements, software development and other personnel, software testing plan is constantly updated and maintained
4. Software Test basic concept?
4.1. The concept
Test (Test Case) is a collection of test embodiments provided to the system being tested, the group set which comprises: a test environment elements, steps, test data, expected results and the like.
It can generally be divided into simple test: test scene (referred to as "test") and test case base (or referred to as "common test")
4.2 Advantages and disadvantages
benefit
Effectiveness
Integrity
Organized
Shortcoming
Test case design is a time-consuming job, often it takes time to design test cases more than the time it takes to execute
4.3 Templates
Word
Excel
use tools
According to the specific circumstances of the company to develop a template
4.4. Quality of
Test methods
Consider the issue of comprehensiveness
Profound knowledge of business
Reverse thinking
A wealth of experience in testing
4.5. Updates and Maintenance
the reason
Demand changes, feature changes, test cases need to be updated
Test cases need to refine and continuously improve, it is a gradual process
Proven by testing test cases and add, modify, delete a test case
Test cases to go through a formal and effective review
Use test tools to manage test cases
Disclaimer: This article is part of the contents or possible sources of finishing from the network, if infringement, please contact deleted