| <?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.3/uma.ecore" epf:version="1.0.0" xmi:id="_NqYIcKeqEdmKDbQuyzCoqQ" name="tester,_0ZM4MclgEdmt3adZL5Dmdw" guid="_NqYIcKeqEdmKDbQuyzCoqQ" changeDate="2006-09-26T13:51:28.608-0700" version="1.0.0"> |
| <mainDescription><p> |
| This role is primarily responsible for the following&nbsp;tasks: |
| </p> |
| <ul> |
| <li> |
| Identify the tests&nbsp;that need to&nbsp;be performed |
| </li> |
| <li> |
| Identify the most appropriate implementation approach for a given test |
| </li> |
| <li> |
| Implement individual tests |
| </li> |
| <li> |
| Set up and execute the tests |
| </li> |
| <li> |
| Log outcomes and verify that the tests have been run |
| </li> |
| <li> |
| Analyze and recover from execution errors |
| </li> |
| <li> |
| Communicate test results to the team |
| </li> |
| </ul></mainDescription> |
| <skills><p> |
| A person&nbsp;filling the&nbsp;this role should have the following 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> 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.&nbsp;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 members that is already playing another role in the project to be responsible for the |
| testing of some part of the system’s capabilities.&nbsp;The team member will have to have the appropriate test |
| skills |
| </li> |
| </ul></assignmentApproaches> |
| </org.eclipse.epf.uma:RoleDescription> |