Test Plan Document Comments

Team: DNA

Grade: (77 out of 100)

Scope (17 out of 20 points)

• Are there pointers to sources for input to testing. OK, but would be better to point directly to the functional requirements section and non-functional requirements section.
• Is there a clear delineation of what activities are subject to the test plan? yes

Schedule (15 out of 20 points)

• Is there a pointer to the current project schedule at the point where testing activities are defined and scheduled? No, just a pointer to the overall schedule. Simple thing to fix. Send the link to the explicit place where testing is scheduled in your current schedule. If more than one place, tehn use more than one link.
• Does the schedule reflect the details of this plan, meaning has enough time been set aside for the testing that will be performed by this team? It is OK if some tests are defined that are not intended to be completed this quarter, but they should be clearly indicated as such. And at least some of the test plan should be executed this quarter. I can see unit testing being explicitly identified, though the time set for that seems low. Where are integration or validation tests brought out?

Validation tests (45 out of 60 points)

• Is there a test defined for every functional and non-functional requirement? The non-functional requirements seem to be covered by a single test, number 7. Is that sufficiently detailed plan to cover the three NF requirements you listed in your Req. doc?
• Is the test clearly defined? OK, except for Test 7.
• Is it clear if/when the test will be conducted this quarter? OK, but it's a bit clumsy to go from test to schedule to figure out when the testing will occur. Information is there, however.
• Is there a clear template for reporting test results? It's fairly generic result template. Not sure it will be that useful for all tests.