The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!
From the Wiki University
What evidence can you provide to prove your understanding of each of the following citeria?
Plan the test effort and develop test strategy for software testing
|
|
Critically analyse functionalities of an application software from the system design document and create a test strategy for a new telecommunications product line Completed |
Evidence:
|
Produce steps in developing test strategy and attributes of each step, according to enterprise policy Completed |
Evidence:
|
Produce a test strategy to evaluate suitability of application software for integration into the telecommunications network Completed |
Evidence:
|
Assess a range of tests required to evaluate performance and functionality of application software and determine tests required to suit the test regime Completed |
Evidence:
|
Evaluate features of testing tool and debuggers, and select an appropriate tool to test the software application and detect faults Completed |
Evidence:
|
Produce a test plan based on requirements of the project specifications, and identify testing artefacts required for model-based software testing Completed |
Evidence:
|
Plan the development of testing artefacts
|
|
Develop software testing strategies for uncovering evidence of defects in software systems as part of the quality assurance process Completed |
Evidence:
|
Produce a test dependency model of the relationship between the test regime and test levels in software testing for referencing and validation Completed |
Evidence:
|
Critically analyse software testing requirements to determine domain testing and application testing artefacts requirements to validate the software product Completed |
Evidence:
|
Develop and manage testing artefacts
|
|
Create reusable domain artefacts to detect early defects in domain testing Completed |
Evidence:
|
Modify domain test artefacts by binding variability to create application test artefacts to detect defects in product line applications Completed |
Evidence:
|
Produce test reporting associated with test cycle phases within the test plan Completed |
Evidence:
|
Critically analyse test reports and evaluate the impact of the test plan with testing artefacts on the testing environment Completed |
Evidence:
|
Manage progress of the test plan to minimise risks associated with testing and ensure the test complies with test requirements Completed |
Evidence:
|
Report detected defects to product evaluation personnel and prepare a strategy to manage defects Completed |
Evidence:
|
Critically analyse testing metrics produced by the test tool to manage tracking of defects, and use metrics to plan process improvements Completed |
Evidence:
|
Produce an evaluation report from the traceability matrix to manage defects or failures from the test plan Completed |
Evidence:
|