Wednesday, May 27, 2015

STEPS TO BE FALLOWED for preparation 2

NOW START Preparing K2 concepts

STEP 1 chapter 4 K2 :
  • Differentiate between a test design specification,a test case specification and a test procedure specification 
  • compare the terms test condition,test case and test procedure
  • Evaluate the quality of  test cases,Do they:                                                                                            -show clear traceability to the requirements;                                                                            -contain an expected result;
  • Explain the characteristics and difference between specification-based testing,structure-based testing and experience-based testing 
  • Understand the main purpose of each of the four technique , what level and type of testing could use the technique,and how coverage may be measured 
  • Understand the concept of use case testing and its benefits
  • Describe the concept and importance of code coverage
  • Explain the concepts of statement and decision coverage and understand that these concepts can also be used at other test levels than component testing 
  • Compare experience-based techniques with specification-based testing technique                                                                   
STEP 2 chapter 5 K2 :
  • List the benefits and drawbacks of independent testing within an organization 
  • Summarize the purpose and content of the test plane ,test design specification and test procedure documents according to the Standard for Software Test Documentation [IEEE 829]
  • Differentiate between standard conceptually different test approaches such as analytical ,model-based ,methodical,,process/standard compliant ,dynamic/heuristic,consultative and regression adverse.
  • Differentiate between the subject of test planning for a system and for scheduling test execution 
  • Differentiate between two conceptually different estimation approaches the metrics based approach and the expert-based approach
  • Recognize/justify adequate exit criteria for specific test levels and groups of test cases 
  • Understand and interpret test metrics for test reporting and test control
  • Summarize the purpose and content of test summary report document according to [IEEE 829]
  • Summarize how configuration management support testing 
  • Describe a risk as a possible that would threaten the achievement of one or more stackeholders project objectives
  • Distinguish between the project and product risk
  • Describe,using example, how risk analysis and risk management may be used for test planning

STEP 3 chapter 1 K2:
  • Describe the importance and value of considering static techniques for the assessment of software work products 
  • Explain the difference between static and dynamic techniques
  • Describe the objective of static analysis and reviews and compare it to dynamic testing 
STEP 4 chapter 2 K2:
  • Understand the relationship between development,test activities and work products in the development life cycle and given examples based on project characteristics and contexts
  • Compare the different levels of testing :major objectives ,typical objectives of testing,typical targets of testing 
  • Compare four software test types
  • Identify and describe non-functional test type based on non-functional requirements 
  • Identify and describe test types based on the analysis of a software system 's structure or architecture
  • Describe the purpose of confirmation testing and regression testing 
  • Compare maintenance testing to testing a new application with respect to test types ,triggers for testing and amount of testing 
  • Identify reasons for maintenance testing 
  • Describe the role of regression testing and impact analysis in maintenance
STEP 5 chapter 6 K2:
  • Classify different types of test tools according to the test process activities 
  • Recognize that test execution tools can have different scripting techniques,including data-driven and keyword-driven 
STEP 6 chapter 3 K2:
  • Describe the importance and value of considering static technique for the assessment of software work products
  • Explain the difference between static and dynamic techniques
  • Describe the objectives of static analysis and reviews and compare it to dynamic testing 
  • Explain the difference between different types of review :informal review,technical review,,walkthrough and inspection 
  • Explain the factors for successful performance of reviews 
     SO here if you all fallow diz steps from 1 to 6 surely you can cover 12 questions out of 40
therefore here K1+K2 together you can cover 20+12=32 questions out of  40 hence your passed with 80% of marks 
                                                                                     

Tuesday, May 26, 2015

STEPS TO BE FALLOWED for preparation 1

As according to the weightage I am giving list of how to start preparation

  • K1 which consists of  maximum number of questions i.e., 20 and chapter 4 consists of  maximum weightage  i.e., 12 so you should  fallow this steps in same order. like that all chapters according to weightage 

Step 1.chapter 4,K1:
.Recall reasons that both specification –based (black-box) and structure based (white   box) approaches to test case design are useful, and list the common techniques for each
.Recall reasons for writing test cases based on intuition, experience and knowledge about common defects

Step 2.chapter 5,K1:
.Recognize the importance of independent testing
.Recognize the different team members to be considered for the creation of a test team
.Recall the tasks of typical test leaders and testers
.Recognize the different levels and objectives of test planning
.Write a test execution schedule for a given set of test cases ,considering test planning .
. List test preparation and execution activities that should be considered during test       planning
.Recall typical factors that influence the effort related to testing
.Recall common metrics used for monitoring test preparation and execution.
.Remember that risks are determined by likelihood and impact 
.Recognize typical product and project risks.
.Recognize the content of the [IEEE 829] incident report.

Step 3.chapter 1,K1:
.Recall the terms 'error','defect','fault','failure' and the corresponding term 'mistake' and 'bug'.
.Recall the common objectives of testing.
.Recall fundamental test activities from planning to test closure activities and the main tasks of each test activity.
.Recall that the success of testing in influenced by psychological factors
    1.clear objectives;
    2.a balance of self-testing and independent testing;
    3.courteous communication and feedback on defects.

Step 4.chapter 2,K1:
.Recognize the fact that software development models must be adapted to the context of project and product characteristics.
.Recall reasons for different levels of testing and characteristics of good testing in any life cycle model.
.Recognize that functional and structural tests occur at any test level.

Step 5.chapter 6,K1:
.Recognize tools that may help developers in their testing.
.Recognize that test execution tools can have different scripting techniques,including data-driven and keyword-driven.
.State the main principles of introducing a tool into an organization
.State the goals of proof-of-concept or piloting phase for tool evaluation 
.Recognize that factors other than simply acquiring a tool are required for good tool support

Step 6.chapter 3,K1:
.Recognize software work products that can be examined by different static techniques
.Recall the phases,roles and responsibilities of a typical formal review
.Recall typical defects identified by static analysis and compare them to reviews and dynamic testing.
.list typical benefits of static analysis.
.list typical code and design defects that may be identified by static analysis tool.
    
     Such that you can easily attend 20 questions out of  40 and it is possible only if you fallow the order
         As you fallow the steps from 1 to 6 the quality level of your preparation increases gradually

 "Similarly for K2,K3,nad K4 will fallow in next posts"

PREPARATION Tips for ISTQB


     

            Hi ASPIRANTS in intention to help you in success of ISTQB  certification I am posting dizz

          Trust me , if you prepare according to the fallowing strategy you will easily PASS.
     

  Here
  • K1: remember, recognize, recall
  • K2: understand, explain, give reasons, compare, classify, categorize, give examples, summarize
  • K3: apply, use
  • K4: analyze
were K means "Knowledge"
     YOU can start preparation according to the list given in the next page i.e, "STEPS TO BE FALLOWED"