I’m currently estimating QA efforts for huge enterprise web portal (about 5k+ hrs DEV efforts / 1.5k hrs QA), based on Liferay / Alfresco platforms / solutions. One of the requirements – 3 interface languages user may switch from any page (place) of the solution.
So the question is that simple: is there any common practice to estimate localization testing as percentage of overall functional testing efforts?
The following assumptions / aspects are actual as well:
2 of 3 languages are common and do not require any special skills for checking from QA team; the 3rd language is uncommon (however, not TOTALLY different, as e.g. English and Japanese). Any criteria for estimations relating that 3rd language, perhaps x2 / x3 efforts required for localization testing of common language?
Which approach is better (or easier to explain) – %% based on overall functional testing efforts OR based on the approximate number of separate web portal pages?
At the moment the following makes sense for me:
5% of overall testing efforts (i.e. about 75 hrs) for common language localization testing;
Approx. 10-15%, i.e. about 200 hrs for UNcommon language localization testing.
For the record – web portal will have about 120-140 different types of pages that should have localized elements.
Any suggestions / help / ideas / approach (as best – based on real experience / cases) are highly appreciated!
P.S. no sample link available – it’s requirements refining stage.
Source: Read More
