Definitely no developer tests all possible combinations, that’s not feasible :/ More likely these manual tests (at least how I’ve used them) is to verify a Camera bug, then verify the fix to the bug worked. It’s not ideal of course since the fix could break some other functionality, but I don’t have any ideas how to effectively cover all cases.
A “smoke test” set of frequently combinations to use would be the best way I suppose. On July 25, 2014 at 6:02:30 AM, Edna Y Morales (eymor...@us.ibm.com) wrote: > > > Hi all, > > I am currently working on adding some documentation to all of the manual > tests (expected results, test process, etc). Looking at the camera manual > tests, I see that there are several different options to test for getting a > picture (source type, destination type, target width, allowEdit, > correctOrientation, etc). I was hoping to get some feedback on what the > original intention for these tests were. I do not think it is necessary to > test every single possible combination of options, as that would be very > time consuming. I think selecting a specific set of combinations to test > that maximizes coverage, and documenting that for the tester to follow > should be sufficient. However, I am open to any thoughts or suggestions. > > Thanks, > Edna Morales, Developer - Apache Cordova
