|
|
|
Tutorials:
Series W
|
You must specify which tutorial you wish to attend (W1 through W2) Tutorials marked with (CSTP) will count as one day of training towards the requirements for the Certified Software Testing Professional |
| W1 | Proactive User Acceptance Testing (Basic) (CSTP, Elective) |
Robin F. Goldsmith JD |
| W2 | Practical
Test Management
(Basic) (CSTP) |
Brian Hambling |
Or PSQT/PSTT Conference Sessions
| Managing Software Testing for eCommerce Projects | Thomas McCabe |
| How Do You Know When You Are Done Tesing? | Richard Bender |
| How to Release the Hiden Power of Inspection | Dr. Rebecca Staton-Reinstein |
| Measuring the Software Testing Process | Linda Westfall |
| Using the Cost of Quality Approach for Software: A Progress Report | Herb Krasner |
| 16 Track Presentations | |
| The Software Quality Summit |
Series M - Monday, April 2,
2001
Series T - Tuesday, April
3, 2001
Series H - Thursday, April
5, 2001
Series F - Friday, April 6,
2001
W1: Proactive User Acceptance Testing (Basic) (CSTP, Elective)
Robin F. Goldsmith JD
This tutorial counts as one day of training towards the Certified Software Test Professional requirements.
Users/customers have a very strong
need to be sure the systems they depend on actually meet business requirements, work
properly, and truly help them do their jobs efficiently and effectively. However, users seldom are confident or comfortable
testing system acceptability. This intensive
interactive seminar shows users what they need to know to confidently make the best use of
their time planning and conducting acceptance tests that catch more defects at the
traditional tail-end of development, while also contributing in appropriate ways to
reducing the number of errors that get through the development process for them to catch
in UAT. Exercises give practice using
practical methods and techniques.
Participants will learn:
Appropriate
testing roles for users, developers, and professional testers; and what each shouldn't
test.
How Proactive
TestingÔ throughout the life cycle reduces the number of errors left to
find in UAT.
Key testing
concepts, techniques, and strategies that facilitate adaptation to your situation.
Systematically
expanding acceptance criteria to an acceptance test plan, test designs, and test cases.
Supplementing
with requirements-based tests, use cases, and high-level structural white box tests.
Techniques for
obtaining/capturing test data and carrying out acceptance tests.
WHO SHOULD ATTEND: This course has been designed for business
managers and system users responsible for conducting user acceptance testing of systems
they must depend on, as well as for system managers, project leaders, analysts,
developers, quality/testing professionals, and auditors.
ROLE OF USER ACCEPTANCE TESTING
Why users may
resist involvement
Making users
confident about testing
Objectives,
types, and scope of testing
Acceptance
testing as users self-defense
Why technical
tests dont catch all the errors
Essential
elements of effective testing
CAT-Scan
ApproachÔ to find more errors
Proactive
TestingÔ Life Cycle model
Separate
technical and acceptance test paths
Place of UAT in
overall test structure
Making sure
important tests are done first
Developer/tester/user
test responsibilities
DEFINING ACCEPTANCE CRITERIA
Defining
acceptance test strategy up-front
Source and role of acceptance criteria
5 elements
criteria should address
Functionality
the user must demonstrate
How much, how
often user must test
Determining
system quality
Who should carry
out acceptance tests
How acceptance
tests should be performed
Added benefit,
revealing requirements errors
DESIGNING ACCEPTANCE TEST PLANS
Expanding the
acceptance criteria
Allocating
criteria to system design
Refining the
design to catch oversights
Checklist of
common problems to test
Equivalence
classes and boundary values
Making quality
factors (attributes) testable
Structural
testing applicable to users
GUI features
that always need to be tested
Defining
requirements-based tests
Constructing use
cases
Cautions about
use case pitfalls
One- and
two-column use case formats
Turning use
cases into tests
Consolidating
tests into efficient test scripts
CARRYING OUT ACCEPTANCE TESTS
Differentiating
test cases and test data
Traps that
destroy value of acceptance tests
Warning about
conversions
Documentation,
training, Help tests
Configuration,
installation, localization
Security,
backup, recovery tests
Suitability of
automating acceptance testing
Performance,
stress, load testing
Issues on
creating test conditions, data
Capturing
results, determining correctness
User's defect
tracking and metrics
Top of Page Tutorials: Series W
W2: Practical Test Management (Basic) (CSTP, 3&4)
Angelina Samaroo, Brian Hambling
This tutorial counts as one day of training towards the Certified Software Test Professional requirements.
Practical Test Management
Most test professionals agree that testing is a
risk reduction process. We also agree that
the earlier the testing starts, the better the quality of the software. We do not always get the opportunity to be 'first
in line', but we are always the last in the line of activities within the SDLC. No amount of early testing will change that. With
this burden of responsibility, how do we manage our testing so that we deliver what is
required? First of all, we need to know what
needs to be done. The ideal is one hundred
percent functional coverage, and no outstanding defects.
· Risk Management
- assessing the business risks
- identifying where testing can help to reduce risk
- Planning to monitor risks
· Preparing a test strategy
- matching the testing to the risk
- matching testing to the development culture
- working with available resources
· Preparing a test plan
- defining and scheduling the testing activities
- scheduling the resources
· Creating test scripts to deliver the planned testing
· Monitoring the test process
- checking progress against the plan
- identifying and reporting problems and changes
- using actual performance to update the test plan
· Defect tracking
· When to 'raise the flag'
· Meaningful test reporting
· Metrics for test improvement
· Automated test management tools
Tutorial Learning Objectives
· Why test planning is essential
· How to cope with changes
· How to get buy-in from other project members
· Why and what metrics should be collected
· How automation can help
Angelina Samaroo BEng(Hons), CEng, MRAeS, AMIEE has spent her entire career in software testing. She started in the defence industry, learning testing from first principles, working closely with designers and developers. For the last two years she has worked in the commercial sector, paying particular attention to the testing of e-business systems, and has very recently devised a process for turning the many standards and guidelines for testing into practical templates for every-day use. She is an approved trainer for the UK's iseb Foundation Certificate in Software Testing, and has trained over two hundred delegates - including 30 delegates at the EuroSTAR conference in Copenhagen, December 2000.
Brian Hambling BA, MSc, Ceng, MIEE, MBCS has worked in the software industry for over 25 years. A career that began with software development for real-time avionics systems has moved steadily in the direction of tackling the quality concerns that have always inflicted high cost and uncertainty on the Information Technology industry. Brian has now experienced the software business across a very broad spectrum of application and business domains, from mission-critical defence systems to business-critical e-business systems. He has been active throughout in seeking to develop, promote and implement quality enhancing practices and he has contributed to the creation of standards, the education of developers and quality specialists, the implementation of quality systems through the TickIT scheme and, more recently, the certification of software testing professionals. Brian is now Technical Director of ImagoQA, the UKs leading software testing consultancy.
Top of Page Tutorials: Series W