Last time I wrote about EDFU, but this time I'll focus on some testing techniques. Probably many of us use them, but it may be interesting to recap.

We can use:

• data-driven testing - to find defects in which certain data is incorrectly processed (e.g. using values above a higher boundary or below a lower boundary can be very effective in finding defects)
• logic-driven - to identify all incorrect handling of the logic (e.g. testing certain combinations of inputs to every logical expression)
• event-driven - to discover incorrect handling of events (the time sequence and arrival time of different inputs may introduce failures, especially in 'mobile world')
• state-driven - to find all incorrect state transitions (all critical states and critical transitions need to be tested)
• dataflow-driven - to focus on problems in component interfaces (data element receives a value in one place and uses it in another - sometimes the value is misinterpreted)

One can also add Message Sequence Charts to understand client-server architecture better, code review (probably one of the most efficient defect finding techniques, but it's very slow and should be used only on the most risky components), extreme programming (includes testing).

Some other facts related to development and quality assurance process you can find in a new set of S60 guidelines: http://www.forum.nokia.com/document/S60_Platform_Development_and_QA_Process_Guideline/
 

I'd like to know your opinions and experiences in using testing frameworks to speed up testing like JUnit for java (or checking your code with SymScan for C++)... Do you consider the Symbian Signed and Java Verified requirements when designing test cases?