Semi-automating QA tests

[o355]

If you don't know, PyWeather QA is done about a month before release to iron out any bugs. To do this, we use random data in regards to city names, and other data types.

Way back before PWSes and airport queries were introduced, it was pretty simple. Fake name generator, type in the city name, run through all the prompts. If a bug appears note down the city name and the traceback.

However, now with having to input 16 locations per copy of PyWeather (5 for runs 1 & 2 - Default options and random options), it's getting a little tough to manually find this data, and I even considered cancelling FreeNAS QA as a result.

But fear not, I'll soon be including a randomcity.py script with PyWeather in the tools folder for QA and for anyone who wants to debug PyWeather. It'll work like this:

• The script will fetch fakenamegenerator.com, and with BeautifulSoup read the city name (I have to learn this but it shouldn't be bad)
• After learning the city name, we query Google's geocoder to get the lat/long of the city.
• With the lat/long in hand, we query Wunderground's API to get a nearby PWS and airport listing
• With this data, we pick the closest airport and randomly select one of 10 nearby PWSes.
• At the end everything is printed out for input into Pyweather.

In addition, this script will have arguments support.

-eu can be used to select to select a random city in the EU (including the UK for convenience) for randomness.
-city "name" can be used to get the nearest airport and a random PWS with a predefined city name.

Development of this script will begin sometime in July, once we get all other minor fixes sorted.