|
|
Requirements
Analysis for
Test
Documentation
(Part 1)
- Cem Kaner
Dr Kaner talks about the
requirement analysis of the
Test documentation. According to Dr
Kaner IEEE 829 is an
paradigmatic example of
standard that supports heavy
weight software development
process. You don't have to
generate all the documents
listed in 829 to be IEEE 829
compliant. Time spent in
filling boiler plate
information could be spent in
documenting testing
strategies and other useful
information. The biggest
problem with modern heavyweight
projects is that they have a
lot of inertia and resist
the necessary change.
|
Requirements
Analysis for
Test
Documentation
(Part 2)
- Cem Kaner
In this part Dr Kaner
explains that using
'Prescriptive Standards' and
templates will yield
inappropriate products.
Questioning should be used
to gather documentation
requirements. There are
different types of
stakeholders and each one is
dealt differently. Dr Kaner
answers some of the
questions about Test
Document Requirements. Needs
of the organisation are more
important than the
prescriptive standards.
Function Testing- Dr. Cem Kaner
In this video Dr Kaner
explains about functional
testing. He talks about the
functional testing tasks and
the risks present in this
type of testing
|
