Tuesday, 30 October 2012

Who uses Static Test Analysis?

Who uses Static Test Analysis?


Static analysis tools are typically used by developers (checking against predefined rules or programming standards) before and during component and integration testing, and by designers during software modeling. Static analysis tools may produce a large number of warning messages, which need to be well managed to allow the most effective use of the tool.


 
 

What are the defects found in Static Test Analysis?

What are the defects found in Static Test Analysis?

 
Defects found by Static Test Analysis could be:
  • Referencing a variable with an undefined value;
  • Inconsistent interface between modules and components;
  • Variables that are never used;
  • Unreachable (dead) code;
  • Programming standards violations;
  • Security vulnerabilities;
  • Syntax violations of code and software models.

What is the benefits of Static Testing Analysis?

What is the benefits of Static Testing Analysis?


  • Early detection of defects prior to test executions
  • Early warning about suspicious aspects of the code or design, by the calculation of metrics, such as a high complexity measure.
  • Identification of defects not easily found by dynamic testing.
  • Detecting dependencies and inconsistencies in software models, such as links.
  • Improved maintainability of code and design.
  • Prevention of defects, if lessons are learned in development
 

What is the objective of Static Testing

What is the objective of Static Testing? 



 The main objective of static testing is:
  • The objective of static analysis is to find defects in software source code and software models.
  • Static analysis is performed without actually executing the software being examined by the tool; dynamic testing does execute the software code.
  • Static analysis can locate defects that are hard to find infesting.
  • As with reviews, static analysis finds defects rather than failures.
  • Static analysis tools analyze program code (e.g. control flow and data flow), as well as generated output such as HTML and XML.
 


 


www.ISEB-sofwaretesting.weebly.com

What is a successful software testing review?

What is a successful software testing  review?



In software Testing a sucessful review consists of:

  • Each review has a clear predefined objective.
  • The right people for the review objectives are involved.
  • Defects found are welcomed, and expressed objectively.
  • People issues and psychological aspects are dealt with (e.g. making it a positive experience
  • for the author).
  • Review techniques are applied that are suitable to the type and level of software work
  • products and reviewers.
  • Checklists or roles are used if appropriate to increase effectiveness of defect identification
  • Training is given in review techniques, especially the more formal techniques, such as
  • inspection.
  • Management supports a good review process (e.g. by incorporating adequate time for review
  • activities in project schedules).
  • There is an emphasis on learning and process improvement.
 

What is an inspection in software testing?

What is an inspection in software testing?



The key characteristics of an Inspection consists of:

  • Led by trained moderator (not the author);
  • Usually peer examination;
  • Defined roles;
  • Includes metrics;
  • Formal process based on rules and checklists with entry and exit criteria;
  • Pre-meeting preparation;
  • Inspection report, list of findings;
  • Formal follow-up process;
  • Optionally, process improvement and reader;
  • Find defects.
 

What is a technical Review?

What is a technical Review?


In Software Testing a Technical Review consists of:

  • Documented, defined defect-detection process that includes peers and technical experts;
  • May be performed as a peer review without management participation;
  • Ideally led by trained moderator (not the author);
  • Pre-meeting preparation;
  • Optionally the use of checklists, review report, list of findings and management participation;
  • May vary in practice from quite informal to very formal;
  • Main purposes: discuss, make decisions, evaluate alternatives, find defects, solve technical
  • Problems and check conformance to specifications and standards.
 

What is an informal review?

What is an informal review?



In Software Testing an Informal Review consists of:

  • No formal process;
  • There may be pair programming or a technical lead reviewing designs and code;
  • Optionally may be documented;
  • May vary in usefulness depending on the reviewer
  • Main purpose: inexpensive way to get some benefit

  • What is a walkthrough?

    What is a walkthrough?


    In software testing a walkthrough consists of:
    • meeting led by author;
    • scenarios, dry runs, peer group;
    • open-ended sessions;
    • optionally a pre-meeting preparation of reviewers, review report, list of findings and scribe
    • may vary in practice from quite informal to very formal; 
    • main purposes: learning, gaining understanding, defect finding