Test organisation in projects 
At the start of a test project, the roles, tasks, authorisations and responsibilities for the test project are defined. This can be done for the total test process (i.e. across all test levels), or for one specific test level. The relationship between the specified roles, the separate test levels, and the relationships with the other stakeholders in the system development process are then determined and laid down. The test manager must not forget to establish the relationship with a test or quality department, if any. 

Test professional 
A great variety of expertise is required for a tester to be able to function well in the discipline of testing. A tester must have knowledge in the field of the subject matter, the infrastructure (test environment, development platform, test tools) and testing itself. What are a tester’s characteristics, in other words,   what properties must a person have to be an ideal tester? While many can be listed, the tester must at least:

• have verbal and written communication skills
• be able to work accurately and have analytical skills
• be convincing and persevering
• be factual and have a positively critical attitude
• be creative. 

Test roles 
The execution of test activities in a project or in the line requires that the tasks are defined and that the executor of the tasks has the right knowledge and competencies. Roles and positions can be distinguished in this respect. A role is the description of one or more tasks with the required knowledge and competencies. There are roles that match positions one-on-one. There are also roles that do not exist as a position. Differences and similarities between roles and positions:

• A role aims at fulfilling tasks for the test project or permanent test organisation. 
• A position focuses on the employee and his place in the career cube.
• They share the tasks to be executed and the required knowledge competencies.