Role-based Framework

The cult of the amateur is a major problem within the test automation industry. Major vendors of test automation software have over sold the involvement of the inexperienced.
Where ever you find test automation projects that fail you will also find test automation novices operating without a methodology or framework.

Traditionally, a testers involvement in automation usually means wearing at least two hats - that of test engineer and test analyst. On very rare occasions this can deliver exceptionally well. As a general practice it is a disaster.

Most test automation efforts merge the implementation of test automation with it's specification. Those that rely on the "record and playback" paradigm are an extreme example of this.

Role-based testing acknowledges the specialisms that exist within the test function. Many test automation projects struggle, simply due to under appreciating the need for specialisation. They deliver neither good analysis nor good engineering.

Only a framework that recognises role based testing can deliver high productivity. This is when test automation engineers and test analysts deliver what they do best. To fully realise this benefit frameworks have to support this distinction by design.

The W3QA Framework is designed to fully support role-based testing.This is one of the advanced features of the W3QA Framework.

Test Analysts write and maintain test specifications and verify failure. Test Engineers write code and schedule the execution of automated test frameworks.

The HRMES Framework is unified across test levels and test assets are common, shared and transferrable, but the entire process supports specialisation and domain expertise.