What
will I learn?
To see
a full copy of the syllabus look on the BCS web site www.bcs.org.uk
under ISEB - Software Testing - Syllabus
Test
Principles:
Discuss what we mean by quality, testing, software quality, software
testing. Discuss elements of testing and influences on testing - mistakes,
ambiguities, assumptions, budgets, time-scales and risks. Software testing
compared with other tests, definition used in different texts, intuitive
and standard definitions. How do we assure ourselves that "The right
thing" is done? Why testing is necessary - Typical reasons for failure
and errors and how they occur. What do we mean by errors, faults, failures
and reliability. What do we mean by zero defects? Grade v. quality, fit
for purpose model, exhaustive testing is impossible, introduce idea of
testing and risk, testing and quality, testing and contractual requirements,
testing and legal, regulatory or mandatory requirements, how much testing
is enough? Testing terminology - Using the BCS SIGIST Standard Glossary
of Testing Terms (British Standard BS7925-1), also ANSI IEEE glossary.
Fundamental test process - The test process, successful tests detect faults,
meaning of completion or exit criteria, coverage criteria. The psychology
of testing - Testing to find faults, tester-developer relationship, independence,
the test paradox, who does testing? Testing and tedium - why the process
requires vision, intellect and attention to detail, testers make errors
too. Re-testing and regression testing - Fault-fixing and re-testing,
test repeatability, regression testing and automation, selecting regression
test cases. Expected results - Identifying required behaviour, checking
against expected results/outcomes, what happens if the actual results
do not match the expected results, re-tests. Difference between re-test
and regression test. Prioritisation of tests - Test scope and limited
resources, most important tests first, criteria for prioritisation, time
cost and grade constraints, the project pressure triangle.
Test Management:
Discuss organisation, planning, management and control of testing
within a project, use of project management methods. Discuss related disciplines
e.g. configuration management. CM of tests and of product, change control,
common CM errors, Test assets and reuse. Audit trails. Audit and compliance
involvement / requirements. Incident logging and tracking. Organisation
for the test team. Configuration Management - Symptoms of poor CM, configuration
identification, control, accounting, auditing. Test estimation, monitoring
and control, Testing as part of the project - budgets and time-scales.
Incident management - What is an incident?, incidents and the test process,
incident logging, tracking and analysis. Standards for testing, QA standards,
industry specific standards, testing standards. .
Testing through the life-cycle:
Discuss models of
testing, and relate these to software life cycles. Economics of early/late
error identification / cost of quality. Discuss the typical test stages
through a life cycle and who gets involved, test planning. Models for
testing - V model, V&V, deadline driven, Economics of testing - Early
test design, how preparing tests finds defects in specifications, cost
of faults versus the cost of testing. High level test planning including
test documentation, planning for audit trails, planning for test control.
An introductory look at the main test phases and types to consider.
Acceptance testing:
User acceptance testing, contract acceptance testing, alpha and beta testing.
Integration testing in the large: Testing the integration of systems and
packages, testing interfaces to external organisations.
Non functional system
testing: Non functional requirements, non functional test types (e.g.
usability, documentation, load, performance, security).
Functional system
testing: Functional requirements, requirements based testing, business
process based testing.
Integration testing
in the small: Assembling components into sub systems, stubs and drivers,
big bang, top down and bottom up approaches.
Component testing:
Overview of BS 7925-2, component test methods.
Maintenance testing:
Problems of maintenance, testing changes, risk and change, regression
testing.
Static and dynamic testing:
Define static testing, Discuss
what static testing techniques could be applied and when, Discuss in brief
static test tools and manual techniques, Discuss economics of static tests.
Define dynamic testing, Discuss what dynamic testing techniques could
be applied and when, Discuss in brief dynamic test tools and manual techniques.
Reviews and the test process. Why, when and what to review? Costs and
benefits. Types of review; goals, activities performed, roles and responsibilities,
deliverables, pitfalls. Static analysis - Simple, computer generated,
data flow, control flow, complexity. Black and white box testing - Functional
or black box testing, structural, white or glass box testing, where they
are placed in the life-cycle. Black and white box techniques as defined
in the BCS standard. Error guessing and error checklists - learning from
your own and other people's experience.
Testing
and tools:
Discuss test
tools - usefulness, disadvantages of, home made and bought in, costs,
savings, test assets, re-use, regression test , CAST, implementing test
tools, maintaining test tools. Tools and testing - why tools are useful,
tools and regression testing, tools and performance. CAST - Computer Aided
Software Testing - advantages and disadvantages, types of tools. Selecting
tools - Which test activities can be automated? How can test automation
be implemented?
to
top
Where
to find us:
Our offices
are in the west of England. We regularly provide our courses and services
throughout the UK. We have worked in Europe and the USA.
For
further information about any of our services or training courses, please
contact:
sales@ietesting.co.uk
Tel: +44 (0) 1905 726727
Fax: +44 (0) 1905 726766
or
write to
Isabel
Evans
IE Testing Consultancy Ltd
Restdale House
32/33 Foregate Street
Worcester WR1 1EE
United
Kingdom
|
