But the question I ask myself is, how should a test charter be built at all?
In this case we used the tips from Elisabeth Hendrickson.
For example, in our project we used an easy test charta template as followed:
Easy template as example
Investigate a goal with medium/resources in order to find (more) information about it
So what does this mean?
I don't think there is one universal approach to tool selection..
That is correct! I would like to explain which experience we made in our company.
Regarding the challenges:
Language: In our company we had e.g.business department, development center and e.g. some kind of testing centers for e.g. different departments. The problem is, that within the ...
I don't think there is one universal approach to tool selection, let alone to tool selection for test automation.
There are many areas and questions you need to consider before going for a particulat tool or set of tools:
How mature is the test tool? Is it available in a stable version, or is it still under heavy development?
How well can you use it? How ...
First, determine the business objective
In order to answer the questions about what to use, first determine the business objectives such as:
What speed is needed for deploying changes ?
What is the cost of automation, especially people ?
What is the future budget for Quality Assurance ?
How fragile is the application code ?
What is the revenue from ...