(REVISED) PPCGeeks Unified ROM Project: Process Proposal

[thallanor]

Originally Posted by psiphi

So what is the criteria for "passing" a QA test? Do we go the Microsoft way and pick the top 100 apps downloaded for WM5 and say we are done when they work, do we poll our own list of apps to focus on, or do we just create a large feature list?

Note the list of apps would only be for compatibility certification, not necessarily for inclusion in a ROM... For instance, I would like GSPlayer compatibility for MIDI support, but think it would be silly to include it in a ROM due to size of the sound samples... Reality is that this app would probably NOT be a priority for compatibility testing anyway because it's just too small a nitch, but thats where a poll or a feature list might make an exception...

Thoughts?

What you are describing is compatibility testing. While a piece of software might not work due to a bug in the operating system, I feel that in a project like this, QA is more focused on problems with the actual OS. Does the Start Menu not come up? Does removing a program cause the OS to hang? Is there a memory leak causing the device to slowly run out of memory until it freezes? Those sort of things. I think that issues like that must be eliminated before application testing begins. At that point, that sort of testing can begin, but I still think it is different than pure QA.