Component Designs and Test Plans
(due Sunday night, as individual Canvas assignments submission)
- P3B.1 Component Designs
- Do you know how you will implement each of your public methods?
- Have you defined the functionality and interface specifications for
any necessary private methods?
- Do you know how you will make (and process the results of) every call you
make to another component?
- Do you know how you will make (and process the results of) every call you
make to an external service?
- Is it clear to you what mock implementations you will need for
your calls to other components (for unit testing)?
- P3B.2 Component Test Plans
- Do you have a list of the functionality to be verified?
- Do you have a list of the assertions to be verified for each function?
- Do you have adequate controlability of the functions and their context
to exercise those assertions?
- Do you know where you will get the mock implementations of other
components (to support each of these test cases)?
- Do you have adequate observability of component state to confidently
verify correct execution?
- Is it clear to you how to implement each of those test cases in your chosen
testing framework?
- P3C Moving Forward
- Have you identified reviewers and set a schedule for the review of
your design(s) and test plan(s)?
- Is there any rationale (or research/prototyping results) that those
reviewers should understand before they review your design and
test plan?
- Will the reviewer(s) need any background on the external services
or tool kits you will be using?
- Will the reviewer(s) need any background on the testing framework
you propose to use for your automated unit testing?