| || |
May I ask a question, as as long as I am in the testing, I found that in the upper level such as supervisor or principle, we need to guide people more than just testing, such as we need to find out visible and hidden relations between modules of the product, we must define best matching testing approaches, ... also leading people.
I know what skills we need to become a lead, however, I don't know what we need to learn to become a test architect. So I want to ask all of you for a guidance.
Many thanks for your help and your time, you may don't know that how much I need to be shared.
Re: Test architect
It completely depends on what you mean by 'Test Architect', some companies give that title to somebody that has a lot of testing experience in their project/product, whilst in some companies they are referring to somebody that does the technical side of the test management role.
Even then the role definitions within companies will differ dramatically, so this is one of those impossible to give a full answer to.
I will start the ball rolling with a few things I expect from a test arch, it will be interesting to see what others expect:
- comfortable with creating test cases for highly complex systems to ensure full test coverage(for a given definition of full)
- in depth knowledge of several/lots of test techniques/methodologies
- in depth experience of working across all (ok lots) of development methodologies
- ability to specify and setup test environments
- ability to produce technical strategy for a project/product
- comfortable perform role outside of their comfort zone (so pick up a new technology, on a new project quickly and become the expert)
- ability to improve testing processes and techniques on a project
- ability to do test tool evaluation
- probably an expert in many test tools
In other words, they have been around the block and back and provide technical leadership for the project/product.
Hope this helps as a starting place