Our software has mainly been used in the UK and US, but is now being used in more European countries and we are coming across problems with the differing locales. So I want to write a general 'regional settings' checklist that can be run against existing and new functionality to ensure that these problems are found early.
I'm thinking about things like, differing date and number formats, different languages used in filling in forms etc. We aren't talking about changing the language of the system though (keeping with universal english).
Does anyone have examples of tests that can be run for this sort of thing?
With respect to Regional Settings, we need to concentrate on Date formats (Different combination (mostly all possible) like mm/dd/yy, yy/mm/dd etc.).
And one major problem comes when working with decimal numbers. Some users will use ',' insted of '.' for decimal indication. This will give lot of problems while calcultions and data saving for decimal numbers.
So these two major issues should consider while writing test cases. You can define standard testcases for this type of testing.
We have a proprietary application that runs in several European countries, Japan, and the U.S. We data drive the automation tool and after an automated query is run to determine the country, the proper data & format is passed to the tool functions to test for that countries particular criteria. Perhaps a similar approach would work for manual testing as well.
Success is the ability to go from one failure to another with no loss of enthusiasm.
~ Winston Churchill ~