| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:RoleDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="_NqYIcKeqEdmKDbQuyzCoqQ" name="tester,_0ZM4MclgEdmt3adZL5Dmdw" guid="_NqYIcKeqEdmKDbQuyzCoqQ" changeDate="2009-07-29T11:36:50.000-0700" version="1.0.0"> |
| <mainDescription><p>
 |
| The person in this role is primarily responsible for the following tasks:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| Identifying the tests that need to be performed
 |
| </li>
 |
| <li>
 |
| Identifying the most appropriate implementation approach for a given test
 |
| </li>
 |
| <li>
 |
| Implementing individual tests
 |
| </li>
 |
| <li>
 |
| Setting up and running the tests
 |
| </li>
 |
| <li>
 |
| Logging outcomes and verifying that the tests have been run
 |
| </li>
 |
| <li>
 |
| Analyzing and guiding the recovery from execution errors
 |
| </li>
 |
| <li>
 |
| Communicating test results to the team
 |
| </li>
 |
| </ul></mainDescription> |
| <skills><p>
 |
| A person filling the this role should have these skills:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| Knowledge of testing approaches and techniques
 |
| </li>
 |
| <li>
 |
| Diagnostic and problem-solving skills
 |
| </li>
 |
| <li>
 |
| Knowledge of the system or application being tested (desirable)
 |
| </li>
 |
| <li>
 |
| Knowledge of networking and system architecture (desirable)
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| Where automated testing is required, consider requiring these additional qualifications:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| Training in the appropriate use of test automation tools
 |
| </li>
 |
| <li>
 |
| Experience using test automation tools
 |
| </li>
 |
| <li>
 |
| Programming skills
 |
| </li>
 |
| <li>
 |
| Debugging and diagnostic skills
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| <strong>Note:</strong><br />
 |
| Specific skill requirements vary depending on the type of testing that you are conducting. For example, the skills
 |
| needed to successfully use system load-testing automation tools are different from those needed for the automation of
 |
| system functional testing.
 |
| </p></skills> |
| <assignmentApproaches><p>
 |
| This role can be assigned in the following ways:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| Assign one or more testing staff members to perform this role. This is a fairly standard approach and is
 |
| particularly suitable for small teams, as well as for teams of any size where the team is made up of an experienced
 |
| group of testers of relatively equal skill levels.
 |
| </li>
 |
| <li>
 |
| Assign one or more testing staff members to perform only this role. This works well in large teams. It is also
 |
| useful to separate responsibilities when some of the testing staff has more test automation experience than other
 |
| team members.
 |
| </li>
 |
| <li>
 |
| Assign one (or more) team member who is already playing other role in the project to be responsible for the testing
 |
| of some part of the system's capabilities. The team member must have the appropriate test skills.
 |
| </li>
 |
| </ul></assignmentApproaches> |
| </org.eclipse.epf.uma:RoleDescription> |
