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?
Prepare test
|
|
Establish and document testing framework and schedule Completed |
Evidence:
|
Determine processes and functions to be tested and assign quantitative and/or qualitative performance benchmarks to each process and function Completed |
Evidence:
|
Benchmark and document page templates, style guides and expected traffic loads Completed |
Evidence:
|
Determine and document the test methodology Completed |
Evidence:
|
Assemble and brief the testing panel on the conduct of the test Completed |
Evidence:
|
Develop user/installation manuals according to target audience understanding and needs Completed |
Evidence:
|
Test individual pages
|
|
Test pages against style guides and templates Completed |
Evidence:
|
Test pages for structural and content consistency Completed |
Evidence:
|
Apply automatic testing software Completed |
Evidence:
|
Document page gross statistics of all confirmed results of all tests Completed |
Evidence:
|
Test page relationships
|
|
Test installation and examples listed in manual/instructions Completed |
Evidence:
|
Test page 'navigability' using a variety of browsers Completed |
Evidence:
|
Test ease of use and functionality against requirements Completed |
Evidence:
|
Test all software interface points against business and technical requirements Completed |
Evidence:
|
Test site security and privacy against business requirements Completed |
Evidence:
|
Test response time against business requirements Completed |
Evidence:
|
Conduct load simulation testing using single and multiple independent browsers or automated load testing tools Completed |
Evidence:
|
Test the website's ability to handle concurrent access Completed |
Evidence:
|
Test conformance to applicable privacy, accessibility and acceptable usage policy standards Completed |
Evidence:
|
Apply automatic testing software Completed |
Evidence:
|
Collect, collate and document results from sample user and data from automated test Completed |
Evidence:
|
Evaluate test results
|
|
Consolidate and compare results to benchmarks Completed |
Evidence:
|
Identify results that fail to meet benchmarks and conduct site remedial iteration Completed |
Evidence:
|
Record and document test results as the site performance baseline, against which further development or updating can be measured Completed |
Evidence:
|
Provide evaluation feedback to appropriate person business and, if applicable, the user Completed |
Evidence:
|
Ensure the appropriate person signs off the site prior to go live date Completed |
Evidence:
|