【ISTQB】ISTQB-FL-考纲-2007(蓝色)Vs.2011(黑色)

xjmen

http://www.51testing.com/?uid-33538-action-viewspace-itemid-822695

The syllabus of ISTQB Foundation Level

2007(Blue) Vs. 2011(Black)



• K1: remember, recognize, recall;

• K1: remember



• K2: understand, explain, give reasons, compare, classify, categorize, give examples, summarize;

• K2: understand



• K3: apply, use.

• K3: apply



• K4No Exist)

• K4: analyze



1.  Fundamentals of Testing (K2)



1.1 Why is testing necessary? (K2)



LO-1.1.5 Recall the terms error, defect, fault, failure and corresponding terms mistake and bug. (K1)



LO-1.1.5 Explain and compare the terms error, defect, fault, failure, and the corresponding terms mistake and bug, using examples (K2)



1.2 What is testing? (K2)



LO-1.2.2 Describe the purpose of testing in software development, maintenance and operations as a means to find defects, provide confidence and information, and prevent defects. (K2)



LO-1.2.2 Provide examples for the objectives of testing in different phases of the software life cycle (K2)



LO-1.2.3 (No Exist)



LO-1.2.3 Differentiate testing from debugging (K2)



2. Testing Throughout the Software Life Cycle (K2)



2.1 Software development models (K2)



LO-2.1.1 Understand the relationship between development, test activities and work products in the development life cycle, and give examples based on project and product characteristics and context (K2).



LO-2.1.1 Explain the relationship between development, test activities and work products in the development life cycle, by giving examples using project and product type (K2).



3. Static techniques (K2)



3.1 Static techniques and the test process (K2)



LO-3.1.3 Explain the difference between static and dynamic techniques. (K2)

LO-3.1.4 Describe the objectives of static analysis and reviews and compare them to dynamic testing. (K2)



LO-3.1.3 Explain the difference between static and dynamic techniques, considering objectives, types of defects to bee identified, and the role of these techniques within the software life cycle (K2)



3.3 Static analysis by tools (K2)



LO-3.3.2 List typical benefits of static analysis. (K1)



LO-3.3.2 Describe, using examples, the typical benefits of static analysis (K2)



4. Test design techniques (K4) * (K3--> K4)



4.1 The test development process (K3) * (K2--> K3)



LO-4.1.3 Evaluate the quality of test cases. Do they:

• show clear traceability to the requirements;

• contain an expected result. (K2)



LO-4.1.3 Evaluate the quality of test cases in terms of clear traceability to the requirements and expected results (K2)



4.3 Specification-based or black-box techniques (K3)



LO-4.3.1 Write test cases from given software models using the following test design techniques: (K3)

• Equivalence partitioning;

• Boundary value analysis;

• Decision table testing;

• State transition testing.



LO-4.3.1Write test cases from given software models using equivalence partitioning, boundary value analysis, decision tables and state transition diagrams/tables (K3)



LO-4.3.2 Understand the main purpose of each of the four techniques, what level and type of testing could use the technique, and how coverage may be measured. (K2)



LO-4.3.2 Explain the main purpose of each of the four testing techniques, what level and type of testing could use thee technique, and how coverage may be measured (K2)



LO-4.3.3 Understand the concept of use case testing and its benefits. (K2)



LO-4.3.3 Explain the concept of use case testing and its benefits (K2)



4.4 Structure-based or white-box techniques (K4) * (K3--> K4)



LO-4.4.2 Explain the concepts of statement and decision coverage, and understand that these concepts can also be used at other test levels than component testing (e.g. on business procedures at system level). (K2)



O-4.4.2 Explain the concepts of statement and decision coverage, and give reasons why these concepts can also bee used at test levels other than component testing (e.g., on               business procedures at system level) (K2)



LO-4.4.3 Write test cases from given control flows using the following test design techniques:

• Statement testing;

• Decision testing. (K3)



LO-4.4.3 Write test cases from given control flows using statement and decision test design techniques (K3)



LO-4.4.4 Assess statement and decision coverage for completeness. (K3)



LO-4.4.4 Assess statement and decision coverage for completeness with respect to defined exit criteria. (K4)



4.6 Choosing test techniques (K2)



LO-4.6.1 List the factors that influence the selection of the appropriate test design technique for a particular kind of problem, such as the type of system, risk, customer requirements, models for use case modeling, requirements models or tester knowledge. (K2)



LO-4.6.1 Classify test design techniques according to their fitness to a given context, for thee test basis, respective models and software characteristics (K2)



5. Test management (K3)



5.1 Test organization (K2)



LO-5.1.2 List the benefits and drawbacks of independent testing within an organization. (K2)



LO-5.1.2 Explain the benefits and drawbacks of independent testing within an organization (K2)



5.2 Test planning and estimation (K3) * (K2--> K3)



5.3 Test progress monitoring and control (K2)



LO-5.3.2 Understand and interpret test metrics for test reporting and test control (e.g. defects found and fixed, and tests passed and failed). (K2)



LO-5.3.2 Explain and compare test metrics for test reporting and test control (e.g., defects found and fixed, and tests passed and failed) related to purpose and use (K2)



6. Tool support for testing (K2)



6.1 Types of test tool (K2)



LO-6.1.1 Classify different types of test tools according to the test process activities. (K2)



LO-6.1.1 Classify different types of test tools according to their purpose and to the activities of the fundamental test process and the software life cycle (K2)



LO-6.1.2 Recognize tools that may help developers in their testing. (K1)



LO-6.1 .2 Intentionally skipped



LO-6.1.3 (No Exist)



LO-6.1.3 Explain the term test tool and the purpose of tool support for testing (K2)



6.2 Effective use of tools: potential benefits and risks (K2)



LO-6.2.2 Recognize that test execution tools can have different scripting techniques, including data driven and keyword driven. (K1)



LO-6.2.2 Remember special considerations for test execution tools, static analysis, and test management tools (K1)



LO-6.3.2 State the goals of a proof-of-concept/piloting phase for tool evaluation. (K1)



LO-6.3.2 State thee goals of a proof-of-concept for tool evaluation and a piloting phase for tool implementation (K1)