BCS/ISTQB Software Testing Foundation Course London UK
Home Software Testing BCS/ISTQB Software Testing Foundation

BCS/ISTQB Software Testing Foundation

  • This course is the first internationally accepted industry accreditation for software testing. This course covers the fundamentals of software testing and helps you to build a strong foundation and will enable professionals to logically speculate the processes and events and be creative and innovative enough at the same time to find the bugs.

    This course is the certified ISTQB-BCS Certified Tester – Foundation Level (previously ISEB Foundation Certificate) – an established qualification and an industry recognised standard for companies and individuals to prove knowledge of the fundamentals of software testing.

     

     

     

    FUNDAMENTALS OF TESTING

    Why is Testing Necessary

    Defines software errors, defects, and failures, and explains their contexts, causes, and costs. Recounts the role of testing in software development, maintenance, and operations, and discusses how testing is related to risk and to quality, and how to determine how much testing is enough.

    What is Testing

    Remedies the misperception that “testing means running a program to see what it does” by identifying the test activities that precede and follow test execution. Distinguishes static and dynamic testing, and differentiates testing from debugging. Emphasises the need to ensure that test objectives are relevant to the testing context.

    General Testing Principles

    Describes 7 basic principles of good testing, which should be applied to all kinds of testing and at any level.

    Fundamental Test Process

    Outlines the essential activities of a fundamental test process, consisting of planning and control, analysis and design, implementation and execution, evaluating exit criteria and reporting, and test closure activities.

    Psychology of Testing

    Discusses differences between the tester’s and developer’s mindsets, the importance of independence in testing, and how independence can be achieved while maintaining good relations.

    TESTING THROUGHOUT THE LIFECYCLE

    Software Development Models

    Discusses different ways of relating test activities and work products to development activities and work products; draws out a set of integrated relationships suitable for any life cycle model, based on four “levels” of testing (component testing, integration testing, system testing, and acceptance testing) and the principle of “early test design”.

    Test Levels

    Describes the major objectives and targets of each of the four test levels, identifying related development work products (“test basis”), types of defect and failure looked for, and likely test personnel.

    Test Types: the Targets of Testing

    Describes and compares four types of test “target”: software functions; “non-functional” characteristics such as performance and usability; software architecture and other structures such as program code; and change-related testing (confirmation testing and regression testing).

    Maintenance Testing

    Describes the special environment and considerations of post-release (“maintenance”) testing, including impact analysis to establish the need for regression testing.

    STATIC TECHNIQUES

    Reviews and the Test Process

    Explains why reviews are beneficial, what can be reviewed, and when in the lifecycle they should be carried out. Discusses the costs and benefits of reviews, and the relationships and differences between static and dynamic techniques.

    Review Process

    Describes the phases, roles, and responsibilities of a typical formal review. Explains the differences between informal reviews, walkthroughs, technical reviews, and Inspection.Discusses the factors for successful performance of reviews.

    Static Analysis by Tools

    Describes the objectives of static analysis as a form of “automated review”, and compares it to dynamic testing. Identifies typical code-level defects most easily found by static analysis, and lists typical benefits of static analysis.

    SESSION 4: TEST DESIGN TECHNIQUES

    Identifying Test Conditions and Designing Test Cases

    Covers the analysis of test conditions from a test basis document, the design of tests to exercise those conditions (“Test Design Specification”), and the implementation of tests via detailed “Test Case Specifications”, “Test Procedure Specifications”, and test execution schedules.

    Categories of Test Design Technique

    Explains the characteristics and differences between specification-based testing, structure-based testing, and experience-based testing. Identifies reasons that both specification-based (black-box) and structure-based (white-box) approaches to test case design are useful, and lists common techniques for each.

    Specification-Based or Black Box Techniques

    Describes four black box modelling techniques (equivalence partitioning, boundary value analysis, decision tables, and state-transition testing), and how their degrees of “coverage” may be measured. Introduces the concept of use case testing and its benefits.

    Structure-based or White Box Techniques

    Describes the concept and importance of statement and decision coverage, including their potential use at all test levels. Explains how to identify test cases based on process flows by using statement testing and decision testing.

    Experience-Based Techniques

    Explains how to supplement systematic techniques with additional creative test techniques, such as error guessing and exploratory testing.

    Choosing Test Techniques

    Shows how different techniques can be used for different kinds of testing and the importance of choosing the appropriate techniques for particular kinds of problem.

    TEST MANAGEMENT

    Test Organisation

    Discusses the importance of independent testing, stressing the resulting need for good communication between testers and the rest of the organisation. Recognises and describes the different roles of “tester” and “test leader” (test manager), listing typical tasks of each.

    Test Planning and Estimation

    Summarises the purpose and content of the Test Plan document according to the ‘Standard for Software Test Documentation’ (IEEE 829). Differentiates two estimation approaches (the metrics-based approach and the expert-based approach). Explores concepts of test adequacy criteria (“exit criteria”) for specific test levels, and outlines several testing strategies that might be selectively combined into a planned “test approach” for achieving them.

    Test Progress Monitoring and Control

    Describes the need to monitor test activities to identify deviations from the Test Plan, so that corrective (“control”) actions may be agreed and undertaken. Identifies common metrics used for monitoring test preparation and execution, such as progress in test case specification, or tests run, passed, and failed. Summarises the purpose and content of the Test Summary Report document specified in the ‘Standard for Software Test Documentation’ (IEEE 829).

    Configuration Management

    Explains why configuration management and change control are necessary, particularly in testing. Discusses the configuration items for testing.

    Risk and Testing

    Describes the nature of risk, distinguishing “project risks” from “product risks”, and shows how risk analysis is used throughout testing to determine what to test, how much to test, and what should be tested first.

    Incident Management

    Discusses how to record incidents according to the ‘Standard for Software Test Documentation’ (IEEE 829), what needs to be tracked, and analysing defect statistics. Discusses the difference between severity and priority, and between defects and change requests.

    TOOL SUPPORT FOR TESTING

    Types of Test Tool

    Describes seven categories of software test tools, outlining what each type can do, and particularly identifying tools that might benefit testers in their testing.

    Effective Use of Tools: Potential Benefits and Risks

    Summarises potential benefits and risks of test automation and tool support for testing.

    Introducing a tool into an Organisation

    States the main principles of introducing a tool into an organization, describing the goals of a proof-of-concept/piloting phase for tool evaluation, and recognising that factors other than simply acquiring a tool are required for good tool support.

    • 2 Months guaranteed internship placement with industry reference
    • Intensive Hands-on Training
    • Complete Study Materials, Course-ware and Testing Software
    • Facility to conduct an Onsite testing
    • Our instructors follow a flexible approach of teaching thus the training methods are altered as per the trainees needs. We offer study material, hands-on labs, skills to work as a team by giving more and more team activity or tasks. Various review exams from time to time to analyse your knowledge.
    • LSI has state of the art training facilities and is equipped with world class fixtures and sans peril instructors who are available to answer your queries. We have labs and libraries open for our trainees

    Q. Is this course accredited?

    A. Yes, it is accredited by the BCS (British Computer Society) and the ISTQB (International Software Testing Qualifications Board).

    Q. What experience does the course instructor have?

    A. All of our instructors are fully accredited and have over ten years of experience.

    Q. What does LSI provide me with on the course?

    A. We provide the learning materials such as presentation slides and practice papers, official certificates and refreshments.

    Q. Does the course include exams?

    A. Yes, the course includes the Software Testing Foundation examination.

    Q. Are there any prerequisites for the Software Testing examination?

    A. There are no prerequisites for the exam.

    • 2 months hands on industry experience.
    • Gives you an edge over your peers in job market.
    • Be able to improve your resume and credentials.
    • Understand various bug logging tools and learn to write good test report.
    • Get opportunities which would both be challenging and will provide participants satisfaction professionally.
    • Get best of monitory benefits within the industry with careers in field of Software Testing.

    The ISTQB-BCS Certified Tester Foundation Level course is aimed at software developers, testers (both technical and user acceptance testers), test analysts, test engineers, test consultants and managers – including test managers, project managers, quality managers and anyone with an interest in software testing. The ISTQB-BCS Certified Tester Foundation Level course is a prerequisite for taking the more advanced BCS Intermediate Certificate.

     

Get your free ebook

itil-course