Please let me know what I should do to test this.
AFAIK, we have never made a definitive list for testing every thing that a porter sets in the sub/<fw> directories. In general, the first firmware version of a new port gets some high level functionality tests - with a bias towards things that are hard to find or have caused problems. Just getting CHDK to load and display menus correctly is a big step all by itself.
Subsequent additions of different firmware versions for any released port get a bit of a free pass. If they appear to work then, based on the original port being good, we mostly assume they are okay until anyone reports otherwise .
So the big things I'd suggest checking are :
- RAW/DNG images - take some shot with DNG enabled and assure yourself that the DNG images actually look like uncorrected versions of the related JPG
- USB remote - enable this and just use a regular USB cable plugged into a spared charger or computer port to trigger it and assure it's working
- exposure overrides in the Enhanced Photo Operations menu - set both Tv, Sv, & Av and make sure the resulting image change appropriately when you change the values
- set a long exposure time (30 seconds) and then see if dark frame subtraction control works ( if not, it will take 60 seconds to complete a 30 second exposure)
- try out the edge overlay, historgram, and zebra functions and make sure they seem to work (i.e. usable images on the camera's LCD)
- try running some scripts - there are four simple ones included with the CHDK installation file and hundreds more online at places like this
- play with anything else that tweaks your interest
There is learning curve here so feel free to post questions. If all else fails -
RTFM. And tell us how you did - if the 1.01b build passes the above list of tests without crashing then we will release it for distribution in the autobuild.